No, nothing about what you propose, which is to encode graphics directly with a custom syntax using specific Unicode characters for this syntax itself. There's no such statement in the UTR, even for "longer term". What is proposed instead is a way to *reference* (not "define") graphics. For the rest, you need a rich-text format to embed graphics (using the syntax of this rich-text format, such as HTML), but this syntax remains out of scope of Unicode which will not standardize any graphic format, or any language by its syntax. Even for CLDR, you will use some JSON or XML rich-text format to create references, or embed some small graphics. But CLDR is NOT part of the Unicode Standard itself, and does not encode new characters (and I've not seen the CLDR requesing additions in the UCS for its own use, instead it uses its own assignments for PUAs where needed, als also for its own private locale tags for internal references within the CLDR data itself).
2015-06-02 12:37 GMT+02:00 William_J_G Overington <[email protected] >: > Responding to Philippe Verdy: > > > Nothing has been published. > > It has been published. It is published in this thread for discussion prior > to a possible submission to the Unicode Technical Committee that could > take place if people on this mailing list feel that it is a good solution > to the problem raised in section 8 of the following document. > > http://www.unicode.org/reports/tr51/tr51-2.html > > Direct link to > > 8 Longer Term Solutions > > http://www.unicode.org/reports/tr51/tr51-2.html#Longer_Term > > > William Overington > > 2 June 2015 > >
