On Feb 14 15:56, Andrey Repin wrote: > > But this is a problem not different from Linux. If you have a username > > with non-ASCII chars, it will use *some* encoding in the passwd DB, > > usually UTF-8 these days. If you then change the codeset in your > > application, you will still get your username in UTF-8. It won't be > > changed on the fly, just because your application calls setlocale. > > I understand it (mostly), but there's actually two issues, not one. > One issue is the display part, where names are output for user consumption. > Another can be observed in, i.e., rsync, and file access in general (remember > the discussion about accessing long directory names in unicode). > Changing LANG variable DO matter for the latter, and you may only hope that > whatever is output in the former case is actually printable (thank God, most > of the time it actually is, in case of UTF-8). > It is getting even more complicated, when you consider the fact, that in > Windows you have 2 different single-byte encodings, so-called ANSI (for GUI > applications) and OEM (for console). And alot of stuff making assumptions > without consulting with current status of things. > As convoluted the problem is, I think, we need some sort of solution, or at > the very least - documentation.
Sorry, I can't provide an easy solution, and afaik this is documented. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgpZ3vu7Qf_va.pgp
Description: PGP signature
