Issue #4073 has been updated by oCameLo oTnTh.


>Anyway I succeeded to generate ucm files from libiconv, so I'll add BIG5-HKSCS:2004.

Big5-HKSCS in libiconv is HKSCS-2008 now:

http://git.savannah.gnu.org/gitweb/?p=libiconv.git;a=commit;h=fd7d5707b506de291acbbefd170281b8226eb379
http://git.savannah.gnu.org/gitweb/?p=libiconv.git;a=blobdiff;f=lib/encodings.def;h=017434351770dabb88f1e4f270eb5933c9f6f92c;hp=b5fda5480f06f4a6160986bddfb7bc48a45dbb78;hb=fd7d5707b506de291acbbefd170281b8226eb379;hpb=8b58085a2a26445b3ec86e811862f3fd4c70eefb

>Just a question,
>
>If you are a real user of Big5-HKSCS, when you use this?
>One time conversion for old data? or communicating with old system?

Unfortunately, not just limited to "old data".

Most computer users don't understand what Encoding is, not even many webmasters. There's also so many web sites use "Big5", they might mean CP950, Big5-HKSCS or Big5-UAO.

Bruno (author of libiconv) said it's a "big mess around Big5", I agree with that ran deep.
----------------------------------------
http://redmine.ruby-lang.org/issues/show/4073

----------------------------------------
http://redmine.ruby-lang.org