Bob Rosenberg replied to Antoine Leca:
> > Since Windows starts with the same letter as
> >Word --or is the reason that they both come from the same company.
> >No! I cannot believe that-- there are a couple of requirements
> >that makes effectively the "other" codepages slighty incompatible,
> >such as the necessary presence for · at position B5 (because this
> >is the character Word uses when you ask it to "display" the spaces,
> >and this is hard-coded in the product).
> Last time I looked, B5 was not in the x80-x9F C1 range where CP125x differs
> from ISO-8859-x. Thus this is a non-issue.
Uh, folks, it's 0xB7 = U+00B7 MIDDLE DOT. Encoded, by the way, at
0xB7 in most, but not all, of the 8859 parts: 1, 3, 7, 8, 9, 10, 13, 15, 16;
and in all the Windows 125X code pages. 0xB7 in ISO 8859-2 and 8859-4
is CARON (U+02C7), in 8859-5 is CYRILLIC CAPITAL LETTER ZE (U+0417),
and in 8859-14 is LATIN CAPITAL LETTER P WITH DOT ABOVE (U+1E56).
Perhaps some cognitive dissonance involved here with 0x95 = U+2022 BULLET
in all the Windows 125X code pages (but missing from all the 8859 parts).
This is one of the common Windows characters causing corrupted
display in misidentified 8859-1 display contexts on the Internet.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:05 EDT