On Fri, 2 Feb 2001, Tomohiro KUBOTA wrote:
> Handling locale-encodings without knowing the locale leads to
> problems which I noticed in the last mail, i.e., the 2nd byte
> of multibyte character can hit '/' ...
> Or, you think locale-encodings should be used but multibyte
> encodings cannot be used? It is unfair.
Life is unfair. Not all encodings are created equal. Some are well
designed (UTF-8) and some are badly designed.
It is not unreasonable to put limits on the problem we are trying to
solve, and specifically, to say that we will limit our attention to
well-designed encodings.
Henry Spencer
[EMAIL PROTECTED]
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
- Re: filename encoding Markus Kuhn
- Re: filename encoding (was: ISO-2022) Bram Moolenaar
- Re: filename encoding (was: ISO-2022) Edmund GRIMLEY EVANS
- Re: filename encoding (was: ISO-2022) Tomohiro KUBOTA
- Re: filename encoding (was: ISO-2022) Marcin 'Qrczak' Kowalczyk
- Re: filename encoding (was: ISO-2022) Tomohiro KUBOTA
- Re: filename encoding (was: ISO-2022) Ulrich Drepper
- Re: filename encoding (was: ISO-2022) David Starner
- Re: filename encoding (was: ISO-2022) Tomohiro KUBOTA
- Re: filename encoding (was: ISO-2022) David Starner
- Re: filename encoding (was: ISO-2022) Henry Spencer
- Re: filename encoding (was: ISO-2022) Edmund GRIMLEY EVANS
- Re: filename encoding (was: ISO-2022) Harald Alvestrand
- Re: filename encoding (was: ISO-2022) Edmund GRIMLEY EVANS
- Re: filename encoding (was: ISO-2022) David Starner
- ISO-2022 (Re: filename encoding (was: ISO-2022)) Tomohiro KUBOTA
- Re: ISO-2022 Markus Kuhn
- Re: ISO-2022 Tomohiro KUBOTA
- Re: ISO-2022 Bruno Haible
- XTerm and ISO-2022 Tomohiro KUBOTA
- Re: XTerm and ISO-2022 Robert Brady
