Re: UTF-8 vs. current locale charset mess...

2000-08-11 Thread Nick Lamb
On Thu, Aug 10, 2000 at 09:24:42PM +0300, Tor Lillqvist wrote: GTK+ 1.3 (and 2.0) uses UTF-8 internally, while the file system related C runtime calls like stat(), open() and opendir() uses a "current codepage" (the Windows term, on Unix you want to use whatever encoding/charset the user's

Re: UTF-8 vs. current locale charset mess...

2000-08-11 Thread Marc Lehmann
On Fri, Aug 11, 2000 at 12:50:12PM +0100, Nick Lamb [EMAIL PROTECTED] wrote: For Linux at least the filesystems speak UTF8. While this is the proposed standard, there exist about zero systems in practise that follow it, and the kernel does neither check nor enforce it. around that without

Re: UTF-8 vs. current locale charset mess...

2000-08-11 Thread Tor Lillqvist
Marc Lehmann writes: "unix", in general, only supports characters from the portable filename character set, so "in theory" there is no problem at all, as characters 127 do not exist in that set. True, but in real life, I would assume most Unix systems are quite happy with using any bytes