Does GnuPG consider supporting more charsets?

[Zuxy]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

I reckon lacking support for a specific display charset won't cause
much trouble among users using the same language, because one
language will mostly have only one common encoding beside utf-8.

But for CJK (Chinese, Japanese and Korean), there're usually more
than one encoding. For Chinese there're GB2312 (whose extension is
GB18030, used in the Mainland), HZ (used in Hong Kong) and Big5 (used
in Taiwan), so email users across the Taiwan strait do need utf-8 as
an intermedium when sending encryped messages, if they don't know
about PGP/MIME.

Now GnuPG doesn't know about either GB2312 or Big5, and therefore
treats the input as utf-8, and applies no conversion:
Message encoded in GB2312 --> (gpg encrypting) --> Message decoded in
Big5
So the Taiwanese receiptor will have an unreadable message.

How does the current version of GnuPG handle the conversion between
display charsets and utf-8? Thru libiconv or an internal translation
table? And what will the upcoming GnuPG 1.4 do? If GnuPG use
libiconv, I hope there won't be much work adding support for more
display charsets.

Thanks.

- --
Zuxy
Beauty is truth,
While truth is beauty.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.90 (MingW32) - WinPT 0.9.12

iF0EAREDAB0FAkFqpWEWGGhrcDovL3N1YmtleXMucGdwLm5ldAAKCRDvAMJ46FVe
1hjRAKCSPHiUYPBJwTFeNuoy4JVM1u6r0gCg239hG5iFHKoK5syCRcVVxeDABgM=
=/N0i
-----END PGP SIGNATURE-----