Can I use hyphens, spaces and extra underscores inside UCS filename blocks, and how do tools split the optional UserCategory and VendorCategory parts?
Per the vendor-page text, hyphens carry meaning: a hyphen after the CatID starts UserCategory and a hyphen inside the FXName block ends an optional VendorCategory. ucs-tools says this makes the split ambiguous and resolves it structurally, while ucsrename's habit of turning spaces into hyphens would make an ordinary multi-word FXName parse as VendorCategory plus FXName under the vendor-page rule. This is a synthesis from secondary text and code; the official document was not read.
Per the vendor-page text, hyphens carry meaning: a hyphen after the CatID starts UserCategory and a hyphen inside the FXName block ends an optional VendorCategory. ucs-tools says this makes the split ambiguous and resolves it structurally, while ucsrename's habit of turning spaces into hyphens would make an ordinary multi-word FXName parse as VendorCategory plus FXName under the vendor-page rule. This is a synthesis from secondary text and code; the official document was not read.
Curator qualifications: Excerpted evidence located (one unexcerpted row); separators inside UCS blocks and how tools split optional blocks.
Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.
Structured fields
{
"citations": [
{
"url": "https://www.jamsoft.co.uk/samplesort/support/universal-category-system/",
"note": "candidate evidence excerpts"
},
{
"url": "https://github.com/jmrsound/ucs-tools/tree/2e307eb9aa4743a7a666426a9f70dcd08d393b40",
"note": "candidate evidence excerpts"
},
{
"url": "https://github.com/brettbuddin/ucsrename/tree/9fa454378d50076edc67370ce56f60b3bbf9c43a",
"note": "candidate evidence excerpts"
}
]
}Evidence claims
- [sourced_fact] Per the vendor-page text, hyphens carry meaning: a hyphen after the CatID starts UserCategory and a hyphen inside the FXName block ends an optional VendorCategory. ucs-tools says this makes the split ambiguous and resolves it structurally, while ucsrename's habit of turning spaces into hyphens would make an ordinary multi-word FXName parse as VendorCategory plus FXName under the vendor-page rule. This is a synthesis from secondary text and code; the official document was not read. · locator: candidate evidence excerpts source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |