[Mono-list] MacOS X Charset

John Duncan jddst19@mac.com
Wed, 22 Jan 2003 22:25:34 -0500


All nice and good, but the charset is not being reported as=20
"en_US.ISO8859-1" like it would be on other operating systems. If you=20
have a better idea about how to get the Mac OS X system to report the=20
charset instead of the locale, i'm all ears. I'll send some info to the=20=

fink people in charge of glib and gettext.

On Wednesday, January 22, 2003, at 07:14 PM, Ram Viswanadha wrote:

>>> Um, pertaining to that charset thing. If you want a permanent=20
>>> solution,
>>> put this in your charset.alias file (fink puts it at
>>> /sw/etc/charset.alias)
>>>
>
> No. This is wrong.
> Locale !=3D Charset. Please do not confuse both. Locale provides =
cultural
> sensitive information such as day names, month names, etc. Charset=20
> provides
> a mapping along with an algorithm to bytes to glyphs.
> en_US is a  Locale and UTF-8 is a Charset.
> Please do not modify charset.alias, charset.alias provides a mapping=20=

> between
> the canonical name of a converter to its alias for iconv.
>
> Instead a better way to deal the problem is to set
> LC_ALL or LANG  en_US.UTF-8
>
> For more information on locale naming conventions please see:
> http://www.li18nux.org/localenameguide/index.html
>
> Regards,
>
> Ram
> ---------------------------------------------------
> Ram Viswanadha
> International Components For Unicode
> GCoC San Jose
> IBM
> ----- Original Message -----
> From: "John Duncan" <jddst19@mac.com>
> To: <mono-list@ximian.com>
> Sent: Wednesday, January 22, 2003 2:39 PM
> Subject: Re: [Mono-list] MacOS X Charset
>
>
> Well, you could do "en_US ISO-8859-1"
>
> On Wednesday, January 22, 2003, at 05:28 PM, Gonzalo Paniagua Javier
> wrote:
>
>> El mi=E9, 22-01-2003 a las 22:28, John Duncan escribi=F3:
>>> Um, pertaining to that charset thing. If you want a permanent=20
>>> solution,
>>> put this in your charset.alias file (fink puts it at
>>> /sw/etc/charset.alias)
>>>
>>> en_US UTF-8
>>
>> That doesn't seem a good solution 'cause you won't get correct en_US.
>> Try "en_US en" or "en_US latin1" or something like that.
>>
>> -Gonzalo
>>
>>
>> _______________________________________________
>> Mono-list maillist  -  Mono-list@lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-list
>
> _______________________________________________
> Mono-list maillist  -  Mono-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>
>