mailto:[email protected] wrote:
> If someone tried to make a Win32 console implementation and tried to > implement both Windows 9x Arabic terminal character set compatibility > and wide string API (ReadConsoleOutputW) compatibility simultaneously, > then they would run into the issue that there is currently no > standardized mapping to handle that scenario. What should Windows 9x > Arabic console compatible implementations do in that case? Unicode (the organization) is no longer in the business of trying to publish definitive and normative mappings between Unicode (the character repertoire) and legacy character sets. However, ICU — a Unicode project — does make available an extensive set of informative mapping tables that may help: https://icu.unicode.org/charts/charset These tables may include some private-use mappings, although I didn’t spot any in a quick scan of the table for IBM’s interpretation of CP720. The usual conditions apply: “characters” that appear in legacy charsets, but which are just fragments or positional glyphs in the Unicode sense, might not have official mappings to Unicode, and the fact that they might have been given such mappings and/or encoded as characters 35 years ago does not serve as a precedent for encoding them today. -- Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org
