Re: Various SVG issues
On Sat, Feb 28, 2009 at 3:09 PM, Valentin Villenave wrote: > 2009/2/28 Patrick McCarty : > >> Can you open an issue on the bug tracker for this? I might have more >> things to add as I discover more. > > Look Patrick, I'm sorry but I just can't add this. > > No, really. I have just opened another issue that says *exactly* the > things you told us. > > By the way, would you happen to know the guy who gave me the details I > added to the tracker? He's called Patrick McSomething -- heck, what's > his name already? > http://code.google.com/p/lilypond/issues/detail?id=755 > > :) > > (Yeah, I know what you'll think: "man, this guy has a long way to go > before becoming a new G. Percival") I tried to think of a clever response, but failed. :-) Thanks, Patrick ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \time information is not being output to midi file
2009/2/28 Valentin Villenave :
> 2009/2/28 Marten Visser :
>> I have attached the example and the midi output generated by Lilypond.
>> Opening its midi output using Anvil Studio, displays the meter as 4/4.
>> In addition, I attached the midi modified by Anvil Studio which does display
>> the meter as 3/4.
>
> Hm.
>
> I don't know about midi time sigs, can anyone else verify? This looks
> weird indeed.
>
> % \time information is not rendered in the midi file
>
> \version "2.12.0"
> \score {
> \relative c''' {
> \time 3/4
> g
> }
> \midi { }
> }
I don't have Anvil Studio installed (couldn't get it to work with
Wine), but here's the result of converting the test file's midi output
to midge using midi2mg:
@head {
$tempo 60
$time_sig 3/4
$title "control track"
$resolution 384
}
@body {
@channel 2 "" {
$attack 127
$decay 64
/l4/g6
}
}
As you can see, there doesn't appear to be anything wrong with the
time signature encoding.
Regards,
Neil
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Various SVG issues
2009/2/28 Patrick McCarty : > Can you open an issue on the bug tracker for this? I might have more > things to add as I discover more. Look Patrick, I'm sorry but I just can't add this. No, really. I have just opened another issue that says *exactly* the things you told us. By the way, would you happen to know the guy who gave me the details I added to the tracker? He's called Patrick McSomething -- heck, what's his name already? http://code.google.com/p/lilypond/issues/detail?id=755 :) (Yeah, I know what you'll think: "man, this guy has a long way to go before becoming a new G. Percival") Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 755 in lilypond: SVG backend improvements
Status: Accepted Owner: v.villenave Labels: Type-Defect Priority-Medium OpSys-All New issue 755 by v.villenave: SVG backend improvements http://code.google.com/p/lilypond/issues/detail?id=755 Greetings, I'm opening this issue to gather reports about SVG export problems and ideas on how to improve our SVG backend. In a detailed mail, Patrick McCarty has made several points. These are to be found below, and you may read his mail on http://www.mail-archive.com/bug-lilypond@gnu.org/msg13934.html (you may also want to have a look at Issue 114). " 1.) The `style' attribute should not be used anywhere in an SVG file, as it does not conform to SVG Tiny 1.2. Instead, presentational attributes should be used: font-family, font-style, font-variant, font-weight, text-anchor. 2.) An incorrect font-family name is used when font families have multiple-word names. Adding a comma after the font-family name in PangoFontDescription strings would simplify the regex matching process: it would delimit the font-family from the font-style, font-variant, etc., if included. 3.) Elements should not be grouped with tags. This requires Inkscape users to "ungroup" elements in order to move them around, resize them, etc. 4.) The and elements should be disabled until Inkscape supports them. Possible workarounds: (a) Process only the first page of a multiple-page score, or (b) Process a single page indicated by a new option -dprint-page-number. 5.) LilyPond creates an ill-formed SVG file when processing bach-schenker.ly because scm/output-svg.scm does not have a dashed-slur stencil routine. 6.) `west' is not a valid value for the text-anchor attribute. Valid values include the following: start, middle, end. " -- 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
Various SVG issues
Hi Valentin, I am currently investigating all of the improvements to be made for the SVG backend, and here is the list of issues I have so far: % 1.) The `style' attribute should not be used anywhere in an SVG file, as it does not conform to SVG Tiny 1.2. Instead, presentational attributes should be used: font-family, font-style, font-variant, font-weight, text-anchor. 2.) An incorrect font-family name is used when font families have multiple-word names. Adding a comma after the font-family name in PangoFontDescription strings would simplify the regex matching process: it would delimit the font-family from the font-style, font-variant, etc., if included. 3.) Elements should not be grouped with tags. This requires Inkscape users to "ungroup" elements in order to move them around, resize them, etc. 4.) The and elements should be disabled until Inkscape supports them. Possible workarounds: (a) Process only the first page of a multiple-page score, or (b) Process a single page indicated by a new option -dprint-page-number. 5.) LilyPond creates an ill-formed SVG file when processing bach-schenker.ly because scm/output-svg.scm does not have a dashed-slur stencil routine. 6.) `west' is not a valid value for the text-anchor attribute. Valid values include the following: start, middle, end. % Can you open an issue on the bug tracker for this? I might have more things to add as I discover more. Thanks, Patrick ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [frogs] Re: Doc - explaining layout dimensions
Carl D. Sorensen wrote: 2009/1/11 Graham Percival : Jonathan: another item for you. Frogs, this could be a task for you guys. http://lists.gnu.org/archive/html/bug-lilypond/2009-01/msg00035.html Regards, Valentin Just so you'll know, I took care of this request ages ago when Graham first said "Jonathan another item for you". It's already in the docs just as Mark Polesky requested it. I didn't realize it was marked as a bug. See 4.6.1 in the docs. If it looks like it should, consider the bug squashed. :) Jon -- Jonathan Kulp http://www.jonathankulp.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [frogs] Re: Doc - explaining layout dimensions
Graham Percival wrote: On Sat, Feb 28, 2009 at 05:35:07PM +0100, Valentin Villenave wrote: 2009/2/28 Graham Percival : Yes, absolutely! Jonathan Kulp is handling (or learning how to handle) normal doc updating tasks. I'm not certain if he signed up as a Frog; if he did, this would contribute to this confusion. Actually, I did have Jonathan in mind, more or less, but I CCed to the Frogs list instead to pretend I was not twisting his arm :) Take your lessons from me. Don't ever pretend not to be twisting a specific arm. :) Cheers, - Graham I've missed something along the way b/c I don't recall an arm-twist form Valentin. I'm definitely not a frog b/c I can't write code. I'm happy to be the doc maintainer. I'm finally getting my head around the basics of git and I think now I'll be able to save time for people with push privileges instead of costing them more time. :) That said, I did volunteer also to help with the LSR, but I don't think that makes me a frog. Jon -- Jonathan Kulp http://www.jonathankulp.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [frogs] Re: Doc - explaining layout dimensions
On Sat, Feb 28, 2009 at 05:35:07PM +0100, Valentin Villenave wrote: > 2009/2/28 Graham Percival : > > Yes, absolutely! Jonathan Kulp is handling (or learning how to > > handle) normal doc updating tasks. I'm not certain if he signed > > up as a Frog; if he did, this would contribute to this confusion. > > Actually, I did have Jonathan in mind, more or less, but I CCed to the > Frogs list instead to pretend I was not twisting his arm :) Take your lessons from me. Don't ever pretend not to be twisting a specific arm. :) Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [frogs] Re: Doc - explaining layout dimensions
2009/2/28 Graham Percival : > Yes, absolutely! Jonathan Kulp is handling (or learning how to > handle) normal doc updating tasks. I'm not certain if he signed > up as a Frog; if he did, this would contribute to this confusion. Actually, I did have Jonathan in mind, more or less, but I CCed to the Frogs list instead to pretend I was not twisting his arm :) Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 745 in lilypond: Enhancement: opposing-landscape FretBoard orientation
Updates: Status: Verified Labels: fixed_2_12_2 Comment #1 on issue 745 by v.villenave: Enhancement: opposing-landscape FretBoard orientation http://code.google.com/p/lilypond/issues/detail?id=745 Hmrfmrfmrff, actually it's already been implemented. -- 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: Missing fretboard orientation option
2009/2/28 Carl D. Sorensen : > Actually, it was already applied in 2.12.2. Sorry I didn't let you know. OK. No problem. Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \time information is not being output to midi file
2009/2/28 Marten Visser :
> I have attached the example and the midi output generated by Lilypond.
> Opening its midi output using Anvil Studio, displays the meter as 4/4.
> In addition, I attached the midi modified by Anvil Studio which does display
> the meter as 3/4.
Hm.
I don't know about midi time sigs, can anyone else verify? This looks
weird indeed.
% \time information is not rendered in the midi file
\version "2.12.0"
\score {
\relative c''' {
\time 3/4
g
}
\midi { }
}
Regards,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: wrong number of arguments to font-file-as-ps-string
2009/2/28 Dan Eble : > I tried 2.12.2 just now. All I get is a bus error. I'm sorry I can't > investigate and deeper right now. A bus error is a big deal. This confirms I was right to set a high priority. Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [frogs] Re: Doc - explaining layout dimensions
On Sat, Feb 28, 2009 at 09:05:26AM -0700, Carl D. Sorensen wrote: > I think that Graham wants to draw a distinction between Frogs, whose primary > purpose is to fix bugs in the code, and documentation developers, whose > primary purpose is to improve the documentation. Yes, absolutely! Jonathan Kulp is handling (or learning how to handle) normal doc updating tasks. I'm not certain if he signed up as a Frog; if he did, this would contribute to this confusion. If he *is* a Frog, I'd cautiously recommend that he stops being a Frog and concentrates on doc-maintenance. It's not like we don't have enough doc tasks to occupy one full-time volunteer! Granted, this may require a bit more oversight from me, and this isn't likely to happen for another two weeks... *sigh* ok, realistically not until the end of April... and even then, possibly not until June. :| I have tomorrow off, though, and should only need to spend about four hours on work emails. So I'll try to have a lilypond splurge of my own, to match Valentin's. :) > To a certain extent I created some confusion between the two, because my > initial Frog task was to have people make changes *to the code* that > affected only the documentation, rather than the program functionality. Yes, bad Carl. :P Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [frogs] Re: Doc - explaining layout dimensions
Valentin, I think that Graham wants to draw a distinction between Frogs, whose primary purpose is to fix bugs in the code, and documentation developers, whose primary purpose is to improve the documentation. To a certain extent I created some confusion between the two, because my initial Frog task was to have people make changes *to the code* that affected only the documentation, rather than the program functionality. If Frogs want to work on improving the documentation, nobody is stopping them. And I'd be happy to have any of the frogs take on documentation projects that they're interested in. But the primary goal for Frogs is to work on the code. Thanks, Carl On 2/28/09 6:18 AM, "Valentin Villenave" wrote: > 2009/1/11 Graham Percival : >> Jonathan: another item for you. > > Frogs, this could be a task for you guys. > > http://lists.gnu.org/archive/html/bug-lilypond/2009-01/msg00035.html > > Regards, > Valentin > > --- > > > Join the Frogs! ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Missing fretboard orientation option
Actually, it was already applied in 2.12.2. Sorry I didn't let you know. Thanks, Carl On 2/28/09 6:17 AM, "Valentin Villenave" wrote: > 2008/12/26 Carl D. Sorensen : >> This orientation is doable. We can add it as a new orientation. Let's call >> it opposing-landscape. >> >> Valentin, can you add this to the tracker as a feature request? > > Yyeesss! I'm here! > > http://code.google.com/p/lilypond/issues/detail?id=745 > >> My first thought was that this would have to wait until 2.14, because of the >> syntax change. However, my second thought is that we can do it now, because >> it's *new* syntax, not changed syntax -- no convert-ly rule is necessary. > > Well, now that we're about to start 2.13, the question is no longer relevant > :) > > Regards, > Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 754 in lilypond: \transpose should not affect \transposition
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 754 by v.villenave: \transpose should not affect \transposition
http://code.google.com/p/lilypond/issues/detail?id=754
% new report from Trevor D:
The \transpose command transposes all pitches within its scope, including
the pitch supplied to the \transposition command. This causes incorrect
MIDI output for transposing instruments. The pitch supplied to
\transposition is a constant determined by the instrument and should never
be transposed.
\score {
\transpose c d {
\new StaffGroup <<
\new Staff {
\key c \major
c'1
}
\new Staff {
\transposition bes
\key d \major
d'1
}
>>
}
\layout {}
\midi {} % Should be a unison D, but is not
}
--
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
Issue 754 in lilypond: \transpose should not affect \transposition
Comment #1 on issue 754 by v.villenave: \transpose should not affect \transposition http://code.google.com/p/lilypond/issues/detail?id=754 Oh, and the version is "2.12.2" -- 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: \transpose should not affect \transposition
2009/2/23 Trevor Daniels : > > The \transpose command transposes all pitches within its scope, including > the pitch supplied to the \transposition command. This causes incorrect > MIDI output for transposing instruments. The pitch supplied to > \transposition is a constant determined by the instrument and should never > be transposed. Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=754 Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 753 in lilypond: Extent estimation not accounting for cresc
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 753 by v.villenave: Extent estimation not accounting for cresc
http://code.google.com/p/lilypond/issues/detail?id=753
It seems that system extent estimation does not take into account
(de)crescendi, as is shown on the following example:
% new report from Nicolas:
\version "2.12.2"
\paper {
annotate-spacing = ##t
}
\new Staff { c'4\< c' c' c'\! \break c'4\> c' c' c'\! }
For both systems:
Y-extent = (-10.08 . -0.50)
Y-extent-estimate = (-8.50 . -0.50)
without crescendi, Y-extent is (-8.50 . -0.50).
--
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: Extent estimation not accounting for cresc
2009/2/22 Nicolas Sceaux : > It seems that system extent estimation does not take into account > (de)crescendi, as is shown on the following example: Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=753 Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: wrong number of arguments to font-file-as-ps-string
2009/2/28 James E. Bailey : > Version 2.12.2, OSX 10.4, I get these warnings on any file I process with This has to be an OSX-specific bug then, since I cannot reproduce it here. Added as a high-priority bug at: http://code.google.com/p/lilypond/issues/detail?id=752 Thanks James! Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 752 in lilypond: Pango errors on OSX (table 28333)
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-High OpSys-OSX Usability
New issue 752 by v.villenave: Pango errors on OSX (table 28333)
http://code.google.com/p/lilypond/issues/detail?id=752
We have multiple reports of Pango errors on Mac OSX (reproduced with 10.4
and 10.5) and version 2.12.*
Here is an example: whenever you process any file with chords, e.g.
\version "2.12.2"
\chords { c d e f }
The error log goes:
(process:31063): Pango-WARNING **: Error loading GDEF table 28333
(process:31063): Pango-WARNING **: Error loading GSUB table 28333
(process:31063): Pango-WARNING **: Error loading GPOS table 28333
/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/
scm/framework-ps.scm:293:28: In procedure font-file-as-ps-string in
expression (font-file-as-ps-string name full-name):
/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/
scm/framework-ps.scm:293:28: Wrong number of arguments to #
--
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
Issue 751 in lilypond: Enhancement: automatically gathering keywords in a Language Reference
Status: Accepted Owner: v.villenave Labels: Type-Other Priority-Low New issue 751 by v.villenave: Enhancement: automatically gathering keywords in a Language Reference http://code.google.com/p/lilypond/issues/detail?id=751 http://lists.gnu.org/archive/html/bug-lilypond/2009-01/msg00097.html I'm opening this issue to keep track of Carl's idea of " an automatically-generated language reference that would include all parser keywords, in addition to the identifiers we currently have". Please also read the discussion at http://listengine.tuxfamily.org/lilynet.net/frogs/2009/01/msg00030.html et passim. -- 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: FW: [frogs] Should _all_ lilypond functions be listed in music-functions-init.ly?
2009/1/13 Carl D. Sorensen : > Hi, Valentin, > > Can we get an enhancement request for an automatically-generated language > reference that will include all parser keywords, in addition to the > identifiers we currently have? Hi Carl, Hi Ian, Here goes: http://code.google.com/p/lilypond/issues/detail?id=751 Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: SeparationItem #'padding not working anymore?
2009/2/2 Joe Neeman : > On Fri, 2009-01-30 at 12:21 -0600, Jonathan Kulp wrote: >> Ok Graham. I've been trying for 20 minutes and can't figure how to use >> PaperColumn to change spacing, though. Joe, could you send me a snippet >> that shows how to use this? > > This is very embarrassing, I'm just testing the fix: > > spacing-spanner.cc:306: > set_column_rods (cols, 0.1); // FIXME: padding Greetings Joe, where are we now? Does this SeparationItem thingy deserve an issue in the tracker? Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \time information is not being output to midi file
2009/1/28 Marten Visser : > Dear developers, Greetings and sorry for the delay, > The \time information is not being output to midi file. > See the example. Hmm... /What/ example? :-) Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Linebreak difference between 2.10.33 and 2.12.2
2009/1/26 Andreas Scherer : > The following code produces a single line with Lilypond 2.10.33, but two lines > with Lilypond 2.12.2. Why? (convert-ly only changed the \version number.) > > Cheers, > Andreas Greetings, that's an interesting remark. I think it is because of our new spacing algorithm: since LilyPond is better at avoiding collisions, it must take a bit more space to print the objects. I had noticed that with some other scores; generally speaking I think the new layout is much better than the former one. Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 750 in lilypond: Misleading warning when a Lyrics context is empty
Status: Accepted
Owner: v.villenave
Labels: Priority-Low Type-Defect Warning-nitpick
New issue 750 by v.villenave: Misleading warning when a Lyrics context is
empty
http://code.google.com/p/lilypond/issues/detail?id=750
% When compiling the following example, a warning is printed:
% "warning: cannot find Voice `notes'"
% The expected warning message would be something like:
% "warning: no lyrics found"
% (or, perhaps better, no warning at all)
\version "2.12.1"
<<
\new Staff
\new Voice = "notes" {
c1
}
\new Lyrics \lyricsto "notes" \lyricmode { }
--
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: Misleading warning message when \lyricmode block is empty
2009/1/22 Chris Snyder : > Test case: http://temp.mvpsoft.com/ly/lyric_warning.ly > > When a \lyricmode block is empty, an incorrect warning message is displayed: Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=750 Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 735 in lilypond: Lilypond 2.12 on OSX errors when trying to change a font.
Updates: Status: Verified Labels: Type-Defect Priority-Low fixed_2_12_2 Comment #3 on issue 735 by v.villenave: Lilypond 2.12 on OSX errors when trying to change a font. http://code.google.com/p/lilypond/issues/detail?id=735 (No comment was entered for this change.) -- 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
Issue 749 in lilypond: SpacingSpanner doesn't work when using gregorian.ly
Comment #1 on issue 749 by v.villenave: SpacingSpanner doesn't work when using gregorian.ly http://code.google.com/p/lilypond/issues/detail?id=749 You might also want to read Jiri's report on http://lists.gnu.org/archive/html/bug-lilypond/2009-01/msg00107.html and my answer. -- 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: When gregorian.ly is included, SpacingSpanner does not work.
2009/1/19 Jiri Zurek : > If gregorian.ly is included to the file, the SpacingSpanner stops working, > given spacing is ignored. How does one increase the space between notes then? I assume this is because the gregorian.ly file contains the following code at line 263: \override SpacingSpanner #'packed-spacing = ##t So I guess if you include this file, you might want to revert this setting. (There are a lot of comments in this file, perhaps you might find them useful?) Anyway, I included your report as http://code.google.com/p/lilypond/issues/detail?id=749 Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 749 in lilypond: SpacingSpanner doesn't work when using gregorian.ly
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 749 by v.villenave: SpacingSpanner doesn't work when using
gregorian.ly
http://code.google.com/p/lilypond/issues/detail?id=749
% If gregorian.ly is included in the file, the SpacingSpanner stops
% working, given spacing is ignored.
\version "2.12.1"
\include "gregorian.ly"
chant = \relative c' { f4 a g b a8 f g4( f4) g }
\score {
\new Staff
\new Voice = "chant" \chant
\layout {
\context {
\Score
\override SpacingSpanner #'shortest-duration-space = #8.8
\override SpacingSpanner #'spacing-increment = #0.6
\override SpacingSpanner #'base-shortest-duration = #(ly:make-moment 1 8)
}
}
}
--
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: (attn doc team) Re: Diatonic notation system
2009/1/14 Trevor Daniels : > A mode contains a quarter tone generates the warning: > > D:/Users/Trevor/Leisure/Music/LilyPond/Tests/test1.ly:7:4: warning: No > ordering for key signature alterations Thanks Trevor, you definitely rule! http://code.google.com/p/lilypond/issues/detail?id=748 Sorry for having been unable to process your report any sooner. Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 748 in lilypond: Modes should support quarter-tones
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 748 by v.villenave: Modes should support quarter-tones
http://code.google.com/p/lilypond/issues/detail?id=748
\version "2.12.1"
% A mode that contains a quarter tone generates the warning:
% "warning: No ordering for key signature alterations"
% and if a \midi { } statement is included this error is also generated:
% "lily-library.scm:149:5: Wrong type (expecting exact integer): -1/2"
% Here's a minimal file to demonstrate the problem:
mode = #`((1 . ,SEMI-FLAT))
\score {
\relative c'' {
\key c \mode
c4
}
\layout { }
\midi { }
}
% This example is musical nonsense, but the same construct is
% used, for example, in the bayati mode in ly/arabic.ly, and
% generates similar errors.
--
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
Issue 747 in lilypond: Documentation: automatic music functions documentation
Status: Accepted Owner: v.villenave Labels: Type-Other Priority-Low New issue 747 by v.villenave: Documentation: automatic music functions documentation http://code.google.com/p/lilypond/issues/detail?id=747 I'm opening this issue to keep track of Carl's suggestion: http://lists.gnu.org/archive/html/bug-lilypond/2009-01/msg00096.html Basically, we're looking for "an automatic method of defining @musicFunctionFoo from the docstrings in ly/music-init.ly". Please also have a look at the long discussion on the Frogs list: http://listengine.tuxfamily.org/lilynet.net/frogs/2009/01/msg00031.html et passim. -- 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: FW: [frogs] my contribution: barCheckNumber to endSpanners
2009/1/13 Carl D. Sorensen : > Valentin, > > Can we add an enhancement request for an automatic method of defining > @musicFunctionFoo from the docstrings in ly/music-init.ly? Yes we can :) http://code.google.com/p/lilypond/issues/detail?id=747 Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 746 in lilypond: Source code cleaning: automatic indentation improvement
Status: Accepted Owner: v.villenave Labels: Type-Other Priority-Low New issue 746 by v.villenave: Source code cleaning: automatic indentation improvement http://code.google.com/p/lilypond/issues/detail?id=746 http://lists.gnu.org/archive/html/bug-lilypond/2009-01/msg00095.html I'm opening this issue to help determining the best way to clean our source code. Please also refer to the discussion we've been having with the Frogs: http://listengine.tuxfamily.org/lilynet.net/frogs/2009/01/msg00014.html Basically, what we're looking for is an automatic way to correct all of our source code, depending on the languages and syntax used. -- 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: FW: [frogs] indentation
2009/1/13 Carl D. Sorensen : > Valentin, > > Can you add a feature request for identifying automatic style programs that > will work for each of our source files, defining the necessary syntax files, > and figuring out how to automatically modify the source files? I'm alive! http://code.google.com/p/lilypond/issues/detail?id=746 Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Doc - explaining layout dimensions
2009/1/11 Graham Percival : > Jonathan: another item for you. Frogs, this could be a task for you guys. http://lists.gnu.org/archive/html/bug-lilypond/2009-01/msg00035.html Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Missing fretboard orientation option
2008/12/26 Carl D. Sorensen : > This orientation is doable. We can add it as a new orientation. Let's call > it opposing-landscape. > > Valentin, can you add this to the tracker as a feature request? Yyeesss! I'm here! http://code.google.com/p/lilypond/issues/detail?id=745 > My first thought was that this would have to wait until 2.14, because of the > syntax change. However, my second thought is that we can do it now, because > it's *new* syntax, not changed syntax -- no convert-ly rule is necessary. Well, now that we're about to start 2.13, the question is no longer relevant :) Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 745 in lilypond: Enhancement: opposing-landscape FretBoard orientation
Status: Accepted Owner: v.villenave Labels: Type-Enhancement Priority-Medium New issue 745 by v.villenave: Enhancement: opposing-landscape FretBoard orientation http://code.google.com/p/lilypond/issues/detail?id=745 Please read the full request at http://lists.gnu.org/archive/html/bug-lilypond/2008-12/msg00129.html John Sellers wrote: "The Fretboard orientation allows two options: normal and landscape. The normal view is with the nut at the top, just as if a guitar were placed in the same orientation of the printed Fretboard. The 2.11.65-landscape orientation is similar to the 2.11.65-normal orientation rotated 90 degrees in the sense of a clock facing the observer. Unfortunately the 2.11.65-landscape option produces a image that is upside down to how a conventional guitar play plays a conventional instrument. You see, for most guitarists, a printed fretboard in 2.11.65-landscape the lowest string on the bottom instead of the top, thus possibly causing confusion. On the other hand, a left-handed guitar player with a regular guitar would not be any better off with the notation since the fingerings would have to be different from most players. The practice of one fine, world-class Jazz guitar player is to write the fretboard notation with the nut to the right. This notation would be the same as rotating the current landscape notation by 180 degrees about an axis perpendicular to the paper. This approach makes good sense because Jazz players often play by ear, and they often teach each other by showing each other new fingerings while playing. When the fretboard of another player is observed in this way, for almost all players the nut will appear to be on the observer's right, with the lowest string on the top. From the standpoint of an observer of a guitar player, this most closely matches the before mentioned orientation of rotating the landscape-2.11.65 orientation 180 degrees about an axis perpendicular to the paper. Such players will have long experience in interpreting another players fingering in exactly this orientation, and that experience would make the suggested orientation much easier for them to read." -- 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: LilyPond-mode breaks my XEmacs configuration
2008/12/21 Jerome Berger : > I use XEmacs to edit lilypond sources, but it does not respect my > configuration > preferences. Greetings, Sorry for having left this report unnoticed; I have added a link in our tracker: http://code.google.com/p/lilypond/issues/detail?id=740#c1 By the way, I don't remember having seen you on our French-speaking mailing-list; you might be interested in having a look at http://lists.gnu.org/mailman/listinfo/lilypond-user-fr Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 740 in lilypond: Various Emacs mode problems
Comment #1 on issue 740 by v.villenave: Various Emacs mode problems http://code.google.com/p/lilypond/issues/detail?id=740 Another (X)Emacs problem: http://lists.gnu.org/archive/html/bug-lilypond/2008-12/msg00114.html -- 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: use of Ambitus_engraver in DrumStaff causes program crash
2009/1/11 Graham Percival : >> 2009/1/10 Jesse Engle : >> >> I'm not top posting. >> > >> > % use of Ambitus_engraver in DrumStaff causes program crash > That's not the point -- lilypond should not crash, no matter what > the input*. This is a high-priority bug. Fortunately, this seems to have been fixed since I can't reproduce it with 2.12.2. (Yeah, I'm a bit late, but I'm still in the middle of my de-zombification process.) Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 744 in lilypond: Cross-staff beams do not work well when including rests
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 744 by v.villenave: Cross-staff beams do not work well when
including rests
http://code.google.com/p/lilypond/issues/detail?id=744
% The rest should be printed on the lower staff; instead it floats
% over the upper staff.
% changing \relative c'' into \relative c' makes the bug disappear.
\version "2.12.1"
Up = \change Staff = "up"
Down = \change Staff = "down"
\new PianoStaff <<
\new Staff = "up"
\relative c'' {
\time 6/8
c'8[ \Down c,16 \Up fis \Down r fis] \Up
}
\new Staff = "down" { s4. }
% Might be related to various other cross-staff beam bugs.
Attachments:
beam-rest-bug.png 1.7 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: cross-staff beaming forces rest above the system
2009/1/9 Andrew Hawryluk :
> The r16 in this example should appear in the lower staff ("PrimoLH"),
> but the cross-staff beaming forces it to float above the system.
Thanks, (finally) added as
http://code.google.com/p/lilypond/issues/detail?id=744
Regards,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 743 in lilypond: no more warning for unterminated crescendos
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Low Warning-nitpick
New issue 743 by v.villenave: no more warning for unterminated crescendos
http://code.google.com/p/lilypond/issues/detail?id=743
http://lists.gnu.org/archive/html/bug-lilypond/2009-01/msg00011.html
Alard de Boer has noticed that the following code
{ c-\< c }
produces an "unterminated (de)crescendo" warning with 2.10, but not with
2.12.
--
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: No more "warning: unterminated (de)crescendo" in 2.12?
2009/1/3 Alard de Boer : > Why does "warning: unterminated (de)crescendo" no longer appear in 2.12? I don't know, but I've added it to the tracker just in case (with much delay): http://code.google.com/p/lilypond/issues/detail?id=743 Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 742 in lilypond: Delayed ties influence lyrics (even with tieWaitForNote unset)
Comment #1 on issue 742 by v.villenave: Delayed ties influence lyrics (even with tieWaitForNote unset) http://code.google.com/p/lilypond/issues/detail?id=742 Oh, by the way the version is "2.12.2" -- 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: text missing
2009/1/2 Mats Bengtsson : > James E. Bailey wrote: >> >> Apparently lilypond is a little too smart with delayed ties. > > Is this perhaps even worth a bug report? I've tried to sum this up as http://code.google.com/p/lilypond/issues/detail?id=742 Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 742 in lilypond: Delayed ties influence lyrics (even with tieWaitForNote unset)
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Low
New issue 742 by v.villenave: Delayed ties influence lyrics (even with
tieWaitForNote unset)
http://code.google.com/p/lilypond/issues/detail?id=742
% In the following example, the tie syntax is incorrect but the
% output should not be affected (i.e. the syllables should be printed
% normally).
\relative c'' {
g1~ f g a
}
\addlyrics {
one two three
}
--
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: wrong number of arguments to font-file-as-ps-string
Version 2.12.2, OSX 10.4, I get these warnings on any file I process
with chords, i.e.,
\version "2.12.2"
\chords { c d e f }
generates the following errors.
GNU LilyPond 2.12.2
Procesando «Pango.ly»
Analizando...
Interpretando la música...
Preprocesando los objetos gráficos...
(process:606): Pango-WARNING **: Error loading GDEF table 28333
(process:606): Pango-WARNING **: Error loading GSUB table 28333
(process:606): Pango-WARNING **: Error loading GPOS table 28333
El 28.02.2009, a las 12:33, Valentin Villenave escribió:
2009/1/1 Dan Eble :
2.12.1 on PowerPC on Mac OS X 10.5.6...
(process:31063): Pango-WARNING **: Error loading GDEF table 28333
(process:31063): Pango-WARNING **: Error loading GSUB table 28333
(process:31063): Pango-WARNING **: Error loading GPOS table 28333
/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/
scm/framework-ps.scm:293:28: In procedure font-file-as-ps-string in
expression (font-file-as-ps-string name full-name):
/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/
scm/framework-ps.scm:293:28: Wrong number of arguments to #
Hi Dan,
Have you tried again with the latest 2.12.2 version? What input file
causes such errors? Are you using extra fonts or something?
Regards,
Valentin
___
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
Issue 508 in lilypond: request: support 128 durations
Comment #4 on issue 508 by reinhold.kainhofer: request: support 128 durations http://code.google.com/p/lilypond/issues/detail?id=508 Works fine here... Here the note has 5 flags. -- 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
Issue 741 in lilypond: \displayLilyMusic does not properly handle \harmonic
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Low
New issue 741 by v.villenave: \displayLilyMusic does not properly handle
\harmonic
http://code.google.com/p/lilypond/issues/detail?id=741
\version "2.12.2"
% The following code
\displayLilyMusic \relative c'' { a\harmonic }
% produces the following output:
{ a'-\harmonic a'-\harmonic }
% ... which is erroneous.
--
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
Issue 740 in lilypond: Various Emacs mode problems
Status: Accepted Owner: v.villenave Labels: Type-Other Priority-Low New issue 740 by v.villenave: Various Emacs mode problems http://code.google.com/p/lilypond/issues/detail?id=740 Some users reported indentation problems with the Emacs mode, particularly when using such characters as brackets: http://lists.gnu.org/archive/html/bug-lilypond/2008-12/msg00033.html ... or dashes: http://lists.gnu.org/archive/html/bug-lilypond/2008-12/msg00088.html I don't know who's maintaining this, but it might be a good idea to keep track of such problems here. -- 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
Issue 739 in lilypond: Erratic \bendAfter behavior when another Staff has arpeggios or grace notes
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium
New issue 739 by v.villenave: Erratic \bendAfter behavior when another
Staff has arpeggios or grace notes
http://code.google.com/p/lilypond/issues/detail?id=739
% Except in the first example, the bendAfter curve goes in the
% wrong horizontal direction.
\version "2.12.2"
pianoR = \relative c'' {
c8 c8-\bendAfter #2 c8 c8 c8 c8-\bendAfter #2 c8 c8 |
c8 c8-\bendAfter #2 c8 c8 c8 c8-\bendAfter #2 c8 c8 |
}
pianoL = \relative c' {
4 4 4 4\arpeggio |
4 \grace b8 4 4 \acciaccatura c8 4 |
}
\new PianoStaff <<
\new Staff = "upper" \pianoR
\new Staff = "lower" \pianoL
Attachments:
bendAfter.png 5.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
Issue 59 in lilypond: rest collision engraver should take note durations into account.
Updates: Status: Verified Comment #5 on issue 59 by v.villenave: rest collision engraver should take note durations into account. http://code.google.com/p/lilypond/issues/detail?id=59 (No comment was entered for this change.) -- 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
Issue 217 in lilypond: articulation collides with beam
Updates: Status: Verified Comment #8 on issue 217 by v.villenave: articulation collides with beam http://code.google.com/p/lilypond/issues/detail?id=217 (No comment was entered for this change.) -- 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
Issue 218 in lilypond: center staccato over stem instead of notehead
Updates: Status: Verified Comment #5 on issue 218 by v.villenave: center staccato over stem instead of notehead http://code.google.com/p/lilypond/issues/detail?id=218 Thanks Maximilian! -- 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
Issue 391 in lilypond: using relative filepath in \include "foo.ly"
Updates: Status: Verified Cc: -hanwenn Comment #12 on issue 391 by v.villenave: using relative filepath in \include "foo.ly" http://code.google.com/p/lilypond/issues/detail?id=391 OK, the option is called -drelative-includes and is currently set to #f by default. Uh, since we're about to start 2.13... Well, I'm just sayin'... -- 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
Issue 429 in lilypond: new accidental style: teaching
Updates: Status: Verified Comment #5 on issue 429 by v.villenave: new accidental style: teaching http://code.google.com/p/lilypond/issues/detail?id=429 (No comment was entered for this change.) -- 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: wrong number of arguments to font-file-as-ps-string
2009/1/1 Dan Eble : > 2.12.1 on PowerPC on Mac OS X 10.5.6... > > (process:31063): Pango-WARNING **: Error loading GDEF table 28333 > > (process:31063): Pango-WARNING **: Error loading GSUB table 28333 > > (process:31063): Pango-WARNING **: Error loading GPOS table 28333 > /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/ > scm/framework-ps.scm:293:28: In procedure font-file-as-ps-string in > expression (font-file-as-ps-string name full-name): > /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/ > scm/framework-ps.scm:293:28: Wrong number of arguments to # font-file-as-ps-string (name file-name font-index)> Hi Dan, Have you tried again with the latest 2.12.2 version? What input file causes such errors? Are you using extra fonts or something? Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Harmonic question
2008/12/30 Reinhold Kainhofer :
> \displayLilyMusic \relative c'' { a\harmonic }
>
> will print out:
>
> { a'-\harmonic a'-\harmonic }
> I'm CC'ing the bug list, since I think this should deserve a bug report in our
> tracker ;-)
Yes indeed. Now that I am no longer brain-dead, I've added this as
http://code.google.com/p/lilypond/issues/detail?id=741
Regards,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 441 in lilypond: Very large beginning of measure spacing gap
Updates: Status: Verified Comment #3 on issue 441 by v.villenave: Very large beginning of measure spacing gap http://code.google.com/p/lilypond/issues/detail?id=441 Well done. For the record, the property is named 'full-measure-extra-space, for the NonMusicalPaperColumn object. This is only documented in the IR. -- 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
Issue 454 in lilypond: beamlets have different length
Updates: Status: Verified Comment #10 on issue 454 by v.villenave: beamlets have different length http://code.google.com/p/lilypond/issues/detail?id=454 Looks great now! -- 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
Issue 498 in lilypond: completion heads loses tie
Updates: Status: Verified Comment #6 on issue 498 by v.villenave: completion heads loses tie http://code.google.com/p/lilypond/issues/detail?id=498 (No comment was entered for this change.) -- 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: emacs mode: square brackets confuse indentation
2008/12/17 Paul Scott : > ocd wrote: >> I am having problems with indentation using emacs mode. > I reported a related problem once and didn't get much of a response. (I'm > not complaining considering all the work that is being done on the great > documentation and getting us close to 2.12) Well, let's keep track of your problems at http://code.google.com/p/lilypond/issues/detail?id=740 Please don't hesitate to report any further details or other problems. Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 508 in lilypond: request: support 128 durations
Updates: Status: Started Owner: lemzwerg Labels: -fixed_2_11_66 Comment #3 on issue 508 by v.villenave: request: support 128 durations http://code.google.com/p/lilypond/issues/detail?id=508 Er, Werner, are you sure it works? When compiling Graham's snippet I get an unbeamed quarter-like note... -- 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: bend curve of \bendAfter goes opposite way
2008/12/14 Kongmu : > % bend curve of \bendAfter goes opposite way Thanks, I've finally added it as http://code.google.com/p/lilypond/issues/detail?id=739 Sorry for the delay! Regards, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 517 in lilypond: missing tuplet number in broken tuplet
Updates: Status: Verified Comment #3 on issue 517 by v.villenave: missing tuplet number in broken tuplet http://code.google.com/p/lilypond/issues/detail?id=517 (No comment was entered for this change.) -- 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
Issue 525 in lilypond: repeat tremolo can't force stem downs
Updates: Status: Verified Comment #4 on issue 525 by v.villenave: repeat tremolo can't force stem downs http://code.google.com/p/lilypond/issues/detail?id=525 (No comment was entered for this change.) -- 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
Issue 661 in lilypond: Unwanted TextScript offset when overriding TrillSpanner style
Updates: Status: Verified Comment #5 on issue 661 by v.villenave: Unwanted TextScript offset when overriding TrillSpanner style http://code.google.com/p/lilypond/issues/detail?id=661 (No comment was entered for this change.) -- 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
Issue 683 in lilypond: \paper variable syntax changes
Updates: Status: Verified Comment #4 on issue 683 by v.villenave: \paper variable syntax changes http://code.google.com/p/lilypond/issues/detail?id=683 (No comment was entered for this change.) -- 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
Issue 691 in lilypond: setting \tempo without duration shouldn't print a duration
Updates: Status: Verified Comment #6 on issue 691 by v.villenave: setting \tempo without duration shouldn't print a duration http://code.google.com/p/lilypond/issues/detail?id=691 (No comment was entered for this change.) -- 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
Issue 710 in lilypond: Support for TTCs missing
Updates: Status: Verified Comment #3 on issue 710 by v.villenave: Support for TTCs missing http://code.google.com/p/lilypond/issues/detail?id=710 (No comment was entered for this change.) -- 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
Issue 713 in lilypond: bus error with \bookpart
Updates: Status: Verified Comment #5 on issue 713 by v.villenave: bus error with \bookpart http://code.google.com/p/lilypond/issues/detail?id=713 (No comment was entered for this change.) -- 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
