Issue 1541 in lilypond: [PATCH] Cleaning Feta flags code (issue4236043)
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 1541 by nez...@googlemail.com: [PATCH] Cleaning Feta flags code (issue4236043) http://code.google.com/p/lilypond/issues/detail?id=1541 http://codereview.appspot.com/4236043/ ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1467 in lilypond: [PATCH] Doc: Rewrite NR 3.2 Titles and headers. (issue3667041)
Comment #3 on issue 1467 by pkx1...@gmail.com: [PATCH] Doc: Rewrite NR 3.2 Titles and headers. (issue3667041) http://code.google.com/p/lilypond/issues/detail?id=1467 hello, if it helps you can make me the owner of this, I will get another draft out in the next couple of days. Jlowe ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1518 in lilypond: DOC: add explanation of part combine functions
Updates: Labels: Patch-new Comment #2 on issue 1518 by nez...@googlemail.com: DOC: add explanation of part combine functions http://code.google.com/p/lilypond/issues/detail?id=1518 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1542 in lilypond: [PATCH] Add springs-and-rods callback to DynamicTextSpanner, so minimum-length has an effect (issue4187054)
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 1542 by nez...@googlemail.com: [PATCH] Add springs-and-rods callback to DynamicTextSpanner, so minimum-length has an effect (issue4187054) http://code.google.com/p/lilypond/issues/detail?id=1542 http://lists.gnu.org/archive/html/lilypond-devel/2011-02/msg00547.html http://codereview.appspot.com/4187054/ ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Too many colliding rests
With the code at the end of this report, I get pretty good output, but get
the following in the log file:
Fitting music on 1 page...
Drawing systems...
warning: too many colliding rests
warning: too many colliding rests
The warnings aren't there unless I have the 3rd voice. Seems like a bug to
me, and I can't find a report on the tracker?
\relative c'{
\new Staff
\new Voice { \voiceOne f'8 f f r f r \oneVoice }
\new Voice { \voiceTwo d,8 d d r d r \oneVoice }
\new Voice { \voiceFour \tieUp a'2~ a \oneVoice }
}
--
Phil Holmes
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Unicode: MUSICAL SYMBOL LEFT REPEAT SIGN
I'm not top posting.
\version 2.12.3
\header {
title = 턆
}
\relative c'' {
c
}
I would like to use the unicode character 턆 (U+1D106, MUSICAL SYMBOL LEFT
REPEAT SIGN) in the text of a stanza. But this results in the error:
“Programmierfehler: Freetype-Fehler: SFNT font table missing”.
Mathias
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Unicode: MUSICAL SYMBOL LEFT REPEAT SIGN
2011/2/25 Mathias Linkerhand proflo...@proflogic.com:
I'm not top posting.
\version 2.12.3
\header {
title = 턆
}
\relative c'' {
c
}
I would like to use the unicode character 턆 (U+1D106, MUSICAL SYMBOL LEFT
REPEAT SIGN) in the text of a stanza. But this results in the error:
“Programmierfehler: Freetype-Fehler: SFNT font table missing”.
I can process your code with no problem under Ubuntu GNU/Linux. The
PDF has that character in the title. What is your OS? Is the error
issued by lilypond or your PDF viewer?
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Too many colliding rests
Phil Holmes mail at philholmes.net writes:
With the code at the end of this report, I get pretty good output, but get
the following in the log file:
warning: too many colliding rests
The warning is not always a false alarm, sometimes LilyPond fails to place the
two rests correctly. I suspect that her rules for placement require keeping
rests away from the line of the third voice, so the warning tells us she cannot
not satisfy all her rules.
\version 2.12
\new Staff
\new Voice { \voiceOne s4 } % just a skip
\new Voice { \voiceTwo d'8 r }
% warning before failure if voiceFour, not so bad if voiceThree.
\new Voice { \voiceFour a'8 r }
%{%}
I suppose desired behavior could be for LilyPond to prioritize collisions over
staying out of the line of the third voice, or something like that, but that
seems more an enhancement request than bug report.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Unicode: MUSICAL SYMBOL LEFT REPEAT SIGN
2011/2/25 Mathias Linkerhand proflo...@proflogic.com: \version 2.12.3 Ubuntu 10.10 amd64. The error is issued by Lilypond. I attached a test.ly to this email. Result: GNU LilyPond 2.12.3 programming error: Free type error: SFNT font table missing -sOutputFile=./test.pdf -c .setpdfwrite -f test.ps' failed (256) Could you try out latest release and tell us whether it works? I can not reproduce it. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Unicode: MUSICAL SYMBOL LEFT REPEAT SIGN
2011/2/25 Francisco Vila paconet@gmail.com: Could you try out latest release and tell us whether it works? I can not reproduce it. It is fair to say, evince issues errors on viewing the PDF in my system, and they are related to the character (obviously): Entity: line 10: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0xF0 0x32 0x33 0x35 1/' dc:format='application/pdf'dc:titlerdf:Altrdf:li xml:lang='x-default' ^ Error: Could not parse ligature component left of left_repeat_sign in parseCharName Error: Could not parse ligature component repeat of left_repeat_sign in parseCharName Error: Could not parse ligature component sign of left_repeat_sign in parseCharName [latest block of 3 lines repeated 4 times] -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Too many colliding rests
Keith OHara k-ohara5...@oco.net wrote in message
news:loom.20110225t211856-...@post.gmane.org...
Phil Holmes mail at philholmes.net writes:
With the code at the end of this report, I get pretty good output, but
get
the following in the log file:
warning: too many colliding rests
The warning is not always a false alarm, sometimes LilyPond fails to place
the
two rests correctly. I suspect that her rules for placement require
keeping
rests away from the line of the third voice, so the warning tells us she
cannot
not satisfy all her rules.
\version 2.12
\new Staff
\new Voice { \voiceOne s4 } % just a skip
\new Voice { \voiceTwo d'8 r }
% warning before failure if voiceFour, not so bad if voiceThree.
\new Voice { \voiceFour a'8 r }
%{%}
I suppose desired behavior could be for LilyPond to prioritize collisions
over
staying out of the line of the third voice, or something like that, but
that
seems more an enhancement request than bug report.
My preference is for all my lily source to compile cleanly, so a warning
when there's actually no problem is annoying. Given the other collisions
that can occur and don't produce a warning, I'd view this warning when
there's no collision as a bug. Low priority, but still a bug.
--
Phil Holmes
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1536 in lilypond: [PATCH] Doc -- Clarify instructions on autobeam settings
Updates: Status: Fixed Owner: Carl.D.Sorensen Labels: fixed_2_13_52 Comment #3 on issue 1536 by carl.d.s...@gmail.com: [PATCH] Doc -- Clarify instructions on autobeam settings http://code.google.com/p/lilypond/issues/detail?id=1536 Fixed in commit 279e858502f36eb2653984fd5f51cecbb7eeb9dc ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
