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

List:       kde-devel
Subject:    Re: Q: The dimension of UNICODE awareness
From:       Stefan Taferner <taferner () salzburg ! co ! at>
Date:       1999-10-14 10:34:57
[Download RAW message or body]

On Thu, 14 Oct 1999, Boris Povazay wrote:
> Waldo Bastian wrote:
> 
> > 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?
> 
> URIs are currently either ASCII or interpreted as UTF-8. The following
> paragraph (http://www.w3.org/TR/WD-charmod#URIs) holds the information
> concerning the current status:
[... url encoding specifications ...]

But nevertheless one could show the URLs in Unicode in the user interface
and only encode it when it is really necessary. Read: when interacting with
protocols that do not support it.

There is IMO no need to convert, e.g.,  file://~stefan: the local file system
undestands these characters. And why bother users with some strange
URL encodings.

Just my 0.01 Euro  ... I have no Euro sign yet :-]

--Stefan

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