Unicode control characters: Difference between revisions

Revision as of 06:29, 5 December 2022

Revision as of 02:38, 26 February 2023

Line 30:

These language tag characters would not be displayed themselves. However, they would provide information for text processing or even for the display of other characters. For example, the display of Unihan ideographs might have substituted different glyphs if the language tags indicated Korean than if the tags indicated Japanese. Another example, might have influenced the display of decimal digits 0 through 9 differently depending on the language they appeared in.

The tag characters {{unichar|E0001|LANGUAGE TAG}} and {{unichar|E007F|CANCEL TAG}} were deprecated in Unicode 5.1 (2008) and should not be used for language information.<ref>{{cite documentjournal|url=http://tools.ietf.org/html/rfc6082|title=RFC6082: Deprecating Unicode Language Tag Characters: RFC 2482 is Historic | publisher=Internet Engineering Task Force (IETF)|date=November 2010|last1=Klensin |first1=John C. |last2=Presuhn |first2=Randy |last3=Whistler |first3=Ken |last4=Dürst |first4=Martin J. |last5=Adams |first5=Glenn |editor-first1=R. |editor-last1=Presuhn |doi=10.17487/RFC6082 }}</ref> The characters {{tt|U+E0020—U+E0073}} were also deprecated, but were restored with the release of Unicode 8.0 (2015). The change was made "to clear the way for the potential future use of tag characters for a purpose other than to represent language tags".<ref name="migration">{{cite web|url=http://unicode.org/versions/Unicode8.0.0/#Migration|title=Unicode 8.0.0, Implications for Migration | publisher=Unicode Consortium}}</ref>

Unicode states that "the use of tag characters to represent language tags in a plain text stream is still a deprecated mechanism for conveying language information about text.<ref name="migration" />