Re: confused by convert-ly 2.17.5

[Eluze]

Julien Rioux-2 wrote
> --
> 
> The utf-8 characters are handled fine in my tests, but on windows it 
> might be a completely different thing. Did it work before 2.17.5?

no - here is the full error message:

D:\Data\lytest>"c:\Program Files (x86)\LilyPond2.14.2\usr\bin\convert-ly.py"
bääh.ly
convert-ly.py (GNU LilyPond) 2.14.2
Traceback (most recent call last):
  File "C:\Program Files (x86)\LilyPond2.14.2\usr\bin\convert-ly.py", line
369, in ?
    main ()
  File "C:\Program Files (x86)\LilyPond2.14.2\usr\bin\convert-ly.py", line
356, in main
    do_one_file (f)
  File "C:\Program Files (x86)\LilyPond2.14.2\usr\bin\convert-ly.py", line
243, in do_one_file
    ly.stderr_write (_ ("Processing `%s\'... ") % infile_name)
  File "C:\Program Files
(x86)\LilyPond2.14.2\usr\share\lilypond\current\python\lilylib.py", line 81,
in stderr_write
    encoded_write (sys.stderr, s)
  File "C:\Program Files
(x86)\LilyPond2.14.2\usr\share\lilypond\current\python\lilylib.py", line 57,
in encoded_write
    f.write (s.encode (f.encoding or 'utf-8', 'replace'))
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 13-15:
invalid data


>> when converting a file containing these lines:
>>
>> { a b c d }
>> \version "2.15.0"
>>
>> with convert-ly -e     abc.ly    the new version is 2.17.5 (seems correct
>> to
>> me)
>> with convert-ly -e -d abc.ly    the new version is 2.16.0
>>
>> although no conversion has been applied.
>> shouldn't 2.15.0 be the version after conversion with -d? maybe I'm not
>> understanding correctly
>>
> 
> The logic in the code is to update to the stable version number. Either 
> the description of the -d option or the code needs changing.

thanks for clarifying this - I vote for a small remark in the doc (AU).

with no replies I'll file a doc enhancement request shortly
Eluze




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/confused-by-convert-ly-2-17-5-tp135108p135308.html
Sent from the Bugs mailing list archive at Nabble.com.