Re: Distances and measurements
Patrick McCarty wrote Friday, September 26, 2008 12:17 AM
I noticed your doc update for Distances and measurements, and it
looks really great!
I'm not sure about really great, but thanks anyway!
I have two suggestions to further improve this section:
1) The `pt' unit is actually 1/72.27 inch, which is the TeX point.
2) Staff-space can be used as a unit too in the \paper and \layout blocks:
\paper {
top-margin = 5\staff-space
bottom-margin = 10\staff-space
}
Actually it is just a place holder to get the docs into a
presentable state before 2.12, but even so
it should be correct - so thanks for your suggestions.
I'll fix it right away.
Thanks,
Patrick
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
accidental placement
Shouldn't this d-sharp be shifted more to the right?
- Mark
(Franz Schubert: Waltz op.127 no.4, m.21)
\version 2.11.60-1
\relative { \key a \major \time 3/4 b'4. } \\ { dis, fis a2 }
attachment: accidental_placement.png___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Cannot push translation status
2008/9/24 John Mandereau [EMAIL PROTECTED]: On 2008/09/23 16:36 +0200, Francisco Vila wrote: John, I try to update the status reports as result of make translation-status, but I'm afraid of erase valuable data from languages other than Spanish. No problem, as I'd have overwritten bad status data with correct ones at next translation-status call anyway. Before git-adding and commiting these results, diff shows lines such as @@ -214,7 +214,7 @@ translations.template.html.in; DO NOT EDIT !-- Jean-Charles Malahieude/td td/td tdspan style=background-color: #1fff1foui/span/td - tdspan style=background-color: #47ff24partiellement/span/td + tdspan style=background-color: #d587ffN/A/span/td tdpré-GDP/td /tr tr align=left This tells me that you have proper objects for French, which I see as bad objects on my side for these very same files, how could this be corrected? thanks. I don't have this error, and all of my master and lilypond/translation branches has been pushed to git.sv.gnu.org. If you want to be sure you have all committishes on git.sv.gnu.org, the least to do is fetching all branches; in this case, master and lilypond/translation should be enough (you will probably want to add stable/2.12 when it's created). For example, which branch is this object in? warning: fr/user/specialist.itely: fatal: bad object 6bcad9cdc487270910758b1ee39cf3c8aee1015e Despite of what you said, I think that it doesn't worth that I push my status with wrong data for other languages, even if you are to overwrite them later. But if I manage to make status w/o errors, I can push it easily. -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: delete-intermediate-files
2008/9/22 Graham Percival [EMAIL PROTECTED]: Is there a good reason to have delete-intermediate-files (#f) delete unusable PostScript files disabled by default? This question was raised a few times already; I think it deserves to be mentioned in the tracker. http://code.google.com/p/lilypond/issues/detail?id=685 Cheers, Valentin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Pdf Toc, NR
On 2008/09/26 17:30 +0200, Francisco Vila wrote: make web-1 has built my PDFs; LM and PU are just fine, but NR has the TOC and the LilyPond Index in English. Can't reproduce with a clean build. This oddity might happen because TeX reads index and toc files from English docs (Documentation/user/out-www), but texi2pdf forgets running TeX again to get correct files generated in first TeX pass. Sorry, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Use 'long long' integers in Rational class.
Neil and Han-Wen,
Thanks so much for the change to 64-bit! I have tried the original test case I
sent to the user list, and it now compiles without error! Also, I tried one of
the parts for the score I'm working on that was similarly breaking, and it
seems to work fine, too.
Below is the test case that now works. Thanks again!
Best,
Adam
===
\version 2.11.59
\layout {
\context { \Score
\override NonMusicalPaperColumn #'line-break-permission = ##f
\override NonMusicalPaperColumn #'page-break-permission = ##f
\override SpacingSpanner #'uniform-stretching = ##t
\override SpacingSpanner #'strict-note-spacing = ##t
proportionalNotationDuration = #(ly:make-moment 1 20)
ragged-right = ##t
}
\context { \Voice
\remove Forbid_line_break_engraver
\override Beam #'breakable = ##t
}
}
\new Staff {
\new Voice {
\time 4/1
c'2.*2351/3696
\scaleDurations #'(495 . 4336) {
d'8*11[ \bar | \break d'8*100 d'8*100]
}
e'1*827949/8012928
\bar |
\time 3/8
c'4.
}
}
%{
The error below now no longer occurs:
warning: unterminated beam d'8*11[ \bar | \break d'8*100 d'8*100]
===
[a=3696, b=34688 (denom. of 495/4366*211/8), c=8012928, d=8]
gcf(a,b,c,d) = 8
lcm(a,b,c,d) = 1027312242130944
32-bit precision maxes out at 4.3 billion (less than the lcm above)
64-bit is more like 18.4 quintillion
%}
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Three questions for ancient.itely
On Wed, 24 Sep 2008, =?ISO-8859-1?Q?Eyolf_=D8strem_ wrote: I'm working on the docs for ancient music, Nice to hear! 3. The form Episem is used, both as a lilypond command and in the documentation text. Since it's not really a medieval concept at all, but a term invented by the Solesmes monks when plainchant was revised/-vived in the late nineteenth century, it is not an established term in any language other than french, where it is episeme (and it doesn't appear neither in Merriam-Webster nor in the full OED). If anything, Episem is the german form. I would strongly recommend going with the latinized greek episema, which is what the Vatican editions have. Originally, I borrowed the term Episem from the OpusTeX implementation of Gregorian Chant. Just a couple of minutes ago, I did a small search on Google and have to agree that the form Episema is obviously much more used than Episem, especially in non-German languages. As you are working on the docs, there is another thing that comes into my mind: Currently, \augmentum is introduced in Sect. 2.8.3.6 (Gregorian square neumes ligatures). This was motivated from an implementation point of view, which is special for \augmentum within ligatures. However, from a user's perspective, I think \augmentum should be introduced in Sect. 2.8.3.1 (Ancient articulations), showing simply an augmented punctum note. Then, in Sect. 2.8.3.6, it should be stated that \augmentum is treated specially within ligatures (i.e. all dots vertically aligned after the ligature), showing \[ \augmentum a \flexa \augmentum g \] as an example. And yet another thing: The Hufnagel style of Gregorian Chant is in English language obviously better known as Gothic style. However, now that lily 2.12 is already in beta release stage, I would not recommend performing such a big rename at present. Thanks greetings, Juergen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Episema not showing
On Thu, 25 Sep 2008, =?ISO-8859-1?Q?Eyolf_=D8strem_ wrote: It is mentioned as one of the known issues in the ancient section of the documentation that The episema line is not displayed in many cases. That in itself does not make it very useful, but it's doubly bad when it doesn't even show up in the example that illustrates it. Yes. Over the last few years, the episema first worked, then broke, then worked again, then broke again, and so forth, probably because people were working on the text spanner implementation. I still have the vision that with the next revision of the text spanner code, the episem will be (re-)fixed as if by a ghost's hand. Hence, the documentation sounds currently odd, but I hope it can be left as is in prospect of future lily releases... ;-) Greetings, Juergen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
