Le lundi 02 juillet 2007 à 21:58 -0300, Han-Wen Nienhuys a écrit :
> 2007/7/2, John Mandereau <[EMAIL PROTECTED]>:
>
> > To fix this, we must use ugettext instead of gettext in lilylib.py.
> > Unfortunately, this fix implies that each gettexted string must be
> > converted from Python internal Uni
Hi,
I've hit character encoding issues when calling lilypond-book compiled
locally. It seems that optparse implementation has changed between
Python 2.4 and 2.5 in a way that OptionParser.print_help wants to
convert string encoding before writing to stdout. The problem is,
Python knows only two
2007/7/2, John Mandereau <[EMAIL PROTECTED]>:
To fix this, we must use ugettext instead of gettext in lilylib.py.
Unfortunately, this fix implies that each gettexted string must be
converted from Python internal Unicode to stdout/stderr encoding before
being written to stdout/stderr.
May I comm
Hi,
I've hit character encoding issues when calling lilypond-book compiled
locally. It seems that optparse implementation has changed between
Python 2.4 and 2.5 in a way that OptionParser.print_help wants to
convert string encoding before writing to stdout. The problem is,
Python knows only two
