ogg dev - Jan 2008 - Ogg/Kate preliminary documentation

"ogg.k.ogg.k@googlemail.com" <ogg.k.ogg.k@googlemail.com> wrote:
...
> > * don't bother with non-UTF8
>
> Yes, I was going to leave it as is while keeping the header field there,
> just in case. I do know, however, that people in eastern countries tend
> to dislike utf-8 for the size it takes for their language, as it's
been, er...
> /optimized/ for the latin alphabet. I am also not clear if every code point
> can be coded in utf-8, I'll have to dig that up.
Every code point can be coded in UTF-8.  As
you point out, when your character set contains
many characters (eg, Chinese and Japanese)
then UTF-8 becomes inefficient and UTF-16
uses less space.

Unless space is at a premium then allowing
only UTF-8 is reasonable.  A header also buys
you future proofing for little cost.

Regards,
Martin
-- 
Martin J Leese
E-mail: martin.leese@stanfordalumni.org
Web: http://members.tripod.com/martin_leese/

On Wed, Jan 16, 2008 at 04:02:35PM -0700, Martin Leese wrote:
> Unless space is at a premium then allowing
> only UTF-8 is reasonable.  A header also buys
> you future proofing for little cost.
There are also some schemes for appending a character encoding to a 
locale string.

 -r

> Every code point can be coded in UTF-8.  As
Ah, thank you for the clarification.
> Unless space is at a premium then allowing
> only UTF-8 is reasonable.  A header also buys
> you future proofing for little cost.
It looks more and more like I'll keep it as it is then.

BTW, thank you for the cleanup on the documentation page
on the wiki, I'd just dumped the file I had on my hard drive,
and I'm not too used to wikis. Much appreciated.