3 ms·

I agree that potential integration with non-Unicode systems is a real concern I hadn't thought of. However, your examples of complexity in the service of demons

I agree that potential integration with non-Unicode systems is a real concern I hadn't thought of. However, your examples of complexity in the service of demonstrating why a system might not support Unicode don't seem to affect or be affected by the allowance of all printable Unicode characters in digital representations of proper nouns, unless I'm misunderstanding. I.e. I don't understand why these problems mean that a postal system might elect to not support all scripts in storage (I get why it means the OCR software for a postal office might not support scripts outside their own country's scripts).

jerf 3y ago
Because having the script in storage is not enough to derive the other possible representations that may be needed. partdavid's answer is correct, you may have to ask for other representations to be provided to you. This is much like the naming scenario, where I may need both your legal name for legal reasons, which may have local restrictions on it, and I may also have a field that is basically "What do you want me to call you?" which may have arbitrary unbounded Unicode for all I care, I don't care if my system calls you the Lord and Master of Zalgo Text. But there's no programmatic way to get from the latter to the former, or indeed, even a human way.