Re: Adding Big5-1984 to Encode

--WYTEVAkct0FjGQmd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 16, 2004 at 11:20:11PM +0800, imacat wrote:
>     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.=
=20
> If I encode them with CP950 instead, European characters, like ê,
> will be mapped to US-ASCII.  Neither one is acceptable for i18n web
> applications.

Have you investigated the Big5-2003 mapping table?

http://pingyeh.net/big5/big5-2003-v3/summary.txt
http://pingyeh.net/big5/big5-2003-v3/big5-2003-draft-v3.csv

If this works for you, I am in favor of adopting this as the new default
"big5" mapping inside Encode.pm.  If you really need big5-1984, please
send the .ucm file to me and I'll add it to HanExtra.

Thanks,
/Autrijus/

--WYTEVAkct0FjGQmd
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFBmj02tLPdNzw1AaARAmreAKCA6aFcA/cK3iOiCcKv+8+cAMDoFQCeOY+8
s1bzo08xBz6BSUxniMrBGGA=
=2B2D
-----END PGP SIGNATURE-----

--WYTEVAkct0FjGQmd--