On Tue, 15 Sep 1998, Jan Nieuwenhuizen wrote:
> I cannot reproduce the error here:
>
> 10:40:14 appel ~/usr/src/lilypond$ locale
> LANG=nl
> LC_CTYPE="nl"
> LC_NUMERIC=de_DE
> LC_TIME="nl"
> LC_COLLATE="nl"
> LC_MONETARY="nl"
> LC_MESSAGES="nl"
> LC_ALL=
Very strange, I cannot reproduce it with LANG=nl, only when I set all
LC_* variables (or simply LC_ALL) to de_DE, the strange behavior
appears. So please try LC_ALL=de_DE, which will result in the
following settings:
$ locale
LANG=nl
LC_CTYPE="de_DE"
LC_NUMERIC="de_DE"
LC_TIME="de_DE"
LC_COLLATE="de_DE"
LC_MONETARY="de_DE"
LC_MESSAGES="de_DE"
LC_ALL=de_DE
Then I have commas instead of dots in the TeX file.
> GNU LilyPond 1.0.8.
I use 1.0.2 here...
> I don't know too much about the international settings; we use them
> for fun sometimes, but i wasn't aware they are being used for real
> (already).
I don't really need them, but they are there and so I think that it's
a good idea to use and test them, so newcomers (to Unix and English)
will run into a little less problems with them :-)
> Having said that, it sounds logical to me that if you choose to use
> the international numerical settings, you want to get them, i.e.,
> TeX and ghostscript should be fixed rather than lilypond? Ah, i see,
> the numerical setting is probably only for *displaying* to the user.
That's it. You should use locale only for the display and maybe for
comments in generated files, but when you write some machine readable
code, you have to switch back to the international locale LC_ALL=C.
> We should turn it off in Lily (how, anyone?)
I don' know what was changed since the source of 1.0.0 that I have
here, but you have to look for setlocale(). I find a
setlocale(LC_ALL,"") in lily/main.cc and mi2mu/main.cc where
setlocale(LC_MESSAGES,"") is commented out (maybe it would be a good
idea to switch these. Then there is a setlocale() in intl/gcgettext.c,
but I don't see which category is set there.
> > BTW: I used a self compiled lilypond 1.0.0 before and didn't had
> this > problem there. I don't like whether it was introduced in
> 1.0.2 or with > the Debian changes.
> I don't think that anything changed there, since 1.0.0. Any other
> debian users?
My old system was based on Linux libc 5, while the Debian system is
based on glibc 2, which has an improved (or maybe buggy?) locale
support.
But with a global setlocale(LC_ALL,"") there must be trouble, because
every printf will use a wrong decimal separator.
Ciao
Roland
--
* Internet: [EMAIL PROTECTED] * Fido: 2:2450/42 *
PGP: 1024/DD08DD6D 2D E7 CC DE D5 8D 78 BE 3C A0 A4 F1 4B 09 CE AF
