[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Trying out the new escaping version...

From: Jan Hudec
Subject: Re: [Gnu-arch-users] Trying out the new escaping version...
Date: Thu, 18 Mar 2004 16:23:07 +0100
User-agent: Mutt/

On Thu, Mar 18, 2004 at 16:02:46 +0100, address@hidden wrote:
> > On Thu, Mar 18, 2004 at 11:32:38 +0100, address@hidden wrote:
> > > Next: the escaped version still only accepts 7bit ascii [...]
> > 
> > I understand how hard it is to lift this. It would be extremely nice
> > if it could accept high characters. I mean \(U+0100) and higher, since
> > I have ISO-8859-2 encoding here. It, of course requires two things:
> > 
> >     1) Proper charset conversion to/from charset detected from locale.
> >     2) Some sane fallback what to do when a character can't be
> >     converted.
> > 
> > The second thing it the hardest part of it. I can imagine:
> >     a) It won't work with such filenames, that is you won't be able to
> >        checkout weird things if your locale does not support it
> >        (workaround -- LC_CTYPE=<something>.UTF-8 tla ...)
> >     b) It will not convert escapes that can't be converted. This would
> >        be very nice, but it disallows valid unicode escape sequences
> >        in filenames -- file '\(U+E1)' would be the same as file 'รก'.
> > Perhaps someone will get a better idea.
> It is prepared to use utf-8 in future, but you got it right, there is
> still alot to do to make tla unicode aware. Until then it is limited to
> 7bit ascii. Just go ahead and code the stuff or wait for it (or fund
> some development on that issue).

Sure it is. I briefely looked at the code. I just wanted more people to
think of it before I or anybody else starts to code it, so the result is
designed sanely.

                                                 Jan 'Bulb' Hudec 

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]