You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2005/12/18 14:55:25 UTC

DO NOT REPLY [Bug 36856] - [email] not support content charset gb2312

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36856>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36856





------- Additional Comments From yoshiyukimikami_20051218@saikyoline.jp  2005-12-18 14:55 -------
(In reply to comment #2)
> From what it looks like, you are basically adding UTF-8 as another charset,
correct?
> 
> At this point we support thre charsets:
>     /** */
>     public static final String KOI8_R = "koi8-r";
>     /** */
>     public static final String ISO_8859_1 = "iso-8859-1";
>     /** */
>     public static final String US_ASCII = "us-ascii";
> 
> I am wondering if there is some sort of master list of charsets we should add.
 If we have KOI8_R, and 
> are now adding UTF-8, what other obscure charsets should we take care off?   

Hello, I'm Japanese.
We usually use "ISO-2022-JP" when using Japanese.
Please add this to list.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org