May be, but using such sequence will not work in many cases: - the display will be almost always wrong due to lack of cont support for some unspecified combinations, or because the usage is too recent - the parsing will not recognize the sequznce as a currecy symbol but as a random "word" - the presence of ZWJ could violate expected data formats (currency amounts largely need to be parsed and processed automatically, they are not just standard text) - these symbols do not belong to any script even if they are most often derived from actual letters from a local script) - users will just prefer using the 3-letter ISO currency code or the name of the currency, or known abbreviations, using more conventional notations for abbreviations that you can detect in text: input with sequnce is just an horror
Anyway, these symbols are not created very often. There's not a lot of currencies in the world. If one country decides changing its currency or assigning it a symbol, it will be announced largely in advance (before it gets legal tender) and the Unicode standard can track this in its yearly updates. Once it is announced, its usage will explode and users will want a simple symbol to be used in lots of context. So these sequences will typically have a temporary usage, at the early time of adoption in the interim time where fonts are still not updated and available in OSes, in contexts were using images or rich text formats allowing the inclusion of web fonts or embedded fonts will not work. But they will not be used in short messaging systems (chat, SMS, twitts...) where abbreviations and ISO currency codes will largely be prefered. 2016-08-04 3:40 GMT+02:00 James Kass <[email protected]>: > Unicode encodes what is or what will be rather than what > might/should/could be. > > The ZWJ character is way to indicate a request for a more joined form of > the two characters surrounding it—at the encoding level. As such, it's > already in place in the standard. The ability to reasonably display > arbitrary combinations depends upon computer software, but such > combinations can already be entered, stored, and exchanged as data. > > Best regards, > > James Kass >
