- From: Bruno Haible <notifications@github.com>
- Date: Mon, 03 Oct 2016 13:41:26 -0700
- To: whatwg/encoding <encoding@noreply.github.com>
Received on Monday, 3 October 2016 20:42:05 UTC
The windows-1255 specified through the spec does NOT map the byte 0xCA. However, the main use of windows-1255 is as a codepage on Windows, and the native Windows converter (function MultiByteToWideChar) maps 0xCA to U+05BA, already since Windows 2000, i.e. for 15 years. On the other hand, the codepage chart at Microsoft https://msdn.microsoft.com/en-us/library/cc195057.aspx marks this position as "not used", and the majority of non-Windows conversion software does not map the byte 0xCA. The implementation of the change would be to edit index-windows-1255.txt, adding a line 74 0x05BA (HEBREW POINT HOLAM HASER FOR VAV) For details of these mapping tables, see http://haible.de/bruno/charsets/conversion-tables/index.html http://haible.de/bruno/charsets/conversion-tables/CP1255.html -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/encoding/issues/73
Received on Monday, 3 October 2016 20:42:05 UTC