On Fri, Jun 29, 2001 at 02:52:03AM +0200, Bart Lateur wrote:
> On Tue, 19 Jun 2001 14:51:43 -0500, Jarkko Hietaniemi wrote:
>
> >But a locale is a collection of user preferences. How I want
> >my dates to be formatted, how I want my strings to be sorted.
>
> That's not right. If I do a text conversion from Windows to Mac, I would
Arguing with me on this is pointless, take it to the standardizing
bodies :-)
> want to source to use the CP-1522 locale, and the output the MAc-Roman
> locale.
That's not a locale issue. It's a character set conversion issue.
> If I have a file in French, and a file in Chinese, I want one to
> be treated as French, and the other as Chinese.
And what do you do one you have a list of say, employees, with
French, Chinese, and Spanish names, and you want to show them
some order, and how does your fellow Chinese or Hindi worker
want to see the same list ordered...?
Also, please don't confuse locales with 'languages'. To start with,
there's no definition of 'language' that people can agree on. Usually
the existing locale definitions try to work around this fuzziness by
having (language,country) pairs, but that is just a partial solution.
> If this can't be done, I don't need locale's. I'll make my own
> kludges thank you very much.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
