This is the mail archive of the
mailing list for the Cygwin project.
Re: Locales with wrong umlauts
- From: Lapo Luchini <lapo at lapo dot it>
- To: cygwin at cygwin dot com
- Date: Sun, 26 Mar 2006 12:02:59 +0000 (UTC)
- Subject: Re: Locales with wrong umlauts
- References: <email@example.com> <firstname.lastname@example.org> <Pine.GSO.email@example.com>
Igor Pechtchanski <pechtcha <at> cs.nyu.edu> writes:
> On Sun, 27 Jun 2004, A. Alper Atici wrote:
> > try the following:
> > set OUTPUT_CHARSET=iso-8859-1
> Wow. Thanks, this was *extremely* useful. Interestingly enough, the
> OUTPUT_CHARSET option was not mentioned anywhere in the gettext/libintl
> documentation, but a search for it unearthed another couple of messages on
> this list from earlier this year with the same info[*] (one was from you).
Extremely useful to me too, I was quite fed up to see "`a" instead of "Ã" =)
I also noticed that OUTPUT_CHARSET=CP1252 *may* be preferred, compare the
% mtn up
monotone: gi`a aggiornato a '1848d7dfabfbed09fe53856da038e31eed0f42dc'
% OUTPUT_CHARSET=CP1252 monotone up
monotone: giÃ aggiornato a â1848d7dfabfbed09fe53856da038e31eed0f42dcâ
% OUTPUT_CHARSET=ISO8859-1 monotone up
monotone: giÃ aggiornato a `1848d7dfabfbed09fe53856da038e31eed0f42dcÂ
% OUTPUT_CHARSET=ISO8859-15 mtn up
monotone: giÃ aggiornato a '1848d7dfabfbed09fe53856da038e31eed0f42dc'
In order to really "check" it some gettext with an euro symbol should be used,
but I'm not aware of any that does and I don't have the time to create one right
Instead of putting it simply in some FAQ couldn't Cygwin define that env var
correctly "by default"? (after all the system *knows* which charset it is using,
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html