Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode

Comment #7 on issue 1688 by lemzw...@googlemail.com: New half-closed hihat symbol for drum mode http://code.google.com/p/lilypond/issues/detail?id=1688 How comes that it suddenly works? Did you do a mistake? ___ bug-lilypond mailing list bug-lil

Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode

Comment #6 on issue 1688 by carl.d.s...@gmail.com: New half-closed hihat symbol for drum mode http://code.google.com/p/lilypond/issues/detail?id=1688 After following up some more, it appears that fontforge 20110222 works properly, so no bug report is needed. However, this provides a good r

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

Il giorno lun, 13/06/2011 alle 20.10 +0200, Janek Warchoł ha scritto: > Hi, > > wish i had not missed this thread and found it earlier... > I found a diff in one of your previous e-mails, but it's kind of > weird, so i'll simply write how things should look. > Hi Janek, thanks for taking care o

Re: Issue 1691 in lilypond: Ugly bars in PDF documents

Comment #2 on issue 1691 by percival.music.ca: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 Technically I suppose that somebody could just manually tweak the line widths of all examples which are too wide, thereby fixing this issue without fixing issue 1

Re: Issue 1691 in lilypond: Ugly bars in PDF documents

Comment #1 on issue 1691 by pkx1...@gmail.com: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 Extra note http://code.google.com/p/lilypond/issues/detail?id=1015 is blocked on http://code.google.com/p/lilypond/issues/detail?id=766 which is postponed I have

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

Hi, wish i had not missed this thread and found it earlier... I found a diff in one of your previous e-mails, but it's kind of weird, so i'll simply write how things should look. 2011/5/24 Federico Bruni : > In the second bar of the snippet > [http://lilypond.org/doc/v2.13/Documentation/snippets

Re: Extracting parts: why does Devnull take as much space as a normal staff ?

2011/6/13 Jean-Charles Malahieude : > - generate a transparent staff of ONE POINT HEIGHT: no way, it still takes > the same vertical space as a regular one. On a quick sight, this could be caused by staff-staff spacing which is still standard, non-null despite of the null extent of your staff. --

Extracting parts: why does Devnull take as much space as a normal staff ?

Hi all, In the book I'm engraving, it happens that some instruments get "tacet" for certain pieces. In order to generate a full table of contents for the parts, I treat them through "Devnull". The problem is that this Devnull context takes as much vertical space as a normal staff of whatever

Issue 1691 in lilypond: Ugly bars in PDF documents

Status: Accepted Owner: Labels: Type-Documentation Priority-Medium New issue 1691 by philehol...@googlemail.com: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 In the documentation build it's common to see an error message beginning "Overfull \hbox".

Re: Issue 1686 in lilypond: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available

Updates: Status: Started Cc: pnorcks hanw...@gmail.com jan.nieuwenhuizen percival.music.ca Comment #1 on issue 1686 by ianhuli...@gmail.com: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available http://code.google.com/p/lilypond/issues