[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Q: The dimension of UNICODE awareness
From:       Waldo Bastian <bastian () suse ! de>
Date:       1999-10-14 8:15:30
[Download RAW message or body]

On Thu, 14 Oct 1999, David Faure wrote:
> On Thu, Oct 14, 1999 at 01:15:48AM +0000, Mirko Sucker wrote:
> > Hello all,
> > I wonder how far we support Unicode in future. Do I have to be aware that
> > filenames and pathes could be handled over in Unicode?
> I think so. I've seen Korean filenames including non-ascii letters.
> We need to model all filenames and paths using QString.
> 
> But I don't know about URLs - the non-ascii chars are encoded, so
> is "const char * url" ok ? We have quite a bit of those...

Yes. An URL contains by definition only ASCII.

> > Does anybody know something about Unix interna regarding this?
> Unix internals use the locale setting, no ? Don't know how
> that copes with more than 256 values though... It
> probably doesn't.

URL's are very bad in handling unicode stuff.. Basically URLs are 8-bit
based. I guess that the only portable way to make a URL of a Unicode
filename is to encode the filename with UTF8 and then encode this UTF8
filename with the normal URL encoding stuff. That means that the URL of
a korean filename looks horrible... even for koreans.

Maybe someone can check if there is an RFC in the making which covers
URLs & Unicode?

Cheers,
Waldo

[prev in list] [next in list] [prev in thread] [next in thread]