Wrong translation in doc
Wrong translation for the description of list type: http://www.lilypond.org/doc/v2.18/Documentation/learning/types-of-properties.de.html Eine eingeklammerte Anzahl von Einträgen, mit Klammern getrennt und angeführt von einem Apostroph It's space-separeted, not paren-separeted. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Wrong translation in doc
2014-09-15 16:40 GMT+02:00 Jakob Schöttl jscho...@gmail.com: Wrong translation for the description of list type: http://www.lilypond.org/doc/v2.18/Documentation/learning/types-of-properties.de.html Eine eingeklammerte Anzahl von Einträgen, mit Klammern getrennt und angeführt von einem Apostroph It's space-separeted, not paren-separeted. Thank you; here is the source file, please download it and resend it to us with your edits. http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=Documentation/de/learning/tweaks.itely;hb=f8c668427f825a69cf68e2ae7e28daf01a6c52cc -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Wrong translation in doc
Am 15.09.2014 um 16:48 schrieb Francisco Vila:
2014-09-15 16:40 GMT+02:00 Jakob Schöttl jscho...@gmail.com:
Wrong translation for the description of list type:
http://www.lilypond.org/doc/v2.18/Documentation/learning/types-of-properties.de.html
Eine eingeklammerte Anzahl von Einträgen, mit Klammern getrennt und
angeführt von einem Apostroph
It's space-separeted, not paren-separeted.
Thank you; here is the source file, please download it and resend it
to us with your edits.
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=Documentation/de/learning/tweaks.itely;hb=f8c668427f825a69cf68e2ae7e28daf01a6c52cc
2014-09-15 17:06 GMT+02:00 Jakob Schöttl jscho...@gmail.com:
Better translation in three hunks and using @code for #t and #f.
Not sure if this is syntactically allowed:
Apostroph-Raute (@code{'#}) - I removed the space before @code!
I could apply your edits right now but there still are some
differences from the original, compare to
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=Documentation/learning/tweaks.itely;hb=translation
@item Vector
@tab Constants
enclosed in @code{#(}@dots{}@code{)}.
@tab @code{#(#t #t #f)}
@end multitable
against German
@item Vektor
@tab Eine Liste mit drei Einträgen, eingeklammert und angeführt mit
Apostroph-Raute (@code{'#})
@tab @code{'#(#t #t #f)}
@end multitable
Please fix this and resend your file, thank you
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Wrong translation in doc
2014-09-15 18:06 GMT+02:00 Jakob Schöttl jscho...@gmail.com: Assuming that the english version is correct, here the fixed german version. Applied in my tree and testing compile. Will push if it succeeds and will be visible after some paperwork. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: misaligned composer in LP 2.19.14
pls p.l.schm...@gmx.de writes:
Hey all,
there seems to be a bug in LilyPond 2.19.14: in the following example
the composer is center-aligned instead of right-aligned:
\version 2.19.14
\header {
composer = composer
}
\score {
c'1
}
Current branch: issue4102
Tracker issue: 4102 (http://code.google.com/p/lilypond/issues/detail?id=4102)
Rietveld issue: 137680043 (https://codereview.appspot.com/137680043)
Issue description:
Issue 4102: misaligned composer in LP 2.19.14 This problem surfaced
in the wake of the fix for issue 3855. It is due to
Stencil::translate not moving an empty expression even if it has
non-empty extents so that \markup fill-line { composer }
which assembles a line piece by piece and determining the offset of
the next piece by looking at the end of the assemblage so far lost
the offset between the first and second in the line. Also
contains another (not necessary but appropriate) commit Remove
redundant check for empty X interval
composer is not actually center-aligned: instead its _right_ edge
(rather than its middle) is at the center of the line because the space
between start and center of the line went missing.
Quite hard to track down, caused in an obscure place in C. Well, seems
like the warning for temporary regressions will apply to 2.19.14, with
the fix only arriving in 2.19.15.
Sorry for that.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Odd layout choices
All, Sometimes Lilypond changes how it does its Fitting music on ... calculations when it decides what can fit on a page and what cannot. In this case, after four pages on which the fitting process puts two systems per page, the subsequent pages *all* have only one system per page--even though there is no change in number of staves -- still seven (SATB plus organ). The links below to the Lilypond code and resulting PDF show what I mean. Now, I know I can fiddle with the margins and likely get Lilypond to fit two systems per page throughout, but this just seems so odd. Why can two seven-stave systems work for four pages but not for all remaining pages? https://www.dropbox.com/s/cr26k3jlkxwg6s1/psalm46.pdf https://www.dropbox.com/s/tjbf7sdudia6zpy/psalm46.ly https://www.dropbox.com/s/zqoxjruc80door8/psalm_46_organ.ly https://www.dropbox.com/s/gcugottr7fukoxv/nak_standard_header.ly Verbose logging provides no guidance as, well, there's technically been no error. In order to get two systems per page through out, I have to set-global-staff-size to 14 and decrease all margins thus: top-margin = 1.0\in bottom-margin = .75\in right-margin = 1.0\in left-margin = 1.0\in Which is, well, odd. To me at least. Regards, Guy -- There is only love, and then oblivion. Love is all we have to set against hatred. (paraphrased) Ian McEwan Guy Stalnaker jimmyg...@gmail.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Odd layout choices
Am 15.09.2014 um 21:41 schrieb Guy Stalnaker:
All,
Sometimes Lilypond changes how it does its Fitting music on ...
calculations when it decides what can fit on a page and what cannot.
In this case, after four pages on which the fitting process puts two
systems per page, the subsequent pages *all* have only one system per
page--even though there is no change in number of staves -- still
seven (SATB plus organ). The links below to the Lilypond code and
resulting PDF show what I mean. Now, I know I can fiddle with the
margins and likely get Lilypond to fit two systems per page
throughout, but this just seems so odd. Why can two seven-stave
systems work for four pages but not for all remaining pages?
Perhaps something requires more padding on the last systems?
https://www.dropbox.com/s/cr26k3jlkxwg6s1/psalm46.pdf
Well, this doesn’t show what you describe, but two systems per page.
https://www.dropbox.com/s/tjbf7sdudia6zpy/psalm46.ly
https://www.dropbox.com/s/zqoxjruc80door8/psalm_46_organ.ly
https://www.dropbox.com/s/gcugottr7fukoxv/nak_standard_header.ly
Verbose logging provides no guidance as, well, there's technically
been no error. In order to get two systems per page through out, I
have to set-global-staff-size to 14 and decrease all margins thus:
top-margin = 1.0\in
bottom-margin = .75\in
right-margin = 1.0\in
left-margin = 1.0\in
Which is, well, odd. To me at least.
Resolving this can be difficult in cases.
Try
\paper {
min-systems-per-page = 2
% or also
% page-count = x
}
in order to force lily to do what you want. It might result in illicit
compression, though. You’ll have to see.
HTH, Simon
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Ottava dash-fraction = #0.0 produces dots, not no line
I'm not top posting
The section on the 2.18 version of OttavaBracket...
http://www.lilypond.org/doc/v2.18/Documentation/internals/ottavabracket
...looks like this:
dash-fraction (number):
0.3
Size of the dashes, relative to dash-period. Should be between 0.0 (no
line) and 1.0 (continuous line).
But this code...
%% --- Start
\version 2.18.2
\relative c,, {
\clef bass
\ottava #-1
\override Staff.OttavaBracket.dash-fraction = #0.0
c4 c c c
}
%% --- End
...produces a dotted line, not no line as the documentations states.
Either the documentation or the behavior should be changed.
Knute Snortum
(via Gmail)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Odd layout choices
Simon, Thanks for the reply. I apologize for forgetting to rename the bad pdf before futzing with the margins to get the piece back to two systems per page. You have provided me another option which I will explore. Here is link to how the piece looks with the original margins: https://www.dropbox.com/s/3xfg31tg4qj6zew/psalm46_bad_fitting.pdf?dl=0 Still baffling why Lilypond fits two systems per page for four pages, then stops for the rest of the piece. I'll try your \paper option. Thank you, Guy On Mon, Sep 15, 2014 at 2:46 PM, Simon Albrecht simon.albre...@mail.de wrote: min-systems-per-page = 2 Guy Stalnaker jimmyg...@gmail.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Odd layout choices
No longer baffling :-) Using the min-systems-per-page option forced LP to put the systems on the same page and it is clear, when it does so, why its default fitting algorithm does not! It appears to be the non-musical elements that are interfering with things. I still had to play with margins, etc. to get it to look right. Thanks for your help. Is there an easy way to tell Lilypond not to stack vertically simultaneous directives like a tempo and dynamics, but to render them horizontally? Thanks again! Guy Guy Stalnaker jimmyg...@gmail.com On Mon, Sep 15, 2014 at 11:13 PM, Guy Stalnaker jimmyg...@gmail.com wrote: Simon, Thanks for the reply. I apologize for forgetting to rename the bad pdf before futzing with the margins to get the piece back to two systems per page. You have provided me another option which I will explore. Here is link to how the piece looks with the original margins: https://www.dropbox.com/s/3xfg31tg4qj6zew/psalm46_bad_fitting.pdf?dl=0 Still baffling why Lilypond fits two systems per page for four pages, then stops for the rest of the piece. I'll try your \paper option. Thank you, Guy On Mon, Sep 15, 2014 at 2:46 PM, Simon Albrecht simon.albre...@mail.de wrote: min-systems-per-page = 2 Guy Stalnaker jimmyg...@gmail.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
