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

List:       kde-devel
Subject:    Re: Q: The dimension of UNICODE awareness
From:       Woohyun JANG <louis () mizi ! co ! kr>
Date:       1999-10-14 9:28:23
[Download RAW message or body]

On Thu, Oct 14, 1999 at 10:15:30AM +0200, Waldo Bastian wrote:
: 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.

Yes, it's true. If I encoded korean filename with normal URL 
encoding method, I couldn't read it.

I know that An URL contains only ASCII, but I hope that KUrl contains 
unicode itself, not encoding it. If KUrl can contain unicode itself, 
many users that use non-latin1 letters can read the URL. :)

And In the IE within the Korean MS Windows, We type Korean letters 
in the URL text field. By doing like this, We can read Korean easily
and can deal it easily too, but it isn't standard. :(

I hacked kfile dialog to use Korean letters in June(it's quite old ^^).
I used unicode itself in the location text field. I think it's easy to
read. :) You can see the screen shot of my hacked kfile dialog in the 
following URL. 

<http://linux.mizi.co.kr/kde/notes/19990609/index.html>

IMHO, to encode unicode stuffs with the normal URL encoding method isn't
good idea, especially for non-latin1 users.

Regards,
-- 
Woohyun JANG, louis@mizi.co.kr                        MIZI Research, Inc.

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