Re: Fun with UDCs in Shift-JIS

From: David Hopwood (david.hopwood@zetnet.co.uk)
Date: Thu Jan 17 2002 - 18:57:09 EST


-----BEGIN PGP SIGNED MESSAGE-----

Lars Marius Garshol wrote:
> * Lars Marius Garshol
> |
> | The problem is what to do about the rest of the range. Lunde
> | suggests mapping to the Unicode PUA, but I don't think this is what
> | the people using these characters in web pages expect that mapping.
>
> Well, that's what I thought, anyway. But now my Japanese colleagues
> tell me that Japanese users sometimes have to define their own
> characters in their own fonts in order to be able to write some
> characters they may need (for example to write their own name), and
> that the UDCs may be intended for this.

Using an image (with alt tag giving a transliteration, say) is much
better, since it doesn't require anyone to have custom fonts.

However, if anyone wanted to use the PUA for this, NCRs (, etc.)
would be a better way of doing it than relying on any particular mapping
from Shift_JIS to the PUA.

My advice would be not to bother with supporting PUA mappings for WWW
use, and use the Unicode-provided CP932 mapping table for the MIME
charset "Shift_JIS". (Disclaimer: I don't speak Japanese or have much
contact with Japanese users, but if I did I don't think it would change
this opinion, since it's just a straightforward interoperability issue.
Using the CP932 variant as opposed to other variants when reading Shift_JIS
does not create any problems, because the Yen sign can and should be
encoded as "¥" or "¥", and similarly for other characters with
ambiguous mappings.)

- --
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

iQEVAwUBPEdkmjkCAxeYt5gVAQHCNAgAoxJmXBSx8WP0BKjWmUV6YkJrLdbv9B46
Q862X5xNKVBQQGbUvjtbOvf2eSpONCJMLMbeiUPtUPxuqPkjZWKZ/OodNgdgi7GB
q5Cok5/rLSBKsAr/k2PVpe6tA3/st3u2tsztlmx3OWSQ8a3VwAoiRiKO3hmf0Uq0
nOq0ABNO1PJvpu7i4qgnFBEu7Mn3t1nhhcCLRFkoXS03tQCrYRFIxxPzZMqBseQP
1E8IA4iaLkPfLZ9vkBxXCSCIuEp6bXfU8uPmyPrnprUjAuZZ1RTMoGimjlKGbJCD
ZIF5fPd4+emKJEdcspZ2SJKsF4JKCdRx04LU9f9XJSmMQMOIeMx6Pw==
=hbe7
-----END PGP SIGNATURE-----



This archive was generated by hypermail 2.1.2 : Fri Jan 18 2002 - 17:40:47 EST