Bug#99933: second attempt at more comprehensive unicode policy
>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?
Then it should be easy to convert it. You can't not convert and expect a
reasonable response - among other things, innocent UTF-8 characters can
include C1 bytes, and screw up an innocent terminal.
>And if my policy proposal is accepted as is, then programs can expect
>filenames at least to be UTF-8.
Not acceptable. Filenames are and must be in the locale charset. There is
no other sane option - what do you expect "echo *" to do? You can't slap
filters around everything; it's horribly buggy, and error-prone and would
take forever to implement, IF everyone wanted to go along with it. The
only sane situation is to transition everything as a whole to UTF-8,
with filterm or the like for legacy terminals. You can't just change
filenames.
Reply to: