Re: SeparationItem #'padding not working anymore?
On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave v.villen...@gmail.com wrote: 2009/2/2 Joe Neeman joenee...@gmail.com: 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? I don't think it deserves an issue. We have two options: 1) Remove SeparationItem from LilyPond's source (scm/define-grobs.scm). Then we would need a convert-ly rule. 2) Keep SeparationItem, even though it is never used. I guess it all depends on whether SeparationItem will ever be used again in the future. -Patrick ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: SeparationItem #'padding not working anymore?
Quoting Patrick McCarty pnor...@gmail.com: On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave v.villen...@gmail.com wrote: 2009/2/2 Joe Neeman joenee...@gmail.com: 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? I don't think it deserves an issue. We have two options: 1) Remove SeparationItem from LilyPond's source (scm/define-grobs.scm). Then we would need a convert-ly rule. 2) Keep SeparationItem, even though it is never used. I guess it all depends on whether SeparationItem will ever be used again in the future. The main thing is that the documentation is modified to show a solution that works, i.e. that gives the same result as you previously could obtain setting SeparationItem #'padding = ... You raise a completely different question, namely what the general strategy is for phasing out obsolete properties/engravers/grobs. This is far from the first time, such things happen, and previously it has often taken quite some time before somebody really has taken the effort to clean it up properly (removing the corresponding source code and documentation and adding a convert-ly rule). /Mats ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: SeparationItem #'padding not working anymore?
On Sun, Mar 1, 2009 at 12:17 AM, Mats Bengtsson mats.bengts...@ee.kth.se wrote: Quoting Patrick McCarty pnor...@gmail.com: On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave v.villen...@gmail.com wrote: Greetings Joe, where are we now? Does this SeparationItem thingy deserve an issue in the tracker? I don't think it deserves an issue. We have two options: 1) Remove SeparationItem from LilyPond's source (scm/define-grobs.scm). Then we would need a convert-ly rule. 2) Keep SeparationItem, even though it is never used. I guess it all depends on whether SeparationItem will ever be used again in the future. The main thing is that the documentation is modified to show a solution that works, i.e. that gives the same result as you previously could obtain setting SeparationItem #'padding = ... Ah, yes. I forgot that the documentation was not updated to reflect the change. Joe added a regtest called spacing-paper-column-padding.ly that demonstrates the new behavior. -Patrick ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: SeparationItem #'padding not working anymore?
Patrick McCarty wrote:
On Sun, Mar 1, 2009 at 12:17 AM, Mats Bengtsson
mats.bengts...@ee.kth.se wrote:
Quoting Patrick McCarty pnor...@gmail.com:
On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave
v.villen...@gmail.com wrote:
Greetings Joe,
where are we now? Does this SeparationItem thingy deserve an issue in
the tracker?
I don't think it deserves an issue.
We have two options:
1) Remove SeparationItem from LilyPond's source
(scm/define-grobs.scm). Then we would need a convert-ly rule.
2) Keep SeparationItem, even though it is never used.
I guess it all depends on whether SeparationItem will ever be used
again in the future.
The main thing is that the documentation is modified to show a solution that
works, i.e. that gives the same result as you previously could obtain
setting SeparationItem #'padding = ...
Ah, yes. I forgot that the documentation was not updated to reflect the change.
Joe added a regtest called spacing-paper-column-padding.ly that
demonstrates the new behavior.
-Patrick
I'll update the docs to reflect the change. Couple of questions first,
though.
1. The regtest mentioned above has two overrides, but as far as I can
tell only one of them has any effect. Unless I'm missing something,
only the NonMusicalPaperColumn affects the spacing. If it's commented
out, the spacing goes back to normal, but if the PaperColumn padding
override is commented out and the NonMusicalPaperColumn override is
kept, the spacing changes. Here's my minimal example made from it:
\relative c' {
% \override Score.PaperColumn #'padding = #10
\override Score.NonMusicalPaperColumn #'padding = #10
c d
}
There might be a good reason to include the first override, a reason not
evident in such a tiny example, so maybe someone with more knowledge can
tell me whether to keep it in there.
2. Doc policy discourages (forbids?) the use of @example, which is
currently how this issue is addressed in NR 4.5.1 known issues and
warnings. It would be easy enough to change the @example currently
there to show the NonMusicalPaperColumn override, but this would
perpetuate a breach of doc policy. On the other hand, lilypond examples
with overrides are also forbidden in the main text, so this would have
to go into a snippet. Should I go ahead and quick-fix the @example
until a snippet can be added to the snippet list and then later make a
link to the snippet?
Thanks,
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
Hi all,
Graham Percival wrote:
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!
OK: how about nick-naming the apprentice documenters like Newts (that way, we
all still count as pond-life {:===:}.
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.
Nevertheless, the docs bugs/feature requests still need to be tracked so Jon
the Newt would still need to learn the processes for this _and_ people in his
role are still the target audience for the Contributor's Guide (CG).
Yes, bad Carl. :P
Cheers,
- Graham
Cheersssh
Ian
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: SeparationItem #'padding not working anymore?
On Sun, Mar 01, 2009 at 07:24:53AM -0600, Jonathan Kulp wrote: 2. Doc policy discourages (forbids?) the use of @example, which is currently how this issue is addressed in NR 4.5.1 known issues and warnings. It would be easy enough to change the @example currently there to show the NonMusicalPaperColumn override, but this would perpetuate a breach of doc policy. Go ahead and keep the @example; NR 4 still needs to start its rewrite. This goes for anything else you see in NR 3 and upwards... I don't see this situation changing until the summer. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: SeparationItem #'padding not working anymore?
Patch attached.
Jon
On Sun, Mar 1, 2009 at 8:11 AM, Graham Percival gra...@percival-music.cawrote:
On Sun, Mar 01, 2009 at 07:24:53AM -0600, Jonathan Kulp wrote:
2. Doc policy discourages (forbids?) the use of @example, which is
currently how this issue is addressed in NR 4.5.1 known issues and
warnings. It would be easy enough to change the @example currently
there to show the NonMusicalPaperColumn override, but this would
perpetuate a breach of doc policy.
Go ahead and keep the @example; NR 4 still needs to start its
rewrite. This goes for anything else you see in NR 3 and
upwards... I don't see this situation changing until the summer.
Cheers,
- Graham
--
Jonathan Kulp
http://www.jonathankulp.com
From 29ad4b14a13313d37f68131ddc70f26af94bbba7 Mon Sep 17 00:00:00 2001
From: Jonathan Kulp jonlancek...@gmail.com
Date: Sun, 1 Mar 2009 08:47:38 -0600
Subject: [PATCH] change SeparationItem @example to NonMusicalPaperColumn
---
Documentation/user/spacing.itely |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/user/spacing.itely b/Documentation/user/spacing.itely
index bacbc94..9f5be80 100644
--- a/Documentation/user/spacing.itely
+++ b/Documentation/user/spacing.itely
@@ -1915,15 +1915,16 @@ Internals Reference:
@rinternals{SpacingSpanner},
@rinternals{NoteSpacing},
@rinternals{StaffSpacing},
-...@rinternals{separationitem}.
+...@rinternals{nonmusicalpapercolumn}.
@knownissues
There is no convenient mechanism to manually override spacing. The
-following work-around may be used to insert extra space into a score.
+following work-around may be used to insert extra space into a score,
+adjusting the padding value as necessary.
@example
- \once \override Score.SeparationItem #'padding = #1
+ \override Score.NonMusicalPaperColumn #'padding = #10
@end example
No work-around exists for decreasing the amount of space.
--
1.5.4.3
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Naming output files
2009/2/26 Reinhold Kainhofer reinh...@kainhofer.com It would actually be quite simple to implement: In scm/lily-library.scm in the print- book-with function, instead of storing the file count as a number in 'output-count, store it in an alist (which is set as the 'output-count parser variable), with the suffix as key. This way, the counting is per suffix and we'll automatically not append the number for the first file with a given suffix... I think this would be quite a nice task or a frog, so I'm not coding it myself, just giving a few pointers... The way to work with the alist (that's Scheme's idea of a Hash) can be seen e.g. in my counter snippet on LSR: http://lsr.dsi.unimi.it/LSR/Item?id=543 All you need to do is to use assoc-ref instead of count and ly:parser-define! (instead of the set! in the counter example) with assoc-set! to set one entry of the hash / alist. The key for the alist would be the suffix. The rest of the function doesn't even need to be changed... Here is my solution: (define counter-alist '()) (define (print-book-with parser book process-procedure) (let* ((paper (ly:parser-lookup parser '$defaultpaper)) (layout (ly:parser-lookup parser '$defaultlayout)) (output-count (assoc-ref counter-alist 'output-suffix)) (base (ly:parser-output-name parser)) (output-suffix (ly:parser-lookup parser 'output-suffix)) ) (if (string? output-suffix) (set! base (format ~a-~a base (string-regexp-substitute [^a-zA-Z0-9-] _ output-suffix ;; must be careful: output-count is under user control. (if (not (integer? output-count)) (set! output-count 0)) (if ( output-count 0) (set! base (format #f ~a-~a base output-count))) (set! counter-alist (assoc-set! counter-alist output-suffix (1+ output-count))) (process-procedure book paper layout base) )) I didn't use ly:parser-define! instead of the set! (I couldn't make it to work). The output-count variable is no more under user control this way. Please do comment. -- Marek Klein http://gregoriana.sk ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: SeparationItem #'padding not working anymore?
Mats Bengtsson wrote Sunday, March 01, 2009 8:17 AM Quoting Patrick McCarty pnor...@gmail.com: On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave v.villen...@gmail.com wrote: 2009/2/2 Joe Neeman joenee...@gmail.com: 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? I don't think it deserves an issue. We have two options: 1) Remove SeparationItem from LilyPond's source (scm/define-grobs.scm). Then we would need a convert-ly rule. 2) Keep SeparationItem, even though it is never used. I guess it all depends on whether SeparationItem will ever be used again in the future. The main thing is that the documentation is modified to show a solution that works, i.e. that gives the same result as you previously could obtain setting SeparationItem #'padding = ... Yes, we're waiting for Joe to complete his fix so we can use 'spacing-spanner in the docs. At present no one has found a way to make it work. Or has this been fixed silently? Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: SeparationItem #'padding not working anymore?
Thanks Jon. Pushed to git. Trevor - Original Message - From: Jonathan Kulp jonlancek...@gmail.com To: Graham Percival gra...@percival-music.ca Cc: Joe Neeman joenee...@gmail.com; Lilypond bug bug-lilypond@gnu.org; Mats Bengtsson mats.bengts...@ee.kth.se Sent: Sunday, March 01, 2009 2:51 PM Subject: Re: SeparationItem #'padding not working anymore? Patch attached. Jon On Sun, Mar 1, 2009 at 8:11 AM, Graham Percival gra...@percival-music.cawrote: On Sun, Mar 01, 2009 at 07:24:53AM -0600, Jonathan Kulp wrote: 2. Doc policy discourages (forbids?) the use of @example, which is currently how this issue is addressed in NR 4.5.1 known issues and warnings. It would be easy enough to change the @example currently there to show the NonMusicalPaperColumn override, but this would perpetuate a breach of doc policy. Go ahead and keep the @example; NR 4 still needs to start its rewrite. This goes for anything else you see in NR 3 and upwards... I don't see this situation changing until the summer. Cheers, - Graham -- Jonathan Kulp http://www.jonathankulp.com ___ 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
Re: SeparationItem #'padding not working anymore?
On Sun, 2009-03-01 at 15:38 +, Trevor Daniels wrote: Mats Bengtsson wrote Sunday, March 01, 2009 8:17 AM Quoting Patrick McCarty pnor...@gmail.com: On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave v.villen...@gmail.com wrote: 2009/2/2 Joe Neeman joenee...@gmail.com: 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? I don't think it deserves an issue. We have two options: 1) Remove SeparationItem from LilyPond's source (scm/define-grobs.scm). Then we would need a convert-ly rule. 2) Keep SeparationItem, even though it is never used. I guess it all depends on whether SeparationItem will ever be used again in the future. The main thing is that the documentation is modified to show a solution that works, i.e. that gives the same result as you previously could obtain setting SeparationItem #'padding = ... Yes, we're waiting for Joe to complete his fix so we can use 'spacing-spanner in the docs. At present no one has found a way to make it work. Or has this been fixed silently? I believe it was fixed in 35db77b06dc96ec680668dfb70b17cdc56c5f24f. Does it still fail? Joe ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: SeparationItem #'padding not working anymore?
Joe Neeman wrote Sunday, March 01, 2009 7:27 PM On Sun, 2009-03-01 at 15:38 +, Trevor Daniels wrote: Mats Bengtsson wrote Sunday, March 01, 2009 8:17 AM Quoting Patrick McCarty pnor...@gmail.com: On Sat, Feb 28, 2009 at 6:00 AM, Valentin Villenave v.villen...@gmail.com wrote: 2009/2/2 Joe Neeman joenee...@gmail.com: 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? I don't think it deserves an issue. We have two options: 1) Remove SeparationItem from LilyPond's source (scm/define-grobs.scm). Then we would need a convert-ly rule. 2) Keep SeparationItem, even though it is never used. I guess it all depends on whether SeparationItem will ever be used again in the future. The main thing is that the documentation is modified to show a solution that works, i.e. that gives the same result as you previously could obtain setting SeparationItem #'padding = ... Yes, we're waiting for Joe to complete his fix so we can use 'spacing-spanner in the docs. At present no one has found a way to make it work. Or has this been fixed silently? I believe it was fixed in 35db77b06dc96ec680668dfb70b17cdc56c5f24f. Does it still fail? No, you're quite right. It works. I must have missed the commit. Jon's already fixed the docs. Trevor ___ 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)
Comment #1 on issue 752 by jameselihubailey: Pango errors on OSX (table
28333)
http://code.google.com/p/lilypond/issues/detail?id=752
I forgot to mention, I can also get this with certain non-ascii characters
in lyrics,
i.e.,
\chords { c d e f }
{
\new Voice = test \relative c' { c d e f }
\new Lyrics \lyricsto test \lyricmode { e~li -- ded text
here }
}
GNU LilyPond 2.12.2
Procesando «Pango.ly»
Analizando...
Interpretando la música...
Preprocesando los objetos gráficos...
(process:1766): Pango-WARNING **: Error loading GDEF table 28333
(process:1766): Pango-WARNING **: Error loading GSUB table 28333
(process:1766): Pango-WARNING **: Error loading GPOS table 28333
Buscando el número de páginas ideal...
Disponiendo la música en una página...
Dibujando los sistemas...
Salida de la página hacia «Pango.ps»...
Convirtiendo en «./Pango.pdf»...
--
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
