[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: similar/identical snippets and cut off on the right border v2.17.2

From: Phil Holmes
Subject: Re: similar/identical snippets and cut off on the right border v2.17.2
Date: Sun, 23 Sep 2012 11:13:51 +0100

"eluze" <address@hidden> wrote in message news:address@hidden
browsing through the /snippets.pdf/  I found under /Setting system
separators/, page 470/471 an example which is cut off on the right.

the same [52/lily-6ae693a3.png] example appears also on page 140/141 and on
page 441/442 both with a cut off right border, too!

The duplicates are deliberate. Snippets are tagged with what area of notation they illustrate: pitches, rhythms, layout, etc., and if a snippet has multiple tags, since it illustrates multiple features, it will occur in the snippets listing multiple times.

in NR there are 2 similar examples

- one after /Miscellaneous \paper variables/ [16/lily-e1ae1c0c.png]
page-spacing-weight …
print-all-headers …

- the other is in chapter /Separating systems/ [4b/lily-3030cea4.png]

does it make sense to keep/maintain both? could the one in /Miscellaneous
\paper variables/ just /link/ to /Separating systems/ where it is explained
with an example?

Only one version is maintained - on the LSR.  The build system creates
the snippet documentation from the LSR tarball.

downloading these snippets from the html version (where it displays
correctly) I was astonished to see that they all have the statement \version
"2.16.0" - is this correct?

I _think_ so, but haven't checked. My belief is that the snippet has no version
number, and this is added during build.

scrolling to page 167, 196, 478 /Adjusting lyrics vertical spacing/ there is
a code line with a black bar at the end

This is partly because the snippets are not strictly part of the documentation system, but are user-generated. Therefore if the user makes line-lengths too
long, we will get black bars.

snippets.pdf, /Incipit/, page 123

the line displays only
 '(or (false-if-exception (- indent (* mm incipit-wid
instead of
 '(or (false-if-exception (- indent (* mm incipit-width

(there are more)

sorry to post all this in one, but I'm not sure if these issues are supposed to be fixed (eg. by http://code.google.com/p/lilypond/issues/detail?id=1691)
or if they will be fixed in the coming new release (stable or unstable).

They are fixed in the "official" documentation, AFAIK. If you'd like to raise an issue relating to the over-runs and black bars in the snippets, please feel
free to do so.  At some stage I would probably look at fixing them, but if
you'd like to experiment with the build system, this is a great place to start.

Phil Holmes
Bug Squad

reply via email to

[Prev in Thread] Current Thread [Next in Thread]