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] Japanese Encoding - which one?
- Date: Thu, 24 Nov 2005 17:56:02 +0900
- From: Evan Monroig <evan@example.com>
- Subject: Re: [tlug] Japanese Encoding - which one?
- References: <20051124131433.0039.B-ROBSON@example.com> <e28811080511232150o11742312ge965692dd3a58e48@example.com> <20051124151805.0041.B-ROBSON@example.com>
Thanks for answering ^^. As you say, email must be sent in 7bit text, and when it is 8 bit it must be encoded to Base64 or Quoted-Printable for transport. In all case you will need MIME headers, and after reading RFC1468 whose link you sent us, I understood that ISO-2022-JP is 7bit by nature, so there is no need to encode it before transport. By the way, the RFC described only what is ISO-2022-JP, not if we should/must use it or not... Now when we say that ISO-2022-JP is better for Japanese, what it means (I guess) is that some devices/software cannot understand anything else... But because of that, we can't communicate using those devices/software in other languages... In my emails I like to mix French and Japanese, and there is no way that I can do that with my cellphone or with (French-speaking !) japanese users of hotmail... (and with French I am quite lucky most letters are ASCII.) Evan On 11/24/05, Brett Robson <b-robson@example.com> wrote: > > On Thu, 24 Nov 2005 14:50:47 +0900 > Evan Monroig <evan.monroig@example.com> wrote: > > > Why do you say so? Which RFC's does it break? > > (Brett I don't mean to attack you I was just really surprised by what > > you said ;)) > > > Email is supposed to be sent in 7bit text (ie printable), UTF needs to > be MIME encoded. > > I can't see Lyle's email as it was originally sent as this appears in > the header > X-MIME-Autoconverted: from 8bit to quoted-printable by > rcpt-mqugw.biglobe.ne.jp id jAO2U7ix029878 > His original email was sent as MIME encoded UTF so that satisifies > RFC822(?). Then rcpt-mqugw.biglobe.ne.jp turned it into plain text > base64. Not sure if that is strictly adhering to the RFCs or not. > > But RFC 1468 "Japanese Character Encoding for Internet Messages" > http://www.ietf.org/rfc/rfc1468.txt > says that Japanese text should be sent in 2022-JP encoding. So if you > don't use 2022-JP you run the risk of clients not being able to read it. > I intentionally use Becky which doesn't read UTF mail for checking > the encoding in emails being sent out from work. > > Brett
- References:
- Re: [tlug] Japanese Encoding - which one?
- From: Brett Robson
- Re: [tlug] Japanese Encoding - which one?
- From: Evan Monroig
- Re: [tlug] Japanese Encoding - which one?
- From: Brett Robson
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Japanese Encoding - which one?
- Next by Date: Re: [tlug] Japanese Encoding - which one?
- Previous by thread: Re: [tlug] Japanese Encoding - which one?
- Next by thread: Re: [tlug] Japanese Encoding - which one?
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links