[tlug] RE: Tlug Digest, Vol 18, Issue 36

[<burlingk@example.com>]

> Message: 5
> Date: Sun, 17 Jun 2007 13:31:30 -0700
> From: steve smith <sjs@example.com>
> Subject: Re: [tlug] font encoding question
> To: Tokyo Linux Users Group <tlug@example.com>
> Message-ID: <46759A22.6010907@example.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> Brian Chandler wrote:
> > steven smith wrote:
> > 
> > But how will you know what the encoding is?
> Agreed, but it looks like jcode.pm will still be useful.
> > 
> > Actually I believe it is simpler than this. If you have a webpage
> > encoded in UTF-8, you can (*) assume that the browser will 
> return form 
<snip>

> 
> Like they said in that thread, one standard would be nice 
> (though the context was a bit different).  I have to make 
> sure everything I send to friends in Japan is in ISO-2022 or 
> they see ÃââÃÂâÃÅâÃÂâ, but most of the rest of the world (and I 
> think this list usually) is utf-8.  And then there's 
> ISO-8859.  For me, font encoding often seems to do the 
> unexpected.  Augh...
> 
> Thanks for the suggestion and I will use it.
> 
> Steve S.


I would like to see everything move to UTF-8, or even some newer standard that allows for more characters.

It is nice to be able to use one encoding and see most languages without too much trouble. ^_^