Bug#99933: second attempt at more comprehensive unicode policy
On Sat, 2003-01-11 at 06:21, David Starner wrote:
> You can input any Unicode character you want, but you probably have
> to out of your way to input something outside your charset (i.e. probably
> not on your keyboard or standard IM.)
Ok, that is probably going to be true.
> If I receive a file in the mail whose
> name is not in ASCII (which has never happened to me), I would rename
> it before saving it, so I could access it easily. How many people in a
> Latin-1 locale who got an email with a Chinese file name would want it
> saved with the original name? A simple hash - say, out of charset
> characters to _ - would probably be fine.
Ugg.
> If you're dealing with a web browser, or a mail reader or anything else
> that handles tagged data, it should convert it, of course. Anything else
> should be in the locale charset, and manually recoded if necessary.
> I'm not sure I really understand what you're asking here.
But what if the program *knows* the data is UTF-8 internally? Like all
GNOME programs do, and my patch for dpkg tries to do?
And if my policy proposal is accepted as is, then programs can expect
filenames at least to be UTF-8.
Reply to: