-----BEGIN PGP SIGNED MESSAGE-----
Kenneth Whistler wrote:
> Laura Nelson <lnelson@kenan.com> wrote:
> > We have a situation where an important character, the Japanese "wave
> > character", is lost during transfers from various parts of our software.
> > The root cause is that Windows uses a different encoding than does the
> > rest of the world.
>
> Yep, that's right. This is one of the notorious small list of
> inconsistencies between various mappings of JIS X 0208:
>
> Microsoft Code Page 932 mapping:
>
> 0x8160 0xFF5E #FULLWIDTH TILDE
>
> Alternative JIS X 0208 Shift-JIS mapping (e.g. for the Mac):
>
> 0x8160 0x2141 0x301C # WAVE DASH
>
> Actually, the Unicode Consortium does not take (as yet) a formal
> position on which of these conversions is correct.
OTOH, the cross-reference note for U+301C WAVE DASH is:
This character was encoded to match JIS C 6226-1978 1-33
"wave-dash". Subsequent revisions of the JIS standard and
industry practice have settled on JIS 1-33 as being the fullwidth
tilde character.
--> 3030 wavy dash
--> FF5E fullwidth tilde
The Microsoft CP932 mapping is as correct as any of the other mappings
for Shift_JIS, and better thought out than some of them. In this
particular case, it's not "Windows against the world" - the ambiguities
were in the original JIS standards.
> > Data is entered into our database by one program which uses the more
> > standard conversion to UTF8, and then read by another program using the
> > Windows version. It displays as garbage, because the wave character gets
> > lost in the conversion.
That is probably an omission in the Windows *fallback* mappings, not the
mapping to Unicode, then: U+301C should have a fallback mapping to Shift_JIS
0x8160. In any case, if it's a Unicode database then the "other program"
should be displaying the field as Unicode, not trying to map it back to
Shift_JIS, which will certainly fail in general.
- --
David Hopwood <david.hopwood@zetnet.co.uk>
Home page & PGP public key: http://www.users.zetnet.co.uk/hopwood/
RSA 2048-bit; fingerprint 71 8E A6 23 0E D3 4C E5 0F 69 8C D4 FA 66 15 01
Nothing in this message is intended to be legally binding. If I revoke a
public key but refuse to specify why, it is because the private key has been
seized under the Regulation of Investigatory Powers Act; see www.fipr.org/rip
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv
iQEVAwUBPHKTGDkCAxeYt5gVAQF+Wwf/YdnbHZc2R01lUih55aAhDh16fHVWnDcB
CQYqIGFWHRvJkLu4nZBN5MHL8xMiQRolVCcP8dTS7BoCRR83ZxczVDdPmhSVUF3r
67BiaW/EVlIluhUoSIb1XnEgqW5Ch21gSaZeRgc0bO9VaYqG4Wpt2UTDviY2QPtj
K/2BUejYimWMOTtMnYDNc0zWGqndrTHpXcj4QWOV/602OXjJtbGeRJeODdl6ii/7
fkqgJQ/Sf/4C3ksiCv+/xzsnm2JyRqjGBFCRf6VqmLfN5iJ7wXaN9MuiuGIjxcC/
Jn+ou/clQ6n1S4+bUbV2UpPhw18vGPFrjErAJjko/W/iGhJtsn8mrg==
=SH2m
-----END PGP SIGNATURE-----
This archive was generated by hypermail 2.1.2 : Wed Feb 20 2002 - 16:13:23 EST