Re: convert-ly can't cope with accented filename

2010-01-05 Thread -Eluze 


John Mandereau-2 wrote:
> 
> Le mardi 05 janvier 2010 à 08:03 +1100, Nick Payne a écrit :
>> Try to run convert-ly on a file with an accented name and I get the 
>> following:
>> 
> 
> 
as a little workaround use the shortname of the file with special
characters.

you can find this using the dos command 

  dir /X *.ly
  copy the shortname of the file you want, and
  invoke convert-ly with the pasted shortname

i tried this on windows and it works!
-- 
View this message in context: 
http://old.nabble.com/Re%3A-convert-ly-can%27t-cope-with-accented-filename-tp27024744p27026729.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Issue 960 in lilypond: Enhancement: FretNumbers alignment improvements (wrt dotted durations)

2010-01-05 Thread lilypond 

Status: Accepted
Owner: 
Labels: Type-Enhancement Priority-Low Instrument-specific

New issue 960 by v.villenave: Enhancement: FretNumbers alignment  
improvements (wrt dotted durations)

http://code.google.com/p/lilypond/issues/detail?id=960

New request on the tablatures list:

"""
In a tab chord the dots are placed relatively to the first note in the
chord (or the note on the highest string).
This places the dot too close or too far away to other notes in the chord.
For instance, if the first note in the dotted chord is on fret 9 and the
next note is on fret 10, the dot will be too close to the 10.

I also see that fret numbers in a chord are left justified instead of
centered.  Would it be difficult to center the fret numbers instead of left
justifying them as an option?
"

See also issue 810, and the whole discussion on
http://n2.nabble.com/Dotted-Notes-and-Fret-Number-Alignment-in-Chords-td4216817.html#a4216817

Attachments:
gview.png  1.6 KB

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Strange page breaking issue in 2.13.10

2010-01-05 Thread Reinhold Kainhofer 
Am Dienstag, 5. Januar 2010 00:02:04 schrieb Joe Neeman:
> On Mon, 2010-01-04 at 17:50 +0100, Reinhold Kainhofer wrote:
> > Hi all,
> > I have a score with a full-page title page and several scores. Now,
> > everything fits on 3 pages, but the page breaks are not ideal and I can
> > afford to use 4 pages anyway.
> >
> > So, I insert a force page break before the last score (which takes ~0.66
> > pages originally) to give it its own page and stretch the scores before
> > that from 1.33 pages to 2 pages.
> >
> > Unfortunately, after inserting this forced \pageBreak the scores (except
> > the last), which before took only ~1.33 pages, suddently don't even fit
> > on 2 pages any more, but need 3 pages!
> >
> > Attached is an example of this effect. if you leave the second \pageBreak
> > commented out, everything fits on 3 pages. As in my real score the page
> > breaks are not ideal, I added the \pageBreak before the final score.
> > Simply uncomment that \pageBreak and suddently the score uses 5 pages
> > instead of the expected 4 pages.
> 
> Thanks, this is definitely a bug. As a workaround, set blank-page-force
> and blank-after-score-page-force to zero (the bug, of course, being that
> these variables should have no effect unless you are using the
> page-turn-breaker).

Yes, thanks, this workaround works for now. Of course, in the longer run that 
bug should be tackled. Currently plain vanilla lilypond does not do a proper 
job with page breaks.

Cheers,
Reinhold
 
-- 
--
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: convert-ly can't cope with accented filename

2010-01-05 Thread Bertalan Fodor (LilyPondTool) 

See http://www.amk.ca/python/howto/unicode

John Mandereau wrote:

Le mardi 05 janvier 2010 à 08:03 +1100, Nick Payne a écrit :
  
Try to run convert-ly on a file with an accented name and I get the 
following:


 > convert-ly --edit "/home/nick/lilypond/Bésard_preludio.ly"
convert-ly (GNU LilyPond) 2.13.10
Traceback (most recent call last):
   File "/usr/local/lilypond/usr/bin/convert-ly", line 337, in ?
 main ()
   File "/usr/local/lilypond/usr/bin/convert-ly", line 331, in main
 do_one_file (f)
   File "/usr/local/lilypond/usr/bin/convert-ly", line 233, in do_one_file
 ly.stderr_write (_ ("Processing `%s\'... ") % infile_name)
   File 
"/usr/local/lilypond/usr/share/lilypond/current/python/lilylib.py", line 
59, in stderr_write

 encoded_write (sys.stderr, s)
   File 
"/usr/local/lilypond/usr/share/lilypond/current/python/lilylib.py", line 
51, in encoded_write

 f.write (s.encode (f.encoding or 'utf_8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 33: 
ordinal not in range(128)



This is a bug, the real question for fixing it is: how to figure out the
encoding of the filesystem in Python?

Thanks for the report,
John
  



___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
  


___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond