Adding Big5-1984 to Encode

[email protected] (imacat) Tue, 16 Nov 2004 23:20:11 +0800
Newsgroups perl.i18n
Message-ID <[email protected]>
--===[PGP/MIME_RFC2015]===419A1AA7.7DB0===
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi all,

    I'm wondering if Big5-1984 can be added to Encode.  I'm developing
web applications, which rely a lot on FB_HTMLCREF.  I found that Big5-eten
and CP950 are incompatible, especially in Japanese and European language
characters.  When FB_HTMLCREF-encoding web pages as Big5-eten, Japanese
hiragana and katakana characters will be mapped to Big5-eten but not
numeric character references, which will not be shown at all under MSIE. 
If I encode them with CP950 instead, European characters, like &ecirc;,
will be mapped to US-ASCII.  Neither one is acceptable for i18n web
applications.

    I agree to use Big5-eten as the standard for Big5 for most
applications, but Big5-1984 should also be available to meet the
requirement of web applications.  Currently I'm doing this locally on my
own, putting Encode::Big51984 according to the instruction in
Encode::Encoding.  But I'm wondering if Big5-1984 can be officially added
to Encode, or Encode::HanExtra.  Of course, it would be best if there
can be some magic for Encode so that it can use Big5-1984 automatically
when running with FB_HTMLCREF, and Big5-eten with others.

--
Best regards,
imacat ^_*' <[email protected]>
PGP Key: http://www.imacat.idv.tw/me/pgpkey.txt

<<Woman's Voice>> News: http://www.wov.idv.tw/
Tavern IMACAT's: http://www.imacat.idv.tw/
TLUG List Manager: http://www.linux.org.tw/mailman/listinfo/tlug

--===[PGP/MIME_RFC2015]===419A1AA7.7DB0===
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32)

iEYEABECAAYFAkGaGqcACgkQi9gubzC5S1xsygCeO+XSFRqMEToS2kKWm9ZBazwu
izIAnAuUIRkWfxDpMIy+KqkeOw+Cou6p
=nA0a
-----END PGP SIGNATURE-----

--===[PGP/MIME_RFC2015]===419A1AA7.7DB0===--