i18n and file systems

[Robert Collins]

On Tue, 2005-12-13 at 19:08 +1100, Martin Pool wrote:


> > Some file systems/platforms are unicode through and through - no matter
> > what your terminal encoding is, the file system can still represent and
> > return an unicode path. (Whether python figures this out and uses the
> > appropriate apis is a good question). Examples are NTFS(on win32)
> > (IIRC), and HFS+(with MacOSX). Lets call this unicode safe.
> 
> Linux can approximate this by just declaring that all applications
> *must* pass utf-8 to filesystem calls (or they're broken.)  Or rather, a
> particular distribution could make such a statement. 
> 
> This suggests users might want all paths to be expressed in UTF-8, even
> if they want their terminal and their file contents in ascii or 8859-1.

If they choose to do it, thats fine. Just hope they dont switch to a
utf16 charset or some such. I think that such approximations as you
suggest still leave linux in the 'unicode-sometimes' bin :).

Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051215/056283a8/attachment.pgp