Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile

2011-05-26 Thread lilypond
Comment #22 on issue 1562 by jan.nieuwenhuizen: using \sans on Windows gives 'gs' error (2.13.53) fails to compile http://code.google.com/p/lilypond/issues/detail?id=1562 Hmm, what is this? Do you have a virus scanner running? Could you see what happens without it? | 16:23:27.6194889 | gs

Re: Issue 1655 in lilypond: Handles longa in MultiMeasureRest

2011-05-26 Thread lilypond
Updates: Labels: -Patch-new Patch-review Comment #2 on issue 1655 by colinpkc...@gmail.com: Handles longa in MultiMeasureRest http://code.google.com/p/lilypond/issues/detail?id=1655 Applied to 2.15.0, no regressions, whitespace at lines 104 and 113. _

Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile

2011-05-26 Thread lilypond
Comment #21 on issue 1562 by jan.nieuwenhuizen: using \sans on Windows gives 'gs' error (2.13.53) fails to compile http://code.google.com/p/lilypond/issues/detail?id=1562 This zip file just added a new 'Decoding' dir in the C:\Program Files\LilyPond\usr\share\ghostscript\9.02\Resource that a

Re: Issue 1635 in lilypond: clean up misleading warnings in website build

2011-05-26 Thread lilypond
Comment #41 on issue 1635 by percival.music.ca: clean up misleading warnings in website build http://code.google.com/p/lilypond/issues/detail?id=1635 Let's just remove (or comment out) the error. Or, just to be totally ultra-safe, dump a hard-coded list of files without directories: - cha

Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile

2011-05-26 Thread lilypond
Comment #20 on issue 1562 by pkx1...@gmail.com: using \sans on Windows gives 'gs' error (2.13.53) fails to compile http://code.google.com/p/lilypond/issues/detail?id=1562 Jan, Just so I am clear. This zip file just added a new 'Decoding' dir in the C:\Program Files\LilyPond\usr\share\ghosts

Re: Issue 1635 in lilypond: clean up misleading warnings in website build

2011-05-26 Thread lilypond
Comment #40 on issue 1635 by philehol...@googlemail.com: clean up misleading warnings in website build http://code.google.com/p/lilypond/issues/detail?id=1635 They come from extract_texi_filenames.py. It seems to assume that every filename supplied to it also has an associated directory -

Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile

2011-05-26 Thread lilypond
Comment #19 on issue 1562 by jan.nieuwenhuizen: using \sans on Windows gives 'gs' error (2.13.53) fails to compile http://code.google.com/p/lilypond/issues/detail?id=1562 Thanks! The procmon log points at the Decoding/Unicode missing so let's first get rid of that warning. Can you try unpac

Re: Issue 1659 in lilypond: convert-ly should check if it's in a comment or not

2011-05-26 Thread lilypond
Comment #2 on issue 1659 by ggit@gmail.com: convert-ly should check if it's in a comment or not http://code.google.com/p/lilypond/issues/detail?id=1659 I think the optional command should default to "don't update comments". ___ bug-lilypond m

Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties

2011-05-26 Thread lilypond
Updates: Labels: -Patch-review Patch-needs_work Comment #14 on issue 1630 by percival.music.ca: Completion heads engraver produces duplicate ties http://code.google.com/p/lilypond/issues/detail?id=1630 There are a few problems with the patch.

Re: Issue 1635 in lilypond: clean up misleading warnings in website build

2011-05-26 Thread lilypond
Updates: Labels: -Patch-review Comment #39 on issue 1635 by percival.music.ca: clean up misleading warnings in website build http://code.google.com/p/lilypond/issues/detail?id=1635 thanks, patch pushed. One thing left to clean up: NOT A DIR from: /main/src/lilypond/build /home/gpe

Re: Issue 1666 in lilypond: Docs problem: fretted-string-harmonics-in-tablature snippet

2011-05-26 Thread lilypond
Comment #1 on issue 1666 by percival.music.ca: Docs problem: fretted-string-harmonics-in-tablature snippet http://code.google.com/p/lilypond/issues/detail?id=1666 if this is a good change, it needs to be applied to Documentation/snippets/new/ *NOT* Docuementation/snippets/fretted-string-har

Issue 1666 in lilypond: Docs problem: fretted-string-harmonics-in-tablature snippet

2011-05-26 Thread lilypond
Status: Accepted Owner: Labels: Type-Documentation Priority-Medium New issue 1666 by philehol...@googlemail.com: Docs problem: fretted-string-harmonics-in-tablature snippet http://code.google.com/p/lilypond/issues/detail?id=1666 From Federico Bruni: It's not a LilyPond issue (a bug), ju

Re: fretted-string-harmonics-in-tablature snippet

2011-05-26 Thread Phil Holmes
"Graham Percival" wrote in message news:20110525174215.GB28368@futoi... On Tue, May 24, 2011 at 11:33:32AM +0300, Dmytro O. Redchuk wrote: I am a bit lost -- bug? Or not? Federico: Well, i've flagged this thread; let's wait a bit. Well, it's certainly a bugfix. We'd need somebody who knows

Re: Issue 1655 in lilypond: Handles longa in MultiMeasureRest

2011-05-26 Thread lilypond
Comment #1 on issue 1655 by percival.music.ca: Handles longa in MultiMeasureRest http://code.google.com/p/lilypond/issues/detail?id=1655 updated location: http://codereview.appspot.com/4536068/ ___ bug-lilypond mailing list bug-lilypond@gnu.org ht

Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile

2011-05-26 Thread lilypond
Comment #18 on issue 1562 by pkx1...@gmail.com: using \sans on Windows gives 'gs' error (2.13.53) fails to compile http://code.google.com/p/lilypond/issues/detail?id=1562 Jan, the 2.15 file didn't work either - same error meesage --snip-- # -*-compilation-*- Processing `C:/Users/jlowe.DCSW/

Vertical spacing: undesired figured bass stretching

2011-05-26 Thread Nicolas Sceaux
Hi, Here is a problem I face, and for which I could not find a workaround. LilyPond version is current git (it says 2.15.0). This is a regression compared to 2.12 series, where figures are not stretched (as someone reported, I've not tested it myself). Nicolas Début du message réexpédié : > D