bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: confused by convert-ly 2.17.5


From: Julien Rioux
Subject: Re: confused by convert-ly 2.17.5
Date: Thu, 25 Oct 2012 04:22:56 -0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1

On 21/10/2012 9:30 AM, Eluze wrote:
bugs:

running without parameters produces 8 errors messages:

convert-ly.py: error: : Unable to open file
convert-ly.py: error: : Unable to open file
convert-ly.py: error: : Unable to open file
convert-ly.py: error: : Unable to open file
convert-ly.py: error: : Unable to open file
convert-ly.py: error: : Unable to open file
convert-ly.py: error: : Unable to open file
convert-ly.py: error: : Unable to open file
convert-ly.py: warning: There were 8 errors.

(I'd expect the help text to display)

for any option - or file - you add there is a reduction of one error.

so invoking

convert-ly -e abc.ly abc.ly  abc.ly abc.ly abc.ly abc.ly abc.ly abc.ly

does not produce any warnings!

------------------------------------

This is ugly. We need to audit the fix for http://code.google.com/p/lilypond/issues/detail?id=1455 more carefully. It affects all python scripts on windows and since it's a GUB fix, all versions built from latest GUB master.

in my cmd I have LANG=en_US.UTF-8
the following command doesn't accept utf-8 characters in the file name:

D:\Data\lytest>convert-ly -e bääh.ly
convert-ly.py (GNU LilyPond) 2.17.5

convert-ly.py: error: b├Á├Áh.ly: Unable to open file
convert-ly.py: error: : Unable to open file
convert-ly.py: error: : Unable to open file
...
...
convert-ly.py: warning: There were 6 errors.



------------------------------

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?

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 taking time to look at this and discuss what should be done!

Eluze


Thanks for testing.

Cheers,
Julien




reply via email to

[Prev in Thread] Current Thread [Next in Thread]