Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Re: KDDI cellphones and encoding
- Date: Fri, 2 Mar 2007 14:42:57 +0900
- From: Wataru Tenga <wtenga@??>
- Subject: Re: [tlug] Re: KDDI cellphones and encoding
- References: <E1HMy03-0007CT-44@example.com> <20070302033447.GA26868@example.com> <20070302135757.b6c035df.wtenga@example.com> <45E7B1C9.80003@example.com>
- Organization: Translator
emiddleton@?? wrote: > The message was > > originally sent as UTF-8 to DoCoMo, but was converted to iso-2022-jp > > either in the cellphone or in DoCoMo's server: > > > > Subject: Fw>èéçæé > > Message-ID: <45e40857.x2$y302twN3@??> > > MIME-Version: 1.0 > > Content-Type: text/plain; charset="iso-2022-jp" > > Content-Transfer-Encoding: 7bit > > > > Try sending something with characters that can't be converted to > iso-2022-jp. You guys are definitely smarter than me. I sent some Chinese as UTF-8 and only the characters that exist in Japanese were displayed normally. And when forwarded from the cellphone, the message was sent as iso-2022-jp. So with DoCoMo, UTF-8 is OK as long as you stick to Japanese. -- Wataru Tenga, Tokyo
- References:
- [tlug] Re: KDDI cellphones and encoding
- From: Jim Breen
- Re: [tlug] Re: KDDI cellphones and encoding
- From: Wataru Tenga
- Re: [tlug] Re: KDDI cellphones and encoding
- From: emiddleton@??
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] stdout redirection
- Next by Date: Re: [tlug] KDDI cellphones and encoding
- Previous by thread: Re: [tlug] Re: KDDI cellphones and encoding
- Next by thread: Re: [tlug] Re: KDDI cellphones and encoding
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links