Re: [tlug] Japanese Encoding - which one?

[Brett Robson <b-robson@example.com>]

On Thu, 24 Nov 2005 09:16:14 +0100
G畸or Farkas <gabor@example.com> wrote:

> Brett Robson wrote:
>  > 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.
> 
> 
> 2022-JP works fine if you ONLY want to use english + japanese in your mail.
> 
> but what if not?
> 
> just a specific example, my given name is Ga'bor (an accent mark on the 
> [a]). it's sometimes quite inconvenient that i cannot even write my name 
> correctly in an email. because 2022-JP will simply not allow it.
> 
> gabor
> 

I mentioned this 2 posts before:
On 11/24/05, Brett Robson <b-robson@example.com> wrote:
> No, not on my client. Using UTF for for Japanese email breaches RFCs,
> you are supposed to use 2022-JP. Now many people will tell you that it
> doesn't matter and there may be good reason to use it (eg mixing
> Japanese with non-English languages),

Brett



-- 
Brett Robson 
Systems Administrator
GOL, Tokyo. 
http://www.gol.com
050-5527-2554  international: + 81 50-5527-2554