Warnings during make
On a fresh repo, as of cf3b8d901949a4a6d811755ec8d6afa2a1f5a067 the build is successful, but: Making lily/out/main.o < cc main.cc: In function 'void parse_argv(int, char**)': main.cc:641:23: warning: loop variable 'keyval' creates a copy from type 'const std::pair, std::__cxx11::basic_string >' [-Wrange-loop-construct] 641 | for (const auto keyval : init_scheme_variables_global) | ^~ main.cc:641:23: note: use reference type to prevent copying 641 | for (const auto keyval : init_scheme_variables_global) | ^~ | & [...] Making lily/out/program-option-scheme.o < cc program-option-scheme.cc: In function 'scm_unused_struct* ly_command_line_options()': program-option-scheme.cc:423:19: warning: loop variable 'keyval' creates a copy from type 'const std::pair, std::__cxx11::basic_string >' [-Wrange-loop-construct] 423 | for (const auto keyval : init_scheme_variables_global) | ^~ program-option-scheme.cc:423:19: note: use reference type to prevent copying 423 | for (const auto keyval : init_scheme_variables_global) | ^~ | &
Re: Glitch in the documentation?
Le 08/10/2022 à 12:43, Jean Abou Samra a écrit : Le 8 oct. 2022 à 12:29, Martín Rincón Botero a écrit : This website http://lilypond.org/doc/v2.23/Documentation/notation/modifying-broken-s panners displays to me in Catalan. As much as I like Catalan (it's one of my two favorite Romance languages) it's weird that changing the version number to 2.22, 2.21, 2.20, 2.19, 2.18... returns the same web page in English. Does anyone else also see that page in Catalan or is it only me? (The default language of my computer is Spanish, in case it's relevant). Changing the "vx.y" part of the URL works in most cases, but not in all cases. This part of the documentation has been reorganized, so the previous URL is no longer the right one for English. However, not all translations have been updated (only the French one has, IIRC) so the set of pages your browser has to choose from consists of a set of languages that does not contain English, and it seems to choose Catalan. What I don’t understand is why your browser doesn’t choose Spanish, since that page does have a Spanish version. Is Spanish the default language for your browser also? You can always select the Spanish version at the bottom. Just a guess: it might have been Afrikaans if the first language, in alphabetical order, would be "af"? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Failing makelsr.py
I'm trying to fix
Documentation/snippets/new/customizing-the-no-chord-symbol
in order to get it right, but running from top-dir :
$ scripts/auxiliar/makelsr.py
Traceback (most recent call last):
File "/home/jcharles/GIT/Lily/scripts/auxiliar/makelsr.py", line 21,
in
import langdefs
ModuleNotFoundError: No module named 'langdefs'
$
Manually changing the header in snippets/ as well (and adding the
"%begin verbatim" gives the expected resul in NR-2.7.2.
\version "2.23.10"
\header {
lsrtags = "chords"
texidoc = "
By default, rests in a @code{ChordNames} context cause the @qq{N.C.}
symbol to be printed. This markup can be customized.
"
doctitle = "Customizing the no-chord symbol"
}
<<
\chords {
R1
\set noChordSymbol = "—"
R1
\set noChordSymbol = \markup \italic "Ssh!"
R1
}
{
R1*3
}
>>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Missing links in German documentation
Le 09/06/2021 à 07:44, Helge Kruse a écrit : Hi, the German versions of the pages https://lilypond.org/doc/v2.20/Documentation/notation/inside-the-staff https://lilypond.org/doc/v2.20/Documentation/notation/outside-the-staff have some broken links. The "Siehe auch" sections point to https://lilypond.org/doc/v2.20/Documentation/snippets/anmerkungen. Either the link to the English version https://lilypond.org/doc/v2.20/Documentation/snippets/editorial-annotations would be helpful, or a German version of the annotation (if existing) would close the missing link. While browsing through other pages I find the same pattern of missing links too: https://lilypond.org/doc/v2.20/Documentation/notation/common-notation-for-vocal-music ---> https://lilypond.org/doc/v2.20/Documentation/snippets/notation-von-gesang This is a long standing problem that has not been solved yet. You might get an idea when reading https://gitlab.com/lilypond/lilypond/-/issues/2266 and follow issue 1776 which has links to discussions from 2012. Cheers, -- Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
bug in snippet "Adding volta brackets to additional staves"
Revising the French translation of repeats.itely, I notice that the volta bracket doesn't appear in the third staff of the snippet with the master branch. Just compare the two versions of the online documentation of NR-1.41.1 where the bracket is present on v2.22, but not on v2.23. Copying Dan who worked on this matter. Cheers, -- Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bug in snippet "Adding volta brackets to additional staves"
Le 28/02/2021 à 15:53, Dan Eble a écrit : The performance length is 4 whole notes, but the third part has only half that. This is not what the image on the LSR means. There is no \repeat music in the third staff, so why should there be a volta bracket? 2.23 is handling this input more correctly. I don't think this snippet teaches anything more than the one entitled "Volta multi staff". I'm definitely not as good as expected with computation… It might be wise to suppress it from the docs and LSR if not corrected. Cheers, -- Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
snippet "Moving the ends of hairpins"
While translating the texidoc of this snippet, it seems erroneous to me. Instead of "Positive values move endpoints to the right, negative to the left." I observe that "Positive values move endpoints inside the range, negative outside." Cheers, -- Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Missing link: Rhythms
Le 20/04/2020 à 14:01, Thomas Morley a écrit : Am Mo., 20. Apr. 2020 um 13:16 Uhr schrieb Bernhard Kleine : When in http://lilypond.org/doc/v2.19/Documentation/notation/bars#bar-lines I engage the link "Schnipsel":Rhythms it is not found: http://lilypond.org/doc/v2.19/Documentation/snippets/rhythmus. After doing some random testing, I think every link from non-english docs to snippets fails, because the keyword is translated. Thus moving this one to the bug-list. It's issue 2266, that lasts forever since 2011 -- a side effect of GDP since snippets is no longer translated. Cheers, -- Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LilyPond — Notation Reference: 2.9.4 Divisiones (v2.18/2.19)
Le 09/09/2019 à 20:09, Jean-Charles Malahieude a écrit : I'll take care of this (in Translation and stable/2.20). Done as commit 2b6b44d46e5af1b61ff5b1be98f48e44bc27f3aa -- Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LilyPond — Notation Reference: 2.9.4 Divisiones (v2.18/2.19)
Le 09/09/2019 à 10:31, Pierre Perol-Schneider a écrit : Hi bug Squad, There's a typo in the french translation: http://lilypond.org/doc/v2.19/Documentation/notation/typesetting-gregorian-chant#divisiones : ‘gregorian-init.ly’ appears twice instead of ‘gregorian.ly’ I'll take care of this (in Translation and stable/2.20). gregorian-init.ly has been renamed in late 2008, but some strings in the docs have been missed. Cheers, -- Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
pitchedTrill bug?
Hi all,
Is there any reason why I get an natural when there is none to be ?
{
\key c \major
\pitchedTrill
c''2\startTrillSpan d'' c''\stopTrillSpan
\pitchedTrill
c''2\startTrillSpan b' c''\stopTrillSpan
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: mistake in French version of \sourcefileline 1381
Le 23/11/2017 à 18:25, Éric a écrit :
in the Learning page on line, french version, this is wrong :
\sourcefileline 1381
\relative {
\time 12/16
\omit Staff.TimeSignature.stencil
c''4 b8 c d16 c d8 |
g,8 a16 b8 c d4 e16 |
e8
}
As in english version, it should be :
\sourcefileline 1381
\relative {
\time 12/16
\omit Staff.TimeSignature
c''4 b8 c d16 c d8 |
g,8 a16 b8 c d4 e16 |
e8
}
A git grep in the source tree (Documentation/fr/learning) gave
git grep -n '\omit Staff.TimeSignature.stencil'
tweaks.itely:1385: \omit Staff.TimeSignature.stencil
I will correct it over the weekend.
Cordialement,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Download links missing at http://lilypond.org/index.de.html
Le 22/10/2016 à 16:26, Simon Albrecht a écrit :
Hi Jean-Charles,
thanks for the effort. Here’s what I’d do in the attachment – though I’m
not sure I dealt with the @uref{}s correctly…
Pushed as 181db07b2627d98fb77564c45fad23a96e7ee54c on the translation
branch, with your amendments, and merged with staging.
Danke für eure Hilfe!
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Download links missing at http://lilypond.org/index.de.html
Le 22/10/2016 à 16:26, Simon Albrecht a écrit :
Hi Jean-Charles,
thanks for the effort. Here’s what I’d do in the attachment – though I’m
not sure I dealt with the @uref{}s correctly…
Would you like me to change the headings in the examples' page according
to this?
By the way, which is right wording between
LP ist ein Werkzeug, dass Notensatz handhaben kann.
and
LP ist ein Werkzeug, das Notensatz handhaben kann.
My memory about "deutsche Grammatik" (30 years ago…) would lean towards
"dass".
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Download links missing at http://lilypond.org/index.de.html
Le 21/10/2016 à 22:35, Malte Meyn a écrit :
The german version of index.html is missing the right column with
download and manual links.
My German writing is very old, but here is a patch.
If any gentle German would kindly proofread…
Cheers,
Jean-Charles
>From ae0ced1be1617970e9ff8748ae018399e3ab1f46 Mon Sep 17 00:00:00 2001
From: Jean-Charles Malahieude <lily...@orange.fr>
Date: Sat, 22 Oct 2016 15:30:20 +0200
Subject: [PATCH] web-de: update the frontpage
---
Documentation/de/web.texi | 65 ++-
1 file changed, 59 insertions(+), 6 deletions(-)
diff --git a/Documentation/de/web.texi b/Documentation/de/web.texi
index 262afd8..55fe1fc 100644
--- a/Documentation/de/web.texi
+++ b/Documentation/de/web.texi
@@ -1,6 +1,6 @@
\input texinfo @c -*- coding: utf-8; mode: texinfo; documentlanguage: de -*-
@ignore
-Translation of GIT committish: 5b6ddab894b3065c35c72ef8048b8c6edbe684ac
+Translation of GIT committish: 901f7ff2acbb996f1e726607f3f8e921c5e1ddd3
When revising a translation, copy the HEAD committish of the
version that you are working on. For details, see the Contributors'
@@ -135,13 +135,66 @@ Lesen Sie mehr in der @ref{Einleitung}!
@divEnd
-@divId{news}
+@divId{homepage-main}
+
+@divClass{column-center-top}
+
+@subheading Schöner Notensatz
+
+@c This example image is the image from the website version of the essay
+@c manual, downloaded to the pictures directory for use on the home page.
+@c Large version is generated manually from ly file in pictures directory.
+@divId{homepage-example-image-wrapper}
+@imageClickable{bwv861-lilypond,png,,bwv861-lilypond-large,png,center}
+@divEnd
+
+@ifclear web_version
+ @c no anchor links, just text
+
+LilyPond ist ist ein sehr mächtiges und flexibles Werkzeug, dass Notensatz
+der unterschiedlichsten Art handhaben kann, wie zum Beispiel klassische
+Musik (wie dieses Orgelpräludium von J. S. Bach), komplexe Notation,
+alte Musik, moderne Musik, Tabulatur, Vokalmusik, Popmusik, Anwendung in
+der Musikerziehung, groÃe Projekte, individuelle Ausgabe ebenwie
+Schenker Graphen.
+
+@end ifclear
+@ifset web_version
+ @c anchor links, link to individual examples by their tag
+ @c Translators should use the localized anchor name
+ @c (e.g. examples.html#Musica-Antica)
+ @c to be found in out-www/web/examples.LL.html
+
+LilyPond ist ist ein sehr mächtiges und flexibles Werkzeug, dass Notensatz
+der unterschiedlichsten Art handhaben kann, wie zum Beispiel
+@uref{examples.html#Klassische-Musik, klassische Musik}
+(wie dieses Orgelpräludium von J. S. Bach),
+@uref{examples.html#Komplexe-Notation, komplexe Notation},
+@uref{examples.html#Alte-Musik, alte Musik},
+@uref{examples.html#Moderne-Musik, moderne Musik},
+@uref{examples.html#Tablatur, Tablatur},
+@uref{examples.html#Vokalmusik, Vokalmusik},
+@uref{examples.html#Popmusik, Popmusik},
+@uref{examples.html#Anwendung-in-der-Musikerziehung, Anwendung in der Musikerziehung},
+@uref{examples.html#Grosse-Projekte, groÃe Projekte},
+@uref{examples.html#Individuelle-Ausgabe, individuelle Ausgabe},
+ebenwiwe
+@uref{examples.html#Schenker-Graphen, Schenker Graphen}.
+
+@end ifset
+
+Sehen sie mehr in @ref{Beispiele} an!
+
+@divEnd
+
+@divClass{column-center-middle-color2}
+@subheading Neuigkeiten
@c TODO: generate this automatically, including RSS feed.
-@include web/news-front.itexi
+@include web/news-headlines.itexi
+
+@ref{News, Weitere Neuigkeiten...}
-@divClass{float-right}
-(@ref{Ãltere Neuigkeiten})
@divEnd
@divEnd
@@ -152,7 +205,7 @@ Lesen Sie mehr in der @ref{Einleitung}!
@end ifclear
@ifset web_version
@c make the side bar:
-@divId{homePageSideBar}
+@divId{homepage-sidebar}
@subheading Stabile Version
@c TODO: javascript to detect OS and suggest download?
--
2.10.1
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: probably an oversight in a link on the home page
Le 15/10/2016 à 16:19, Federico Bruni a écrit :
If you don't mind, and as I'm about to merge
master->translation->staging, I'll take care of it.
I'll also take care of the Japanese and French versions as Federico
mentioned on the translation list.
Ok, go ahead.
Don't forget what Masamichi pointed out (in the translation mailing
list): 'make doc' (and 'make website', I guess) adds .it/.fr/.ja/etc to
the relative links of translated manuals. So the recommendation to
translators should be to keep the URL as is and change only the anchor
(after checking the anchor name created by texinfo in the localized HTML
manual).
I didn't have the time to test it yet, but I trust Masamichi.
He is right: the LL part of the URL is inserted during the build process.
Nevertheless, when I replace
@uref{examples.html#g_t_53e4_697d, 古楽}
with
@uref{examples.html#Gu-Le-, 古楽}
as mentioned in out-www/web/
古楽
I still only reach the top of examples.ja.html.
The only one that works is Schenker graphs (the only "non encoded" anchor).
Results are pushed and merged with staging now.
BTW, I won't be reachable tomorrow, my mom's 84th!
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: probably an oversight in a link on the home page
Le 15/10/2016 à 05:00, Paul a écrit :
On 10/14/2016 07:31 AM, Federico Bruni wrote:
Hi Paul
I think that you forgot to remove the absolute URL here. Or I'm
missing something?
+LilyPond is a powerful and flexible tool for engraving tasks of
+all kinds, for example
+@uref{http://lilypond.org/examples.html#Classical-Music, classical
music}
+(like the example above by J.S. Bach),
+@uref{examples.html#Complex-Notation, complex notation},
The first link should be relative, like all the others:
@uref{examples.html#Classical-Music, classical music}.
BTW, this comment:
@c anchor links, link to individual examples by their tag
may be more informative (for translators also):
@c Translators should use the localized URLs, followed by their
translated anchor name (e.g. examples.it.html#Musica-Antica)
You're right, that was an oversight on my part. Good catch, thanks!
Those edits all make sense to me. Should I do them or would you like
to? Either way is fine with me.
If you don't mind, and as I'm about to merge
master->translation->staging, I'll take care of it.
I'll also take care of the Japanese and French versions as Federico
mentioned on the translation list.
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Texinfo indexing
Le 14/06/2016 à 10:47, David Kastrup a écrit : Huh, I have to try. I just remember that we likely are still using texi2html for our web page generation, and I have no idea how _that_ does the indexing. If we can only create better sorted indices for PDF and/or Info, that would be sort of a let-down. A cursory glance would suggest that the following commands are entered both with and without backslash via @funindex: \accepts [...] This one appears only once, labeled "\accepts" with notation.pdf. Even more, there is only one target (so to say only one place where both versions are mentioned) for "accepts" vs 3 targets when @set txiindexbackslashignore is specified in common-macros.itexi. BTW this make a 6 pages less volume. If texi2any follows the same rule, it would be the same, I guess for the HTML version. For the moment I'm still stuck withe the same errors and unable to dig further in the switch from texi2html that, sooner or later, will disappear from distros. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Review of chapter 4 of NR (spacing.itely)
Le 22/12/2015 11:00, Federico Bruni a écrit :
h) 4.6.1 Displaying spacing
"Note that:
@multitable {1 staff-space} {staff-size)/4 * (25.4/72.27) mm}
@item 1 point
@tab = (25.4/72.27) mm
@item 1 staff-space
@tab = (@code{staff-size})/4 pts
@item
@tab = (@code{staff-size})/4 * (25.4/72.27) mm
@end multitable
"
The first line within @multitable block is not rendered. What is meant for?
If I'm not mistaken, it fixes the wideness of the columns: you first
determine the largest you would need for each of them ("1 staff-space"
for the first). This will position the tab accordingly. Look how the =
are vertically aligned on the three lines.
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: # comments in the PO files
Le 28/09/2015 12:19, Benno Schulenberg a écrit : Then my PO file still has not been imported into git. Yes it has been imported on Saturday 26 by commit "PO: sync Dutch and German from FTP" 45a35a03c3dd7b6dc3bc6347ffd97958f20b1fd2 and is part of 2.19.28, with all your comments. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LP website : right column has strange look in other langage than english
Le 14/03/2015 14:39, Federico Bruni a écrit : we don't need a tracker issue. I've updated Italian in the translation branch. I'm sure that the other languages actively maintained will follow soon.. What about the unmaintained languages? Since it is mostly moving around things, what might be done is updating the different ll/web.texi files without changing their committish ID. I think that we'll have, one day or the other, to discuss about dealing with unmaintained materials : The web-site is like a shop window and the more cleaned the glass is, the better. But what is on the shelves should not smell too musty… Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
lyrics extender and acciaccatura
Hi all,
Trying to align a syllable to acciaccaturas, I came across an extender
problem:
The extender should stop *before* the rest, not when encountering the
next acciaccatura.
\version 2.19.15
Music = {
r4 \acciaccatura { c'8 } e'4~ e'2~
e'1
r4 \acciaccatura { e'8 } c'2.
}
TextKO = \lyricmode { Ah __ KO }
TextBetter = \lyricmode { Ah __ Hum }
\score {
\new Staff
\new Voice = music { \Music }
\new Lyrics \lyricsto music \TextKO
\new Lyrics \lyricsto music \TextBetter
\layout { }
}
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lyrics extender and acciaccatura
Le 11/11/2014 17:22, David Kastrup a écrit :
David Nalesnik david.nales...@gmail.com writes:
On Tue, Nov 11, 2014 at 9:53 AM, David Nalesnik david.nales...@gmail.com
wrote:
Hi Jean-Charles,
The problem I see here is that the X-parent of the LyricText is being set
to the NoteColumn of main note rather than to the grace note. (Perhaps
that's desirable?)
This doesn't work:
\new Staff
\new Voice = music { \grace c'8 }
\new Lyrics \lyricsto music { hi }
Not much of a surprise here.
\new Staff
\new Voice = music { \grace c'8 }
\new Lyrics \with { includeGraceNotes = ##t } \lyricsto music { hi }
Thanks, David. I was sure to have seen something about it. Unfortunately
dig not enough deeply since this clause is only mentioned in NR2.1.3
Stanzas (as a @subsubheading in Stanzas with different rhythms)
instead as in 2.1.2 with Placing syllables horizontally!
Even better, includeGraceNotes takes care of the extender's problem that
was most annoying.
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: spacing.itely sectioning does not match menu
Le 06/08/2014 23:03, James disait : On 06/08/14 20:34, Jean-Charles Malahieude wrote: Hi all, Building docs from scratch, I get an error in French (I'm on it) but also and in notation.splittexi.log: ** Node following `Optimal page breaking' in menu `Optimal page turning' and in sectionning `Minimal page breaking' differ ** No node following `One-line page breaking' in menu, but `Optimal page turning' follows in sectionning I forgot to change/check the 'menu' ordering So the 'truth' is the sectioning. I'll fix that in a patch now. Interesting that this doesn't break a full doc for me. AFAIR, this never did break a doc-build. Too bad for me: as a gourmet, I've trusted the menu… Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: spacing.itely sectioning does not match menu
Le 07/08/2014 18:37, Jean-Charles Malahieude disait : I'll add: And hopefully it doesn't break, otherwise no translation because of snippets and internals. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
spacing.itely sectioning does not match menu
Hi all, Building docs from scratch, I get an error in French (I'm on it) but also Please check the logfile notation.bigtexi.log for errors make[3]: *** [out-www/notation-big-page.html] Error 255 make[3]: *** Waiting for unfinished jobs Please check the logfile notation.splittexi.log for errors and in notation.splittexi.log: ** Node following `Optimal page breaking' in menu `Optimal page turning' and in sectionning `Minimal page breaking' differ ** No node following `One-line page breaking' in menu, but `Optimal page turning' follows in sectionning Menu announces: * Manual page breaking:: * Optimal page breaking:: * Optimal page turning:: * Minimal page breaking:: * One-line page breaking:: But sectioning is: 1488:@subsection Page breaking 1503:@unnumberedsubsubsec Manual page breaking 1587:@unnumberedsubsubsec Optimal page breaking 1603:@unnumberedsubsubsec Minimal page breaking 1626:@unnumberedsubsubsec One-line page breaking 1643:@unnumberedsubsubsec Optimal page turning Which one to believe saying the truth? Cheers, Jean-Charles Comes from aec840a735b33a4be38b10baeb40f8e660e3d55c Doc: NR Section 4.3 - reformatting as per CG Guidelines ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
LSR 405 (Changing the tuplet number)
One remaining occurrence of \times in texidoc:
- the denominator of the argument to the @code{\\times} command.
+ the denominator of the argument to the @code{\\tuplet} command.
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LSR 405 (Changing the tuplet number)
Le 03/08/2014 17:17, Jean-Charles Malahieude disait :
One remaining occurrence of \times in texidoc:
- the denominator of the argument to the @code{\\times} command.
Since the fraction is inverted with \tuplet, it should read:
the numerator of the argument to the @code{\\tuplet} command.
That's what happens when reading too much at a time!
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 3648 – revolution revisited
Le 08/07/2014 08:11, David Kastrup disait : Simon Albrecht simon.albre...@mail.de writes: I currently try out the consequences of issue 3648 http://code.google.com/p/lilypond/issues/detail?id=3648, namely the possibility to use isolated durations as frequently as has been normal for isolated pitches. It certainly means a change to the habits of entering music in LilyPond language, but I can imagine that it considerably simplifies typing in the long run. I'd keep away from it unless entering predominantly rhythmic patterns. That includes a lot of drum music, of course. That is: you should focus on those use cases which simplify _reading_ music rather than _writing_ it. Don't forget other software that export to LilyPond: Rosegarden for instance puts a space between pitch and duration. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
accidentalStyle dodecaphonic-no-repeat
Hi all, On my way in updating translations, I notice that this style seems to not do what it claims. Look at the two successive examples in NR-1.1.3 Automatic accidentals, both styles dodecaphonic and dodecaphonic-no-repeat: there is no difference at all. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-invoke-editor requires emacs?
Le 20/10/2013 18:31, Federico Bruni disait : I've set up point and click on my Gnome 3 system as described in Usage 4.1.1 When I run gnome-open textedit:///etc/issue:1:0:0 (or click on a PDF in evince), the output says: sh: 1: emacsclient: not found sh: 1: emacs: not found lilypond-invoke-editor (GNU LilyPond) 2.17.27 sh: 1: emacsclient: not found sh: 1: emacs: not found Should I have emacs installed? How can I configure the editor I like? Not sure if it's really some sort of bug or if I'm missing something. Just have a look at usgage 4.1.1 Configuring the system It seems you haven't defined any environment variable EDITOR Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: lilypond-invoke-editor requires emacs?
Le 20/10/2013 19:50, Federico Bruni disait : 2013/10/20 Jean-Charles Malahieude lily...@orange.fr mailto:lily...@orange.fr Just have a look at usgage 4.1.1 Configuring the system It seems you haven't defined any environment variable EDITOR thanks, I've added the variable to .bashrc but it doesn't work anyway: $ echo $EDITOR gedit $ gnome-open textedit:///etc/issue:1:0:0 $ lilypond-invoke-editor (GNU LilyPond) 2.17.27 sh: 1: emacsclient: not found sh: 1: emacs: not found lilypond-invoke-editor (GNU LilyPond) 2.17.27 sh: 1: emacsclient: not found sh: 1: emacs: not found ^C I don't use PC when retyping because of inflation (my urtext version of BWV246 is 1.6 Mo instead of 13.9. I just checked and have a problem, maybe due to the tree I have adopted? Nevertheless, here is the begining of my .bashrc # User specific aliases and functions export EDITOR=/usr/bin/emacs Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: quoteDuring: no midi nor repeats
Le 25/08/2013 08:34, Keith OHara disait :
Jean-Charles Malahieude lilyfan at orange.fr writes:
1- unfoldRepeats doesn't work, neither on pdf nor in midi, [on Quotes]
You can
\addQuote echo { \singer }
before the printed score, and
\addQuote echo { \unfoldRepeats \singer }
before the midi score with \unfoldRepeats
I'll add a tracker issue.
Thanks.
The workaround is nevertheless not optimal in case of a large project
with lots of included files, like:
BWV246/05/BassoM.ily containing music for bass singers,
BWV246/05/Continuo.ily containing :
\addQuote basso { \include BassoM.ily }
{
\set Score.quotedEventTypes = #'(note-event rest-event)
\quoteDuring basso { \repeat volta 2 { s1*5 } s1*8 f1 }
}
BWV246/05/Score.ily for the score layout (used both for pdf and midi):
…
\new Staff = Continuo
\XContinuo \clef bass
\new Voice \include Breaks.ily
\include Global.ily \include Continuo.ily
\new FiguredBass { \include Figures.ily }
BWV246/Urtext.ly collecting all 80 pieces with preface and ToC
reproducing my source:
…
\tocItem \AE \label #'RefAE
\score { \keepWithTag #'(Full Urtext)
\include 05/Score.ily
\header {
breakbefore = ##t
piece = (CHORAL.)
}
\layout { }
} %ends 05
…
BWV246/Midi.ly including all 80 \book for midi:
…
\book { \bookOutputName BWV_246-05
\score { \keepWithTag #'Full \unfoldRepeats
\include 05/Score.ily
\midi { \tempo 4 = 72 }
} } %ends 05
…
Strange that I now get lots of errors I didn't get before moving
addQuote from 05/Continuo.ily into a 05/Midi.ily:
/home/jcharles/Partothek/Bach/246-Lukas-Passion/Lily/05/Midis.ily:2:1:
Error : wrong argument type for 1.
Expected music, found #unspecified
\addQuote basso { \unfoldRepeats { \include BassoM.ily } }
I think I'll unfortunately have to review the all of it, at least each
time there is a quoting (many of them?) with repeats, and increase the
number of involved files.
2- quoted parts don't go to midi by default, you have to at least add
\set Score.quotedEventTypes = #'(note-event rest-event).
This is issue 2250. Thanks for the workaround; it might be a proper fix
if we simply include it in the defaults.
(note that adding Stream-event to the list includes sluring which is bad
thing when used for melismas)
I didn't find it because searching for addquote…
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
quoteDuring: no midi nor repeats
Hi all!
While generating homework material for choristers, I notice the following:
1- unfoldRepeats doesn't work, neither on pdf nor in midi,
2- quoted parts don't go to midi by default, you have to at least add
\set Score.quotedEventTypes = #'(note-event rest-event).
This is with LP-2.17.24
Cheers,
Jean-Charles
\version 2.17.24
singer = \relative c' {
\repeat volta 2 { f4 g( a) r }
c1
}
\addQuote echo { \singer }
continuo = {
\set Score.quotedEventTypes = #'(note-event rest-event)
\quoteDuring echo {
\repeat volta 2 { s1 }
s1
}
}
\markup { Printed output }
\score {
\new Staff { \singer }
\new Staff { \new Voice { \continuo } }
\layout { }
}
\markup { With unfoldRepeats for MIDI }
\score {
\unfoldRepeats
\new Staff { \singer }
\new Staff { \new Voice { \continuo } }
\layout { }
\midi { }
}attachment: Quotes.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
buggy quoting as of first note
Hi all!
When using *quoteDuring*, I would expect the third staff not to
displayed at normal size, not as a *cueVoice*.
\version 2.17.22
music = { e'1 c' }
\addQuote quoted { \music }
quoteA = { R1 \quoteDuring quoted { s1 } }
quoteB = { \quoteDuring quoted { s1 } R1 }
\score {
\new Staff { \music }
\new Staff { \quoteA }
\new Staff { \quoteB }
\layout { }
}
Cheers,
Jean-Charles
attachment: quote.preview.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Figured bass brackets (bug?)
Hi!
I'm trying to reproduce editorial markings in figured bass like in the
enclosed image, but get nowhere even after having read the sources.
I admit I don't fully get the add_brackets function in
lily/figured-bass-engraver.cc and need someone to correct my commenting
of these lines I find in scm/define-music-display-methods.scm;
(define-display-method BassFigureEvent (figure parser)
;;a figure may be composed of 4 elements
(let ((alteration (ly:music-property figure 'alteration)) ;;an
alteration
(fig (ly:music-property figure 'figure)) ;;a
figure (number)
(bracket-start (ly:music-property figure 'bracket-start)) ;;an
opening bracket
(bracket-stop (ly:music-property figure 'bracket-stop))) ;;a
closing bracket
;;that should be follow this order
(format #f ~a~a~a~a
(if (null? bracket-start) [) ;;optional editorial
(cond ((null? fig) _) ;;reserved place in the column
((markup? fig) (second fig)) ;; fig: (number-markup
number)
(else fig))
(if (null? alteration)
;;no accidental
(cond ;;the different permitted accidentals
((= alteration DOUBLE-FLAT) --)
((= alteration FLAT) -)
((= alteration NATURAL) !)
((= alteration SHARP) +)
((= alteration DOUBLE-SHARP) ++)
(else )))
(if (null? bracket-stop) ] ;;optional editorial
I don't find anything wrong in my code
\version 2.17.22
\new Staff
\new Voice { g'1 }
\new FiguredBass \figuremode { [6 5]2 6 5] }
but don't see the last closing bracket despite its announcement.
Could anyone help me finish this BWV246 project?
TIA,
Jean-Charles
attachment: extract.pngattachment: Brackets.preview.png-*- mode: compilation; default-directory: ~/Partothek/Astuces/ -*-
Compilation started at Sun Jul 21 19:31:50
lilypond -dpreview Brackets.ly
GNU LilyPond 2.17.22
Traitement de « Brackets.ly »
Analyse...
(make-music
'SequentialMusic
'elements
(list (make-music
'ContextSpeccedMusic
'create-new
#t
'property-operations
'()
'context-type
'FiguredBass
'element
(make-music
'SequentialMusic
'elements
(list (make-music
'EventChord
'elements
(list (make-music
'BassFigureEvent
'duration
(ly:make-duration 1 0 1)
'bracket-start
#t
'figure
6)
(make-music
'BassFigureEvent
'duration
(ly:make-duration 1 0 1)
'bracket-stop
#t
'figure
5)))
(make-music
'EventChord
'elements
(list (make-music
'BassFigureEvent
'duration
(ly:make-duration 1 0 1)
'figure
6)
(make-music
'BassFigureEvent
'duration
(ly:make-duration 1 0 1)
'bracket-stop
#t
'figure
5
Interprétation en cours de la musique...
Pré-traitement des éléments graphiques...
Détermination du nombre optimal de pages...
Répartition de la musique sur une page...
Dessin des systèmes...
Sortie mise en page vers « Brackets.ps »...
Conversion à « ./Brackets.pdf »...
Sortie mise en page vers « Brackets.preview.eps »...
Conversion à « ./Brackets.preview.pdf »...
Conversion à « PNG »...
Compilation menée à son terme, avec succès.
Compilation finished at Sun Jul 21 19:31:52
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Broken x-refs in translated docs
Le 06/07/2013 19:48, Jean-Charles Malahieude disait : Le 06/07/2013 15:45, Phil Holmes disait : Jean-Charles Malahieude wrote... I'll try to narrow this large window (slowly because of my box's power) and let you know. If you have less of a restriction with download limits, http://download.linuxaudio.org/lilypond/binaries/documentation/ might be of help? Unfortunately there is no tarball between 2.12.3 (Jan. 2010) and 2.14.0 (June 2011). And the only from the 2.13 series on my box are 2.13.1 (May 2009) and 2.13.45 (Jan. 2011). I've no other option than rewinding... and try to have a successful compilation. Too bad, resetting more than 2 years ago is a good idea; each compile fails and I suspect upgrades to the compiling tools don't like this much of going back in time. Another track would be to try each modification of either lilypond-texi2html.init or extract_texi_filenames.py between 2010/01/13 and 2011/01/03 in order to locate the culprit. I'll do it as soon as the master-translation-staging merge is checked and pushed (80mn for each make make doc). Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Broken x-refs in translated docs
Le 01/07/2013 21:55, Phil Holmes disait : Jean-Charles Malahieude wrote... Most of the cross-references between manuals are broken in the translated documentation, split version. Do you think this is a new 2.17.21 problem, or has it been around a while? OK. Since I had a number of tarballs on my disk, I checked some of them. Cross references were worked well with 2.12.3 (new design), either LM-NR, NR-LM, NR-Snippets, NR-IR. The next I have is 2.13.45 and LM-NR is KO as well as NR-Snippets, but NR-LM and NR-IR work both. Note that all cross-manual references do work well with big-page; the problem only occurs with split manuals. I'll try to narrow this large window (slowly because of my box's power) and let you know. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Broken x-refs in translated docs
Le 06/07/2013 15:45, Phil Holmes disait : Jean-Charles Malahieude wrote... I'll try to narrow this large window (slowly because of my box's power) and let you know. If you have less of a restriction with download limits, http://download.linuxaudio.org/lilypond/binaries/documentation/ might be of help? Unfortunately there is no tarball between 2.12.3 (Jan. 2010) and 2.14.0 (June 2011). And the only from the 2.13 series on my box are 2.13.1 (May 2009) and 2.13.45 (Jan. 2011). I've no other option than rewinding... and try to have a successful compilation. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Broken x-refs in translated docs
Most of the cross-references between manuals are broken in the translated documentation, split version. I'm not able to work on this, but here is what I've diagnosed: For instance, in LM 2.1.2 Accidentals and key signatures in French from http://lilypond.org/doc/v2.17/Documentation/learning/accidentals-and-key-signatures.fr.html Pour en savoir plus sur les autres langues disponibles, consultez a name=index-Nom-des-notes-dans-d_0027autres-langues/a a href=../notation/note-names-in-other-languages.fr.htmlNom des notes dans d'autres langues/a. which spits a 404-not found but, in English: To use other names for varaccidentals/var, see a name=index-Note-names-in-other-languages/a a href=../notation/writing-pitches.html#note-names-in-other-languagesNote names in other languages/a. It is the same for every language except English. When I consider notation.fr.xref-map I read Nom des notes dans d'autres langues \t Note-names-in-other-languages \t Note-names-in-other-languages and in Spanish (notation.es.xref-map) Nombres de las notas en otros idiomas \t Note-names-in-other-languages \t Note-names-in-other-languages to be compared with notation.xref-map which states Note names in other languages \t Writing-pitches \t Note-names-in-other-languages It should instead state Nom des notes dans d'autres langues \t Writing-pitches \t Note-names-in-other-languages in order to generate ../notation/writing-pitches.fr.html#note-names-in-other-languages and Nombres de las notas en otros idiomas \t Writing-pitches \t Note-names-in-other-languages for ../notation/writing-pitches.es.html#note-names-in-other-languages Hoping it can be solved before 2.18, Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: How to debug std::bad_alloc
Le 12/06/2013 20:45, Jean-Charles Malahieude disait : Hi all, I've typeset BWV246 and printed an Urtext version without any problem. A modern version spits me (version 2.17.20) terminate called after throwing an instance of 'std::bad_alloc' what(): St9bad_alloc For anyone interested, a tarball of the sources is available on demand (87ko). As soon as I add another score to number 42, I get this very message, and invoking with -l DEBUG is of no help for me. TIA, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
How to debug std::bad_alloc
Hi all, I've typeset BWV246 and printed an Urtext version without any problem. A modern version spits me (version 2.17.20) terminate called after throwing an instance of 'std::bad_alloc' what(): St9bad_alloc I think I've narrowed the problem to a particular score which, when alone, compile fine. I need some help in order to understand what's going wrong. The only differences are: - using \keepWithTag #'Full for modern as opposed to\keepWithTag #'(Full Urtext) for Urtext - the global size - some paper block variables inner-margin = 1.2\cm % for Urtext, 1cm outer-margin = 1.3\cm % for Urtext, 1cm binding-offset = 0.6\cm %for Urtext, 0.4cm % top-system-spacing #'basic-distance = #10 % for Urtext % top-markup-spacing #'basic-distance = #10 % for Urtext % last-bottom-spacing #'basic-distance = #10 % for Urtext - nonstaff-unrelatedstaff-spacing minimum-distance at 2 in Urtext, 3 otherwise - singers clefs TIA, JeanCharles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Footnote oddity
Hi all,
Here is something very odd when the text of a footnote is spread over
more than one line: there are as many marks as the number of lines.
Using auto-footnote, each line get numbered.
attachment: oops.manual.png\version 2.17.16
#(set-default-paper-size a6)
FootA = \markuplist { \justified-lines {
% \super *)
Lorem ipsum dolor sit amet, consectetur adipisicing
elit, sed do eiusmod tempor incididunt ut labore et dolore magna
aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco
laboris nisi ut aliquip ex ea commodo consequat.
}}
\markuplist { \justified-lines {
Lorem ipsum dolor sit amet, consectetur adipisicing
elit, sed do eiusmod tempor incididunt ut labore et dolore magna
\auto-footnote aliqua. \FootA
%aliqua.\footnote \super *) \FootA
Ut enim ad minim veniam, quis nostrud exercitation ullamco
laboris nisi ut aliquip ex ea commodo consequat.
}}___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Footnote oddity
Hi all,
Here is something very odd when the text of a footnote is spread over
more than one line: there are as many marks as the number of lines.
Using auto-footnote, each line get numbered.
Hit the wrong button...
Cheers,
Jean-Charles
attachment: oops.manual.png\version 2.17.16
#(set-default-paper-size a6)
FootA = \markuplist { \justified-lines {
% \super *)
Lorem ipsum dolor sit amet, consectetur adipisicing
elit, sed do eiusmod tempor incididunt ut labore et dolore magna
aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco
laboris nisi ut aliquip ex ea commodo consequat.
}}
\markuplist { \justified-lines {
Lorem ipsum dolor sit amet, consectetur adipisicing
elit, sed do eiusmod tempor incididunt ut labore et dolore magna
\auto-footnote aliqua. \FootA
%aliqua.\footnote \super *) \FootA
Ut enim ad minim veniam, quis nostrud exercitation ullamco
laboris nisi ut aliquip ex ea commodo consequat.
}}
Oops-footnote.pdf
Description: Adobe PDF document
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Footnote oddity
Le 18/05/2013 18:29, David Kastrup disait :
Jean-Charles Malahieude address@hidden writes:
Here is something very odd when the text of a footnote is spread over
more than one line:
That description is quite misleading. You are not spreading the text
of a footnote over more than one line but are rather creating a markup
_list_ containing multiple markups. Then you call \footnote with this
markup list as last argument, and since \footnote expects a single
markup, LilyPond creates one \footnote call for every element in the
markup list.
Thanks. It is now very clear.
Here is how I succeed (it might be worth a snippet):
FootA = \markup { \justify {
Lorem ipsum dolor sit amet, consectetur adipisicing
elit, sed do eiusmod tempor incididunt ut labore et dolore magna
aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco
laboris nisi ut aliquip ex ea commodo consequat.
\hspace #30 % for ragged-righting
\fill-line {
\score {
\new Staff \relative c'' { c1 }
\layout { ragged-right = ##t indent = 0 }
}
}
Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich.
}}
Cheers,
Jean-Charles
ps: forgot the list
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
combining quotes and tags
Hi all,
I've got a problem when combining \include \tag and \quoteDuring :
where should I put the addQuote statement? This is on a big project
(notes and lyrics in separate files for everybody). I tried to
instantiate it in the quoting file, but with no result.
Nevertheless, trying to find my path and a solution, I now block on the
following: I would expect the E from the sopranos to appear
on the violin staff. Am I doing something wrong?
-- 8 --
\version 2.17.15
sopran = \relative c' {
f1
\tag #'Full { R1^one }
\tag #'(Chor Part) { R1^foo }
e^sop
f1
}
violin = \relative c' {
d1
\tag #'Full { s1*2 }
\tag #'Part { R1^bar \quoteDuring Soprano { s1 } }
a1
}
\addQuote Soprano { \sopran }
\score {
\keepWithTag #'Part
\new Staff { \violin }
}
-- 8 --
which results in
D bar foo A
instead of D bar E A
TIA,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
lilypond.pot polluted
Hi John and all, I just noticed that, because the out of tree build, lilypond.pot gets polluted by personal path, what does not happen with an in tree build. e.g. we get, when out of tree : #: parser.yy:174 parser.yy:188 /home/jcharles/GIT/Mentor/lily/parser.yy:174 #: /home/jcharles/GIT/Mentor/lily/parser.yy:188 msgid Too much lookahead msgstr #: parser.yy:466 parser.yy:736 parser.yy:803 #: /home/jcharles/GIT/Mentor/lily/parser.yy:466 #: /home/jcharles/GIT/Mentor/lily/parser.yy:736 #: /home/jcharles/GIT/Mentor/lily/parser.yy:803 msgid bad expression type msgstr instead of just : #: parser.yy:174 parser.yy:188 msgid Too much lookahead msgstr #: parser.yy:466 parser.yy:736 parser.yy:803 msgid bad expression type msgstr As a matter of fact, only lily/lexer.ll and lily/parser.yy are concerned with the duplication. I suspect it comes from ALL_PO_SOURCES which gets defined in stepmake/stepmake/po-targets.make, but am not sure how to fix it. Once again, this does not occur when NOT building out of tree (you know I prefer a local clone). Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: LSR is not at the stable release level
I can't vouch for Fedora since they have made it TOTALLY IMPOSSIBLE to figure out what versions of software they use. Going on their web page, you get just bounced from one buzzphrase page to another, and I was not going to download a whole distribution iso just to check what versions they might be offering. http://pkgs.fedoraproject.org/cgit/lilypond.git/log/ says 2.16.0 Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR-4.1.6. automatic saving of line breaking configuration
Le 11/09/2012 00:29, Trevor Daniels disait : Jean-Charles Malahieude wrote Monday, September 10, 2012 6:57 PM The last paragraph of the line breaking section (l. 1460 of spacing.itely) (which gets a @c TODO check this) puts me into trouble. I think it should be deleted (I've already @ignored it in French): Yes, it should be deleted. The section on two-pass spacing was deleted in 81f5263fa1b6adf642b06970cd34e10d4635495d 2009-08-23 Remove two-pass spacing code and documentation. but this paragraph seems to have been missed. May I remove it directly? Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Doc: NR-4.1.6. automatic saving of line breaking configuration
Hi all, The last paragraph of the line breaking section (l. 1460 of spacing.itely) (which gets a @c TODO check this) puts me into trouble. I think it should be deleted (I've already @ignored it in French): It was reintroduced with commit 87518c6b29f146a903bb6915ce75a014b727 Re-add chapter on two-pass spacing (but warn that it is deprecated) but stands it is a new feature (advocated with 2.7.29). The reg-test (page-layout-twopass.ly), that might have helped to understand how this worked, has been deleted with commit 2f38710a2b40a24977441aa7faa05b6ab132f3cf Rewrite the vertical layout of staves/systems. by the time of 2.13.30. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Length of a footnote note
Hi all,
There seems to be no limitation to the length of the annotation string
of a footnote.
It would be nice to be able to spread it over several lines, even
without taking the mark part into account.
Could anyone help me to construct a function to deal with that?
Cheers,
Jean-Charles
\version 2.16.0
\paper {
footnote-auto-number = ##f
}
lorem = \wordwrap-lines { Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. }
\book {
\score {
\markup { Lorem ipsum \footnote * * Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. dolor... }
\relative c' {
a'1
}
}
\pageBreak
\score {\markup { Lorem ipsum \footnote * * \lorem dolor... }
\relative c' {
a'1
}
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Length of a footnote note
Sorry, I tried something else in the middle.
Here it is.
\version 2.16.0
\paper {
footnote-auto-number = ##f
}
lorem = \markup { \justify { Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. } }
\book {
\lorem
\markup { Lorem ipsum \footnote * * Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. dolor... }
\score {
\relative c' {
a'1
}
}
\pageBreak
\markup { Lorem ipsum \footnote * * \lorem dolor... }
\score {
\relative c' {
a'1
}
}
}
footnote-long.pdf
Description: Adobe PDF document
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Length of a footnote note
David Kastrup writes:
Does something like
\version 2.16.0
\paper {
footnote-auto-number = ##f
}
lorem = \markup { \justify { Lorem ipsum dolor sit amet, consectetur
adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna
aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris
nisi ut aliquip ex ea commodo consequat. } }
\book {
\lorem
\markup { Lorem ipsum \footnote * \justify { * Lorem ipsum dolor sit
amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore
et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation
ullamco laboris nisi ut aliquip ex ea commodo consequat. } dolor... }
\score {
\relative c' {
a'1
}
}
\pageBreak
\markup { Lorem ipsum \footnote * \put-adjacent #X #LEFT \lorem *
dolor... }
\score {
\relative c' {
a'1
}
}
}
give you ideas?
Many thanks! It works like a charm.
I was really upset by the quoted string as being the way to introduce
the annotation and did not come to such a simple workaround. And I
wanted to avoid the use of another variable in my project just for this
particular case.
Thanks also for teaching me how to use \put-adjacent:
I can even type
Lorem ipsum \footnote * \put-adjacent #X #LEFT \justify {the long
text} *
Nice way to put whatever plus text in the annotation.
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [Feature request] attach lilypond code in pdf.
Le 09/07/2012, Phil Holmes disait : [...] Hi, I'm a pretty much new user of lilypond and I have an idea for a almost dummy new feature: automatically attach lilypond code in pdf. With pdf files it is possible to attach a file into it. What a great idea! the basic function in LilyPond is given with \include test.ly \markup \verbatim-file #test.ly now I don't know what you mean with automatically - should it be attached every time? on a new page, in another (pdf) file? or did you mean something else? Eluze I do think this would do what the user wants, if we did not need to put the filename in explicitly. Is there any way of getting the filename into a variable? It might be OK when _one_ score means _one_ file. I see a problem when you deal with a full book and, for instance, have 646 files spread in 53 folders. You should then enclose an archive of the tree. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
[Enhancement request] NoteNames speaks only Dutch
Hi all,
How would it be possible for the note-Name-engraver to change his mind
thanks to an additional argument or, at least, adopt the specified language?
\language italiano
scale = \relative do' {
lab4 sid dobb redd
mi4 fa solb lad
}
\new Staff {
\scale
\context NoteNames {
\scale
}
}
gives: aes bis ceses disis e f ges ais
I was expecting at least: lab sid dobb redd mi fa solb lad
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Link to PostScript Language Reference broken
Le 24/05/2012 13:01, Urs Liska disait : In CG, 7.2.6 PostScript The link to the PostScript Language Reference http://www.adobe.com/devnet/postscript/pdfs/PLRM.pdf is broken. Unfortunately I didn't manage to find a working link. I hope you refer to CG 10.2.7. It is referenced, if I'm not mistaken, as the first item on this page: http://www.adobe.com/devnet/postscript.html which links to: http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/postscript/pdfs/PLRM.pdf HTH, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: issues 2266 and 1721
Le 18/04/2012 16:29, Phil Holmes disait : - Original Message - From: Jean-Charles Malahieude I think that if everything goes well, Documentation/snippets.splittexi.log should not weight that much with all those lines like ** `Pitches' is up for `Pitches: Separating key cancellations from key signature changes', but has no menu entry for this node ** No node following `Pitches: Separating key cancellations from key signature changes' in menu, but `Pitches: Transposing pitches with minimum accidentals (Smart transpose)' follows in sectionning I have no idea _why_ these things happen: I was simply showing a possible reason for those errors occurring. It seemed to me a possible way of fixing the errors. One more thing: I wanted to know what happens when trying to build a translated Snippets, which generates out-www/.../snippets/pitches.fr.html with unnumberedsubsec translated as soon as exists a doctitlefr, and I notice that Documentation/fr/snippets.splittexi.log weights exactly the same as the English version with its 1618 lines. The only thing that differs is the file-name part (take into account that Altering the length of beamed stems doesn't have a texidocfr so remains in English): ** `Pitches: Adding ambitus per voice' doesn't appear in menus ** `Pitches' is up for `Pitches: Adding ambitus per voice', but has no menu entry for this node ** No node following `Pitches: Adding ambitus per voice' in menu, but `Pitches: Altering the length of beamed stems' follows in sectionning vs. ** `Pitches: Un ambitus par voix' doesn't appear in menus ** `Pitches' is up for `Pitches: Un ambitus par voix', but has no menu entry for this node ** No node following `Pitches: Un ambitus par voix' in menu, but `Pitches: Altering the length of beamed stems' follows in sectionning Oh, wait a moment! I just realize this is absolutely normal, since there is no sub-menu in this file. So, just forget those 1618 lines! All of this might just come from the macroization of the noding, mixed between snippets.tely and extract_texi_filename.py Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: issues 2266 and 1721
Le 15/04/2012 14:56, Phil Holmes disait :
- Original Message - From: Jean-Charles Malahieude
lily...@orange.fr
To: Phil Holmes m...@philholmes.net
Cc: Lily Bugs bug-lilypond@gnu.org; lilypond-devel
lilypond-de...@gnu.org
Sent: Saturday, April 14, 2012 5:46 PM
Subject: Re: issues 2266 and 1721
It might have something to do with the way both glossary and snippet
are built: I just noticed, on fresh make doc on staging (as of
312f7ebc83ec9fb8cbbddfcf78b65a8502c16ab2 ), that
music-glossary.splittexi.log weight is 0 byte, but
snippets.splittexi.log is 190.9 Kio (1618 lines).
I reckon I now know why this is happening. We get the same error if the
text of pitches.itely is cut down to:
@node Hauteurs
@section Hauteurs
@translationof Pitches
Morceaux choisis :
@rlsrnamed{Pitches,Hauteurs}.
The error goes away if @translationof Pitches is changed to
@translationof Pitcher. So I think @rlsrnamed{Pitches,Hauteurs} is
translated automatically to @rlsrnamed{Hauteurs,Hauteurs} and the system
can't then find the node Hauteurs.
What do you think?
This might make one point.
But what is still strange is:
in fr/learning/common-notation.itely I read
@node Altérations et armure
@subsection Altérations et armure
@translationof Accidentals and key signatures
and, in fr/notation/pitches.itely,
@rlearning{Altérations et armure}
which points to
learning/accidentals-and-key-signatures.fr.html
never to learning/Altérations-et-armure.fr.html which by the way doesn't
exist.
So, why is it tempted to translate the base file name only when dealing
with snippets?
Don't forget I've no skill in programming; I'm just trying to understand
what is going on. Would it be possible that the origin being the macros
at the head of snippets.tely? or something weird in conjunction with
extract_texi_filenames.py?
I think that if everything goes well,
Documentation/snippets.splittexi.log should not weight that much with
all those lines like
** `Pitches' is up for `Pitches: Separating key cancellations from key
signature changes', but has no menu entry for this node
** No node following `Pitches: Separating key cancellations from key
signature changes' in menu, but `Pitches: Transposing pitches with
minimum accidentals (Smart transpose)' follows in sectionning
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: issues 2266 and 1721
Le 13/04/2012 19:54, Phil Holmes disait :
- Original Message - From: Jean-Charles Malahieude
lily...@orange.fr
To: Lily Bugs bug-lilypond@gnu.org; lilypond-devel
lilypond-de...@gnu.org
Sent: Saturday, March 31, 2012 6:47 PM
Subject: Re: issues 2266 and 1721
Hi all,
I just noticed something:
1- I overuse of @rlsrnamed{original,translated} in order to present a
translated link towards snippets, like @rlsrnamed{Pitches,Hauteurs}.
1-1 When in NR, this produces tons of lines in the logs like
WARNING: Unable to find node 'translated' in book snippets.
@rlsrnamed{Pitches,Hauteurs} is snippets/hauteurs.fr.html which
doesn't exist, so I get nowhere.
1-2 When in LM, there in nothing in the logs
@rlsrnamed{Pitches,Hauteurs} is snippets/pitches.fr.html where I
want to go, but non success.
2- I overuse of @rglosnamed{original,translated} in order to present a
translated link towards glossary both in LM and NR, and I never get
any kind of warning or error, and the link is effective.
@rglosnamed{{Pitch names,Noms des notes} is
music-glossary/pitch-names.fr.html where I want to arrive and it's a
perfect landing.
My questioning is:
Why a same macro could behave differently when in LM or in NR, and
why, though they look identical do they work differently according to
the target manual?
Cheers,
Jean-Charles
I thought I'd have a look at this, and have just been doing so. I think
the difference between learning and notation is that there is no
instance of @rlsrnamed or @rlsr in learning, whereas it's used
extensively in notation. So there's no difference in the file types,
except it's used in one and not in the other
It might have something to do with the way both glossary and snippet are
built: I just noticed, on fresh make doc on staging (as of
312f7ebc83ec9fb8cbbddfcf78b65a8502c16ab2 ), that
music-glossary.splittexi.log weight is 0 byte, but
snippets.splittexi.log is 190.9 Kio (1618 lines).
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: issues 2266 and 1721
Le 13/04/2012 19:54, Phil Holmes disait :
- Original Message - From: Jean-Charles Malahieude
I just noticed something:
1- I overuse of @rlsrnamed{original,translated} in order to present a
translated link towards snippets, like @rlsrnamed{Pitches,Hauteurs}.
1-1 When in NR, this produces tons of lines in the logs like
WARNING: Unable to find node 'translated' in book snippets.
@rlsrnamed{Pitches,Hauteurs} is snippets/hauteurs.fr.html which
doesn't exist, so I get nowhere.
1-2 When in LM, there in nothing in the logs
@rlsrnamed{Pitches,Hauteurs} is snippets/pitches.fr.html where I
want to go, but non success.
2- I overuse of @rglosnamed{original,translated} in order to present a
translated link towards glossary both in LM and NR, and I never get
any kind of warning or error, and the link is effective.
@rglosnamed{{Pitch names,Noms des notes} is
music-glossary/pitch-names.fr.html where I want to arrive and it's a
perfect landing.
My questioning is:
Why a same macro could behave differently when in LM or in NR, and
why, though they look identical do they work differently according to
the target manual?
I thought I'd have a look at this, and have just been doing so. I think
the difference between learning and notation is that there is no
instance of @rlsrnamed or @rlsr in learning, whereas it's used
extensively in notation. So there's no difference in the file types,
except it's used in one and not in the other
The fact is that I've added a @rlsrnamed somewhere in the LM in order to
test.
Secondly, both @rglosnamed and @rlsrnamed should have the same effect:
neither glossary nor snippets are translated, an I wonder why I get no
problem at all with @rglosnamed as opposed to @rlsrnamed.
@macro rglosnamed{TEXT,DISPLAY}
@vindex \TEXT\
@ref{\TEXT\,,\DISPLAY\,music-glossary,Glossaire}
@end macro
@macro rlsrnamed{TEXT,DISPLAY}
@ref{\TEXT\,,\DISPLAY\,snippets,Morceaux choisis}
@end macro
and even adding a @vindex \TEXT\ to rlsrnamed doesnt change anything.
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2391 in lilypond: Add Appendix entry for Predefined Paper Sizes
Le 02/04/2012 00:19, Colin Hall disait :
On Sun, Apr 01, 2012 at 03:34:27PM +0200, Jean-Charles Malahieude wrote:
Unfortunately, the rewriting of NR-4.1.2 Paper size and automatic
scaling results in disappearance of the standard paper sizes which
now get only mentioned in an appendix.
This appendix needs a @ref (will be there in French after I have committed).
Yes, comparing those pages for 2.14 and 2.15.35:
Yes, I can see what you mean.
Could you submit a documentation suggestion, as set out here:
see enclosed
Cheers,
Jean-Charles
diff --git a/Documentation/notation/spacing.itely b/Documentation/notation/spacing.itely
index 68208d2..05509f5 100644
--- a/Documentation/notation/spacing.itely
+++ b/Documentation/notation/spacing.itely
@@ -233,7 +233,8 @@ placed @emph{before} any other functions used within the same
Paper sizes are defined in @file{scm/paper.scm}, and while it is
possible to add custom sizes, they will be overwritten on subsequent
-software updates.
+software updates. The available paper sizes are listed in
+@ref{Predefined paper sizes}.
@c An appendix entry exists for paper sizes but is not auto-generated
@@ -268,7 +269,8 @@ The music output will @emph{not} be rotated, just the paper size.
@seealso
Notation Reference:
-@ref{Automatic scaling to paper size}.
+@ref{Automatic scaling to paper size},
+@ref{Predefined paper sizes}.
Installed Files:
@file{scm/paper.scm}.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: issues 2266 and 1721
Le 01/04/2012 00:23, Colin Hall disait : On Mar 31, 2012 at 07:47PM, Jean-Charles Malahieude wrote: [...] My questioning is: Why a same macro could behave differently when in LM or in NR, and why, though they look identical do they work differently according to the target manual? Hi Jean-Charles, and thanks for reporting your problem. Are you reporting a problem against a released version of Lilypond? Is so, please let me know which version and then I can raise an issue tracker for the unexpected behaviour. If you are working with unreleased code then I think I should allow the developers to respond to your queries. This is just what I observe when building docs, that might be useful for both http://code.google.com/p/lilypond/issues/detail?id=1721 and http://code.google.com/p/lilypond/issues/detail?id=2266 I might add that it could be something related to the way of noding that differs between Glossary and Snippets (both being untranslated manuals)? I had some warnings related to Internals, that disappeared yesterday. I'll do a clean build in order to check it was not by accident. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: issues 2266 and 1721
Hi all,
I just noticed something:
1- I overuse of @rlsrnamed{original,translated} in order to present a
translated link towards snippets, like @rlsrnamed{Pitches,Hauteurs}.
1-1 When in NR, this produces tons of lines in the logs like
WARNING: Unable to find node 'translated' in book snippets.
@rlsrnamed{Pitches,Hauteurs} is snippets/hauteurs.fr.html which
doesn't exist, so I get nowhere.
1-2 When in LM, there in nothing in the logs
@rlsrnamed{Pitches,Hauteurs} is snippets/pitches.fr.html where I want
to go, but non success.
2- I overuse of @rglosnamed{original,translated} in order to present a
translated link towards glossary both in LM and NR, and I never get
any kind of warning or error, and the link is effective.
@rglosnamed{{Pitch names,Noms des notes} is
music-glossary/pitch-names.fr.html where I want to arrive and it's a
perfect landing.
My questioning is:
Why a same macro could behave differently when in LM or in NR, and why,
though they look identical do they work differently according to the
target manual?
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Combining lyrics lines
Le 19/03/2012 12:13, Eluze disait : I think this needs some adaptation: - the lyrics mum and dad don't fit to the voices - should they be inversed!? Oops! I'm so used to the inverted situation with my parents! - Reedmace Star had proposed to use \voiceOne and \voiceTwo (which is quite usual when notating 2 voices in 1 staff): this helps the singers to locate their part (and also eliminates the warnings about clashing notes). But with the stems going down the lyrics are moved downwards, too, and they don't seem to be on one line anymore. (maybe adding some kind of padding could help). Depending on the ambitus, \voiceXXX is not optimal, and there should be few warnings about clashing note columns. By the way, what I've used with King Arthur is a third voice with lyrics aligned above for the overlapping (see page 106 of the full score available on CPDL, bar 122). I also think there are some LilyPond features that will not work in the normal way and should be discussed: - stanza numbers Having tried it, it appears that the one who doesn't sing on the first beat in the line is not mentioned (bug?). - vocalName (shortVocalName) Of no use in such a case: when a soloist shares the staff with the choir part, there is usually just a markup when switching (solo/tutti), or you change the instrument/vocal name which is attached to the *staff*. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Combining lyrics lines
Le 17/03/2012 11:14, Reedmace Star disait : In the first line, Alice and Eve alternate strictly in singing, so their lyrics get collapsed: ALICE EVE ALICE EVE maybe that the second words are After the manual line break, Alice cuts off Eve with a bit of overlap. Their lyrics stay on different lines, which makes sense: EVE ALICE Shut up, you fool! ...and then I was like- I wished I had found it myself... Would be worth a selected snippet in NR 2.1.2 Techniques specific to lyrics, Placing lyrics vertically? http://lists.gnu.org/archive/html/lilypond-user/2012-03/msg00508.html Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Combining lyrics lines
Le 18/03/2012 12:38, James disait : Hello, On 18 March 2012 11:33, Jean-Charles Malahieude wrote: Le 17/03/2012 11:14, Reedmace Star disait : In the first line, Alice and Eve alternate strictly in singing, so their lyrics get collapsed: ALICE EVE ALICE EVE maybe that the second words are After the manual line break, Alice cuts off Eve with a bit of overlap. Their lyrics stay on different lines, which makes sense: EVE ALICE Shut up, you fool! ...and then I was like- I wished I had found it myself... Would be worth a selected snippet in NR 2.1.2 Techniques specific to lyrics, Placing lyrics vertically? http://lists.gnu.org/archive/html/lilypond-user/2012-03/msg00508.html I don't understand this request for a 'snippet', are you saying it already exists as a snippet and you want it in the NR or that you want a new snippet created *as well*? If it is the latter, and someone can give me a 'clear' explanation of what this snippet shows (so I can write a concise texidoc entry) I can arrange that, else if the snippet already exists tell me the name of it and I can add it very easily. Searching the LSR does not return it, and I think it is worth to have it in the NR. I would sort of call it a partcombine for lyrics: it often happens that a soloist shares a staff with a choir part (let's say the diva and the soprani) when they sing alternatively, or two characters like in Reedmace Star's example. The fact is that Lily place /two/ lines of lyrics when the change appears on the same system. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Combining lyrics lines
Le 18/03/2012 14:53, James disait : Jean-Charles, I don't understand how Lyrics work in LilyPond or what your last paragraph means (it is meaningless to me, sorry - I play trumpet, I don't sing, so never need to read or use lyrics in a score) I was hoping that you could give me a texidoc string I could simply copy.paste into the example at http://lists.gnu.org/archive/html/lilypond-user/2012-03/msg00508.html Then I can create a snippet from that. I can't articulate it myself. Please find enclosed a draft. It is much less complicated than what Keith O'Hara provided in http://lists.gnu.org/archive/html/lilypond-user/2010-12/msg00674.html which might help you understand what singers might read. You'll see what I mean by commenting the layout overrides. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Combining lyrics lines
Le 18/03/2012 14:53, James disait :
Jean-Charles,
I don't understand how Lyrics work in LilyPond or what your last
paragraph means (it is meaningless to me, sorry - I play trumpet, I
don't sing, so never need to read or use lyrics in a score)
I was hoping that you could give me a texidoc string I could simply
copy.paste into the example at
http://lists.gnu.org/archive/html/lilypond-user/2012-03/msg00508.html
Then I can create a snippet from that. I can't articulate it myself.
Please find enclosed a draft. It is much less complicated than what
Keith O'Hara provided in
http://lists.gnu.org/archive/html/lilypond-user/2010-12/msg00674.html
which might help you understand what singers might read.
You'll see what I mean by commenting the layout overrides.
Cheers,
Jean-Charles
ps: forgot the file!
\version 2.14.0
texidoc = The space engine preserves by default the space for the
empty sections of lyrics, so that the lines remain consistently spaced.
When you want to use a separate @code{Voice} context for each
singer, even though the melodies usually don't overlap, you might want
to let interrupted lyrics collapse to a single line.
The layout overrides may still be useful for scores where there is
occasional small overlap between the voices, though.
In order to easily identify who sings, one of the lyrics may be
displayed in italics.
doctitle = Combining lyrics
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'nonstaff-nonstaff-spacing
#'minimum-distance = ##f
\override VerticalAxisGroup #'nonstaff-unrelatedstaff-spacing
#'minumum-distance = ##f
\override LyricText #'minimum-Y-extent = #'(-0.6 . 2.0)
}
}
\new Staff
\new Voice = mum { f'4^mum g' r2 | s1 | \break a'2 g' | f'1 }
\new Voice = dad { s1| a'2^dad g' | e'1 }
\new Lyrics \lyricsto dad \lyricmode {
\override LyricText #'font-shape = #'italic
may -- be... to -- mor -- row }
\new Lyrics \lyricsto mum \lyricmode { let's say now }
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 2410 in lilypond: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs
New issue 2410 by address@hidden: Doc: Translation NR 5.1.4 - Typo for engraver in Fr/Ja/Es and De docs http://code.google.com/p/lilypond/issues/detail?id=2410 http://lilypond.org/doc/v2.14/Documentation/notation/modifying-context-plug_002dins First Paragraph. 'Key_signature_engraver' does not exist. Should be 'Key_engraver' Fixed in French, as per commit on translators' branch 3401c21cf14672c016a793400626d3b574a97063 Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \grace after \cadenzaOff suppresses auto-beams
Le 06/03/2012 01:04, Colin Hall disait :
[...]
Have you isolated a bug here?
I'm not sure about it but, thanks to the Scheme tutorial I just finished
to translate I'm now not so blind:
\displayMusic {
c1
\cadenzaOn d1 e \cadenzaOff
f1 }
and it looks like the D and E don't belong to the list of elements
attached to the right SequentialMusic.
As I understand it, here are the steps:
1 open a sequence MAIN
1.1 play a C
1.2 open a sequence (the cadenza)
1.2.1 define its properties
1.2.1.1 no timing
1.2.1.2 no beaming
1.3 play a D
1.4 play a E
1.5 open a sequence
1.5.1 define its properties
1.5.1.1 activate timing
1.5.1.2 synchronize the clock
1.5.1.3 activate beaming
1.6 play a F and close MAIN
I believe that, at least, steps 1.3 to 1.5 should be sub-parts of 1.2,
thus not sure about step 1.5.1.2
Please correct me if I'm wrong.
Cheers,
Jean-Charles
(make-music
'SequentialMusic
'elements
(list (make-music
'NoteEvent
'duration
(ly:make-duration 0 0 1 1)
'pitch
(ly:make-pitch -1 0 0))
(make-music
'SequentialMusic
'elements
(list (make-music
'ContextSpeccedMusic
'context-type
'Timing
'element
(make-music
'PropertySet
'value
#f
'symbol
'timing))
(make-music
'ContextSpeccedMusic
'context-type
'Timing
'element
(make-music
'PropertySet
'value
#f
'symbol
'autoBeaming
(make-music
'NoteEvent
'duration
(ly:make-duration 0 0 1 1)
'pitch
(ly:make-pitch -1 1 0))
(make-music
'NoteEvent
'duration
(ly:make-duration 0 0 1 1)
'pitch
(ly:make-pitch -1 2 0))
(make-music
'SequentialMusic
'elements
(list (make-music
'ContextSpeccedMusic
'context-type
'Timing
'element
(make-music
'PropertySet
'value
#t
'symbol
'timing))
(make-music
'ContextSpeccedMusic
'context-type
'Timing
'element
(make-music
'PropertySet
'value
(ly:make-moment 0 1 0 1)
'symbol
'measurePosition))
(make-music
'ContextSpeccedMusic
'context-type
'Timing
'element
(make-music
'PropertySet
'value
#t
'symbol
'autoBeaming
(make-music
'NoteEvent
'duration
(ly:make-duration 0 0 1 1)
'pitch
(ly:make-pitch -1 3 0
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: \grace after \cadenzaOff suppresses auto-beams
And I just found a solution that works even better for me...
%%% previous stuff
\cadenzaOff
\bar |
\appoggiatura b4
\set Timing.measurePosition = #(ly:make-moment 0 4)
%%% subsequent stuff
...by setting the measurePosition *after* the grace/appoggiatura and
before the first beat of the measure, the beams remain intact and
the warning disappears. Huzzah.
But still strange if you consider the bar numbering (the same goes
with your accidentals' problem):
\relative c' {
\override Score.BarNumber #'break-visibility = #'#(#t #t #t)
\set Score.currentBarNumber = #11
\bar
\time 2/4
c2
\cadenzaOn
c2 d8-[ e \bar | f g-]
\cadenzaOff
\bar |
\grace b8 \bar |
a4. \bar | gis8 \bar |
e'8 \bar | e \bar | e \bar | e
}
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Windows scheme sandbox
Hi! While translating the Scheme tutorial, I tried in a Windows (XP sp3) virtual machine where I've installed 2.15.30 to access the sandbox. Here is the output: ===8=== C:/Program Files/LilyPond/usr/share/lilypond/current/current/ly/scheme-sandbox.ly Parsing... C:/Program Files/LilyPond/usr/share/lilypond/current/current/ly/scheme-sandbox.ly:2:1: Error: Guile signaled an error for the expression beginning here # use-modules ice-9 readline readline is not provided in this Guile installation C:/Program Files/LilyPond/usr/share/lilypond/current/current/ly/scheme-sandbox.ly:3:1: Error: Guile signaled an error for the expression beginning here # activate-readline Unbound variable: activate readline guile ===8=== FWIW, GUILE_LOAD_PATH and path are as requested. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2336 in lilypond: Patch: Add layout changing command \layout-from for getting context defs from music
Ok, what do people say to the following:
a) rename settingsFrom to \context-like
b) rename \layout-from to \output-like
Then we may do things like
\midi {
\Score { \context-like { \tempo 4 = 80 } }
}
\layout {
\output-like { \accidentalStyle modern }
}
Is that better than xxx-from ?
I totally agree.
It is an evidence that \context-like deals with contexts and,
from a non English native user point of view, I know that layout deals
with printable; therefore I would get confused to be allowed to mention
\layout-from in a midi block...
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
make doc problem
Hi all! Not only that I can no longer use -j on a first build (it is OK on the next builds), which means 40' for a make doc LANGS='fr' and about 2 hours for all languages, I now have to make doc-clean in order to view a corrected typo. I've tried a touch masterfile.tely before make doc but it doesn't change anything. Does anybody else experiment this as well? Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: make doc problem
Le 22/01/2012 19:32, Julien Rioux disait : On 22/01/2012 1:19 PM, Jean-Charles Malahieude wrote: Hi all! Not only that I can no longer use -j on a first build (it is OK on the next builds), [...] I can't run -j, I have a single core. Can you please report more precisely why you can no longer use it? I make a clean and let you now... -- Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: make doc problem
Le 22/01/2012 20:22, Julien Rioux disait : On 22/01/2012 2:15 PM, Julien Rioux wrote: On 22/01/2012 2:11 PM, Jean-Charles Malahieude wrote: What I've done to check is: open Documentation/fr/usage/running.itely add the five X at the beginning of the first text line XCe chapitre passe en revue ce qui se passe lorsque vous lancez LilyPond. save it and make -j3 doc LANGS='fr' File out-www/offline-root/Documentation/usage/running-lilypond.fr.html still shows Ce chapitre passe en revue ce qui se passe lorsque vous lancez LilyPond. -- Jean-Charles You're right, I forgot that I caused that. Give me a moment I will push the fix to staging... Regards, Julien Done: 930dbeff8f5d31faa9654365c8ed84a30e489e83 Hope this fixes it for you as well. Yes, many thanks! -- Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2079 in lilypond: website links to 2.13
Le 05/12/2011 11:44, Graham Percival disait :
New issue 2079 by address@hidden: website links to 2.13
http://code.google.com/p/lilypond/issues/detail?id=2079
there's links to doc/v2.13/ on this page:
http://lilypond.org/help-us.html
obviously some hard-coded version number somewhere needs to be updated.
I'm unable to help, but what I can say is that it works fine on a local
build (reaches the appropriate page). I nevertheless get:
===
$ git grep -n 'v2.13'
Documentation/contributor/release-work.itexi:157:@code{graham} owns
v2.13; @code{han-wen} owns v2.12.
Documentation/contributor/website-work.itexi:312:mkdir -p
$HOME/public_html/doc/v2.13/
Documentation/contributor/website-work.itexi:313:mv
out-www/online-root/* $HOME/public_html/doc/v2.13/
Documentation/es/web/news-front.itexi:121:@uref{http://lilypond.org/doc/v2.13/Documentation/changes/index.html}
Documentation/lilypond-texi2html.init:1431:$href =
../../doc/v2.13/Documentation/web/.$href;
Documentation/web/news.itexi:222:@uref{http://lilypond.org/doc/v2.13/Documentation/changes/index.html}
Documentation/web/server/robots.txt:19:Disallow: /doc/v2.13/
scripts/build/create-version-itexi.py:18:# these links are relative from
the v2.13 docs
===
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
[Translation] Czech xrefs towards Notation Reference
Hallo Pavel!
As a follow up to
http://lists.gnu.org/archive/html/bug-lilypond/2011-11/msg00549.html
please find enclosed a file listing all @ruser{} that should be
corrected as long as the Notation Reference has not been translated.
It is the result of
git grep -n '@ruser'
launched in Documentation/cs/
I let you do the job and commit. Each second line contains what should
appear in place of @ruser{Czech words}. Don't forget I haven't learned
Czech…
As a matter of fact, each cross-reference to a manual that has not been
translated should use its named version if you want its translation to
appear.
Cheers,
Jean-Charles
Result of command launched from Documentation/cs/
git grep -n '@ruser' ../../../cs-xrefs.log
DUPLICATED FILE (STILL IN WORKING STAGE) SHOULD BE REMOVED ***
download.itexi:18:prosÃm, o naÅ¡Ã @ref{Text-Eingabe}.}
download.itexi:49:@ref{Unix, @sourceimage{logo-linux,,,}
download.itexi:51:@ref{Unix, Unix (Linux und FreeBSD)}
download.itexi:54:@ref{MacOS X, @sourceimage{logo-macosx,,,}}
download.itexi:55:@ref{MacOS X, MacOS X}
download.itexi:58:@ref{Windows, @sourceimage{logo-windows,,,}}
download.itexi:59:@ref{Windows, Microsoft Windows}
download.itexi:71:@ref{Zdroje}:
download.itexi:75:@ref{Stará staženÃ}:
download.itexi:78:@item @ref{Vývoj}:
download.itexi:90:@ref{GPL, GNU General Public License}.
download.itexi:564:PÅÃkazy se nacházejà v @rcontribnamed{Compiling
LilyPond,Sestavenà LilyPondu}.
download.itexi:595:naleznete v @ref{Svoboda}.
*
learning/common-notation.itely:82:@ruser{PÅezkouÅ¡enà taktů a poÄtu taktů}.
@rusernamed{Bar and bar number checks,PÅezkouÅ¡enà taktů a poÄtu taktů}
learning/common-notation.itely:117:PodÃvejte se na @ruser{OznaÄenà not v
jiných jazycÃch}.
@rusernamed{Note names in other languages,OznaÄenà not v jiných jazycÃch}
learning/common-notation.itely:211:@ruser{Automatické pÅedznamenánÃ} na
nÄkolik pÅÃkladů, jak mohou být
@rusernamed{Automatic accidentals,Automatické pÅedznamenánÃ}
learning/common-notation.itely:217:@ruser{OznaÄenà not v jiných jazycÃch},
@rusernamed{Note names in other languages,OznaÄenà not v jiných jazycÃch}
learning/common-notation.itely:218:@ruser{PÅedznamenánÃ},
@rusernamed{Accidentals,PÅedznamenánÃ}
learning/common-notation.itely:219:@ruser{Automatické pÅedznamenánÃ},
@rusernamed{Automatic accidentals,Automatické pÅedznamenánÃ}
learning/common-notation.itely:220:@ruser{OznaÄenà tóniny}.
@rusernamed{Key signature,OznaÄenà tóniny}
learning/common-notation.itely:297:@ruser{Ligatury},
@rusernamed{Ties,Ligatury}
learning/common-notation.itely:298:@ruser{Legatové oblouÄky},
@rusernamed{Slurs,Legatové oblouÄky}
learning/common-notation.itely:299:@ruser{OblouÄky frázovánÃ}.
@rusernamed{Phrasing slurs,OblouÄky frázovánÃ}
learning/common-notation.itely:396:@ruser{ArtikulaÄnà znaménka a ozdoby},
@rusernamed{Articulations and ornamentations,ArtikulaÄnà znaménka a ozdoby}
learning/common-notation.itely:397:@ruser{PÅÃkazy pro prstoklad},
@rusernamed{Fingering instructions,PÅÃkazy pro prstoklad}
learning/common-notation.itely:398:@ruser{Dynamika}.
@rusernamed{Dynamics,Dynamika}
learning/common-notation.itely:433:@ruser{Zadánà textu}.
@rusernamed{Writing text,Zadánà textu}
learning/common-notation.itely:485:@ruser{Automatické trámce},
@rusernamed{Automatic beams,Automatické trámce}
learning/common-notation.itely:486:@ruser{RuÄnà trámce}.
@rusernamed{Manual beams,RuÄnà trámce}
learning/common-notation.itely:563:@ruser{Ozdoby},
@rusernamed{Grace notes,Ozdoby}
learning/common-notation.itely:564:@ruser{Jiná rytmická rozdÄlenÃ},
@rusernamed{Tuplets,Jiná rytmická rozdÄlenÃ}
learning/common-notation.itely:565:@ruser{PÅedtaktÃ}.
@rusernamed{Upbeats,PÅedtaktÃ}
learning/common-notation.itely:858:@ruser{Klávesové nástroje a jiné
nástroje s vÃce notovými osnovami},
@rusernamed{Keyboard and other multi-staff instruments,Klávesové nástroje
a jiné nástroje s vÃce notovými osnovami}
learning/common-notation.itely:859:@ruser{Nechat ukázat osnovy}.
@rusernamed{Displaying staves,Nechat ukázat osnovy}
learning/common-notation.itely:901:@ruser{Akordové noty}.
@rusernamed{Chorded notes,Akordové noty}
learning/common-notation.itely:931:@ruser{SouÄasnÄ se objevujÃcà noty}.
@rusernamed{Simultaneous notes,SouÄasnÄ se objevujÃcà noty}
learning/common-notation.itely:1219:@ruser{Notový zápis zpÄvu}.
@rusernamed{Vocal music,Notový zápis zpÄvu}
learning/common-notation.itely:1264:@ruser{Notový zápis zpÄvu}.
@rusernamed{Vocal music,Notový zápis zpÄvu}
learning/common-notation.itely:1413:v kapitole @ruser{VytvoÅenà názvu}.
@rusernamed{Creating titles headers and footers,VytvoÅenà názvu}
learning/common-notation.itely:1506:@ruser{Hudebnà notový zápis,,hudebnÃm
notovým zápisem}.
@rusernamed{Musical
Re: Issue 2038 in lilypond: Czech translation of learning never builds
Le 16/11/2011 20:00, Jean-Charles Malahieude disait :
This has been the first time I have ever read Czech text, and I noticed
some mistakes in the use of @refs. Those are mostly @rusername{Czech}
instead of @rusername{English,Czech}, but I would need one full day of
work to correct them (comparing with English and Spanish and French).
I mean for instance
@ruser{Notový klíč}
instead of
@rusernamed{Clef, Notový klíč}
since the Notation Manual has not been translated at all.
I'll have a look at it over the week end and ping Pavel.
Cheers,
Jean-Charles
ps: Thanks for having pushed.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2038 in lilypond: Czech translation of learning never builds
Le 15/11/2011 23:12, Graham Percival disait : On Tue, Nov 15, 2011 at 04:37:26PM -, Phil Holmes wrote: - Original Message - From: Jean-Charles Malahieude lily...@orange.fr I think I've found the cause: replacing all instances of Začátek in @nodes or @refs by Top did the trick for me, even if I get lots of bad links(external xrefs to NR which is not translated). Hmm. What do the other languages do for this? es/ is generally the most trustworthy. I've tried quickly and it didn't work for me, but I guess I've done the changes wrong. Any chance of a patch or an exact list of where to change? I think at this point we'd best check with the translators; they may have the experience to give a certain answer quickly. It seems that I'm not a trustworthy person. Graham, do you happen to have opened the diff? We had this linking problem some years ago, and I did notice it to Francisco when he had Arriba instead of Top. If you cannot take 1.5 minute of YOUR SO PRECIOUS TIME to compare with other languages as I did in order to be sure that THIS IS the problem... I'm seriously believe I'd better go back to being just an occasional Lilypond basic user. Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2038 in lilypond: Czech translation of learning never builds
Le 16/11/2011 19:17, Graham Percival disait :
On Wed, Nov 16, 2011 at 07:07:33PM +0100, Jean-Charles Malahieude
wrote:
Graham, do you happen to have opened the diff?
I glanced at it, but I assume that if it worked, Phil would have
pushed it by now. Or that he _will_ push it once there is a clear
set of instructions for pushing to staging.
I believe Phil is waiting to know how the Mary-go-round settles. Only
thing is that he has not told if he has noticed some sort of
improvement after applying the change.
I saw your comment that you got lots of bad links so I thought
something was wrong with the patch, but perhaps that's normal for
translations.
This has been the first time I have ever read Czech text, and I noticed
some mistakes in the use of @refs. Those are mostly @rusername{Czech}
instead of @rusername{English,Czech}, but I would need one full day of
work to correct them (comparing with English and Spanish and French)
since I'm unable to build with -j on my dual core (this now takes 50
minutes for a full doc build).
And I already have 7 commits awaiting to be pushed (I want to build from
scratch before).
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2038 in lilypond: Czech translation of learning never builds
Comment #2 on issue 2038 by address@hidden: Czech translation of learning never builds http://code.google.com/p/lilypond/issues/detail?id=2038 I think it must be a part of the input files that mean that no index is made, but I can't find it and I'm not an expert. Could someone else look at the CS learning docs to see why it doesn't make an index file? Strange! if you link from /out-www/offline-root/Documentation/web/manuals.cs.html I get to /out-www/offline-root/Documentation/music-glossary/zacatek.cs.html#za_010d_00e1tek or out-www/offline-root/Documentation/learning/za_00c4_008d_00c3_00a1tek.cs.html Let mefeed my dog, have another look at it, and I ping you back Cheer, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2038 in lilypond: Czech translation of learning never builds
Le 14/11/2011 19:27, Jean-Charles Malahieude disait : Comment #2 on issue 2038 by address@hidden: Czech translation of learning never builds http://code.google.com/p/lilypond/issues/detail?id=2038 I think it must be a part of the input files that mean that no index is made, but I can't find it and I'm not an expert. Could someone else look at the CS learning docs to see why it doesn't make an index file? Strange! if you link from /out-www/offline-root/Documentation/web/manuals.cs.html I get to /out-www/offline-root/Documentation/music-glossary/zacatek.cs.html#za_010d_00e1tek or out-www/offline-root/Documentation/learning/za_00c4_008d_00c3_00a1tek.cs.html I think I've found the cause: replacing all instances of Začátek in @nodes or @refs by Top did the trick for me, even if I get lots of bad links(external xrefs to NR which is not translated). HTH, Jean-Charles ps: Sorry, I got with no connection for about 1.5 hour ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR3.2.2: erroneous example?
Le 20/08/2011 00:03, Trevor Daniels disait :
Jean-Charles, you wrote Friday, August 19, 2011 3:02 PM
Since the only header fields that will be printed are piece and opus,
the example in Custom text formatting for title blocks should read
(line 802 of input.itely)
- subtitle = \markup { \italic (Excerpt) }
+ opus = \markup { \italic (Excerpt) }
May I change it myself, or?
Please do.
OK
When this section was changed quite a lot
of useful information was lost. I think
the following also needs to be reinserted
(properly formatted, of course) in Title
blocks explained:
Since I don't like very much having two consecutive
if sentences, I would favor:
-
If the book only has a single score, the @code{\header} block may be
placed inside or outside of the @code{\score} block.
The default behavior, when the @code{\header} has been defined inside
the @code{\score} block, is to print only the @code{piece} and @code{opus}
fields:
@lilypond[papersize=a5,quote,verbatim,noragged-right]
\score {
{ c'4 }
\header {
title = title % not printed
piece = piece
opus = opus
}
}
@end lilypond
@funindex print-all-headers
@noindent
You may change this behavior (and print all the headers when defining
@code{\header} inside @code{\score}) by using
@example
\paper@{
print-all-headers = ##t
@}
@end example
@warning{Remember when adding a @bs{}@code{header} block inside a
-
Cheer,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: NR3.2.2: erroneous example?
Le 20/08/2011 16:11, Trevor Daniels disait : I like it! Thanks for picking this up! Done as 6810d727b278d15825eecb2b497d1a966241d4eb Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
NR3.2.2: erroneous example?
Hello all!
Since the only header fields that will be printed are piece and opus,
the example in Custom text formatting for title blocks should read
(line 802 of input.itely)
- subtitle = \markup { \italic (Excerpt) }
+ opus = \markup { \italic (Excerpt) }
Unless it is sympathetic ink?
May I change it myself, or?
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1806 in lilypond: Wrong search for translated docs
Quoting Phil: Where there is no language specific search box (e.g. cs) I assume the root version is used. This was updated by Graham. Some of the other search boxes were updated (e.g. es) but most were not. This would be quite quick to fix manually, but it would seem worth adding the other change suggested in 1171 at the same time - use site:lilypond.org/doc/v2.14 as the restriction, rather than forcing +2.14 as part of the search term. I'm just unable to figure it out, but would it be possible to feed those .ihtml in the same way as the other pages with what is in VERSION during the build process? Wee wouldn't then have to care about it. I'll correct the French version this afternoon. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: make doc
Le 01/08/2011 05:11, Graham Percival disait : On Sun, Jul 31, 2011 at 06:29:33PM +0200, Jean-Charles Malahieude wrote: No such file: file.itexi Search path: .:./out-www:. Extremely normal; happens all the time. :( Sorry to have disturbed, I had not noticed this manner to label the path. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
make doc
Hi Phil, I don't know if this is in relation with your work on extract_texi_filenames.py and don't remember if it was spitted before. Many of the calls to this script, especially each time it will process an out-www/web.texi I get something weird with searchpath: No such file: file.itexi Search path: .:./out-www:. I'm in sync with 54b02666750062788185bd3f99e644d621e348c2 and about to push some xref-fixes on the French version. If interested, the 10 Mo of logs are available. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Lilynet down?
Hi all! Is there any problem with www.lilynet.net ? I'm landing at Test Page for the Apache HTTP Server on Fedora telling me: This page is used to test the proper operation of the Apache HTTP server after it has been installed. If you can read this page, it means that the web server installed at this site is working properly, but has not yet been configured. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Partcombine: full bar rests
Le 16/07/2011 03:42, Colin Campbell disait : On 11-07-14 12:14 PM, Jean-Charles Malahieude wrote: Hi all! Using the part combiner, I would prefer not to have to split a multimeasure rest or use tags in order to get what is on the second line. There were several new additions to the basic \partcombine command introduced fairly recently, JeanCharles. Here is a link to the online documents for Automatic Part Combining. I believe that you may find what you need there. Unfortunately not, unless I don't understand it. The structure I have is: 2 oboes, 2 violins, 1 viola, 1 continuo and a SATB choir with soloists. Full score: Oboe and violin 1 play most of the time alternatively and share the same staff. Same goes for oboe and violin 2. Vocal score: Reduction for Violins (combined on the same staff) and continuo (without figures). I there have to use tags in order to switch notes when the second gets higher than the first, and then better manage stems and beaming. And I use two other tags for managing line breaks in full score or parts. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Partcombine: full bar rests
Hi all!
Using the part combiner, I would prefer not to have to split a
multimeasure rest or use tags in order to get what is on the second line.
---
\version 2.14.1
\partcombine
\relative c' { R1 c R1*2 r4 c r2 \break R1 c R1 R1 r4 c r2 }
\relative c' { R1*3 e1 R1 R1*3 e1 r4 r2. }
---
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [translations] Doc: @snippets links are broken when translated
Le 28/06/2011 19:05, Valentin Villenave disait :
Greetings everybody,
some translated doc pages have broken @snippet links; for example if
you follow the link at the bottom of
http://lilypond.org/doc/v2.15/Documentation/notation/expressive-marks-as-curves.de.html
you'll see that it points to
http://lilypond.org/doc/v2.15/Documentation/snippets/ausdrucksbezeichnungen
which doesn't exist (node names are not supposed to be translated in URLs).
However, this isn't the case in other sections: for example at the bottom of
http://lilypond.org/doc/v2.15/Documentation/notation/piano.fr.html
It points to the right address:
http://lilypond.org/doc/v2.15/Documentation/snippets/keyboards
Just because I use
@rlsrnamed{Keyboards, Claviers}
to have it labeled in French even if the target wont be translated.
I often adopt the same behaviour with @rglosnamed instead of @rglos.
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Partcombine: beaming
Hello all,
While combining parts for a piano reduction (choral score), it appears
that each time the first combine voice is lower than the other, beams
are not combined :
\version 2.14.1
VlnI = \relative c'' {
a4. g8 f[ g a f]
}
VlnII = \relative c' {
f4. g8 a[ g f a]
}
\score {
\new Staff
\set Staff.printPartCombineTexts = ##f
\partcombine
\VlnI
\VlnII
\layout { }
}
attachment: partcombine-beams.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Extracting parts: why does Devnull take as much space as a normal staff ?
Hi all,
In the book I'm engraving, it happens that some instruments get tacet
for certain pieces. In order to generate a full table of contents for
the parts, I treat them through Devnull. The problem is that this
Devnull context takes as much vertical space as a normal staff of
whatever kind I use (by the qay, a rhythmic staff is spread over the
same extent as a 5 lines staff - min-dist = 8.00).
Using annotate-spacing = ##t, Lily spits a
space: NaN/inf
min-dist: NaN/inf
padding: NaN/inf
bottom-of-extent: NaN/inf
extent-estimate: NaN/inf
---8---
\version 2.14.0
#(set-global-staff-size 20)
\paper { annotate-spacing = ##t
ragged-bottom = ##t
ragged-last-bottom = ##t }
\score { b'1}
\score {
%{ \new RhythmicStaff \with {
% \override StaffSymbol #'stencil = ##f
fontSize = #-3
\override StaffSymbol #'staff-space = #(magstep -3)
\override StaffSymbol #'thickness = #(magstep -3) %}
\new Devnull { s1 }
\header { piece = Piece two opus = TACET. }
\layout { %#(layout-set-staff-size 1)
%{\context {
\RhythmicStaff
\remove Time_signature_engraver
\remove Stem_engraver
\remove Beam_engraver
\remove Bar_engraver
\override VerticalAxisGroup
#'default-staff-staff-spacing = #'((basic-distance . 0.01)
(minimum-distance . 0.01)
(padding . -24)
(stretchability . 0))
}
\context {
\Score
\remove Bar_number_engraver
\override VerticalAxisGroup
#'default-staff-staff-spacing = #'((basic-distance . 0.01)
(minimum-distance . 0.01)
(padding . -24)
(stretchability . 0))
\override VerticalAxisGroup #'Y-extent = #'(-0.1 . 0)
%}
}
}
\score { b'1}
---8---
After three full days digging in that; I'm really fed up and upset, and
rely upon you.
The tracks I was following:
- have a piece and opus headers and a Devnull which normally should take
no vertical space - wrong guess;
- have a piece and opus headers and a transparent staff I would
translate up : impossible to change markup-score-spacing neither
score-markup-spacing within a book(part);
- generate a transparent staff of ONE POINT HEIGHT: no way, it still
takes the same vertical space as a regular one.
- create TACETpiece and TACETopus that would mimic the piece and opus
headers whatever the customized layout I use for them: the only point of
entry I git grep are in Documentation/*
Thanks and sorry if for the disturbance,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Timing.baseMoment behaviour
Le 27/02/2011 19:23, Phil Holmes disait :
Jean-Charles Malahieude wrote:
Hi,
While translating the commit Doc -- Clarify instructions on autobeam
settings I wanted to understand what was illustrated, but
texidoc = { Timing.baseMoment does not always work }
\score {
\new Staff {
\time 2/4
\set Timing.baseMoment = #(ly:make-moment 1 16)
\set Timing.beatStructure = #'(3 3 2)
a'16^works \repeat unfold 7 { a'16 }
}
}
\score {
\new Staff {
\time 6/8
\set Timing.baseMoment = #(ly:make-moment 1 16)
\set Timing.beatStructure = #'(3 3 2 3 1)
a'16^works \repeat unfold 11 { a'16 }
}
}
\score {
\new Staff {
\time 3/4
\set Timing.baseMoment = #(ly:make-moment 1 16)
\set Timing.beatStructure = #'(3 3 2 3 1)
a'16^does not work \repeat unfold 11 { a'16 }
}
}
===
Cheers,
Jean-Charles
You also need to clear beamExceptions:
\score {
\new Staff {
\time 3/4
\set Timing.baseMoment = #(ly:make-moment 1 16)
\set Timing.beatStructure = #'(3 3 2 3 1)
\set Timing.beamExceptions = #'()
a'16^works \repeat unfold 11 { a'16 }
}
}
I find it strange that this clearing is mandatory only with 3/4, and had
preferred the snippet to contain it, since whatever you try to
understand and explain this known issue it wont work. Nevertheless,
I'll add it to the French version.
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Timing.baseMoment behaviour
Hi,
While translating the commit Doc -- Clarify instructions on autobeam
settings I wanted to understand what was illustrated, but
texidoc = { Timing.baseMoment does not always work }
\score {
\new Staff {
\time 2/4
\set Timing.baseMoment = #(ly:make-moment 1 16)
\set Timing.beatStructure = #'(3 3 2)
a'16^works \repeat unfold 7 { a'16 }
}
}
\score {
\new Staff {
\time 6/8
\set Timing.baseMoment = #(ly:make-moment 1 16)
\set Timing.beatStructure = #'(3 3 2 3 1)
a'16^works \repeat unfold 11 { a'16 }
}
}
\score {
\new Staff {
\time 3/4
\set Timing.baseMoment = #(ly:make-moment 1 16)
\set Timing.beatStructure = #'(3 3 2 3 1)
a'16^does not work \repeat unfold 11 { a'16 }
}
}
===
Cheers,
Jean-Charles
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: make translation-status fails
Le 16/02/2011 13:19, Francisco Vila disait : 2011/2/16 Francisco Vilapaconet@gmail.com: Fixed in git, I hope. Still testing the build. OK succeeds here as well. Thanks for the chase! BTW does LANG=whatever date -u work for you? for whatever = fr, de etc? [jcharles@localhost ~]$ LANG=zh date -u Wed Feb 16 18:47:21 UTC 2011 [jcharles@localhost ~]$ LANG=cs date -u Wed Feb 16 18:47:26 UTC 2011 [jcharles@localhost ~]$ LANG=es date -u Wed Feb 16 18:47:31 UTC 2011 [jcharles@localhost ~]$ Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: make translation-status fails
Le 16/02/2011 13:19, Francisco Vila disait : 2011/2/16 Francisco Vilapaconet@gmail.com: BTW does LANG=whatever date -u work for you? for whatever = fr, de etc? [jcharles@localhost ~]$ LANG=de_DE.utf8 date -u Mi 16. Feb 18:52:37 UTC 2011 [jcharles@localhost ~]$ LANG=de date -u Wed Feb 16 18:53:21 UTC 2011 [jcharles@localhost ~]$ LANG=de_DE.utf8 date -u Mi 16. Feb 18:53:24 UTC 2011 [jcharles@localhost ~]$ LANG=es_ES.utf8 date -u mié feb 16 18:53:39 UTC 2011 [jcharles@localhost ~]$ date -u mer. févr. 16 18:54:02 UTC 2011 [jcharles@localhost ~]$ LANG=fr date -u Wed Feb 16 18:54:14 UTC 2011 [jcharles@localhost ~]$ LANG=fr_FR.utf8 date -u mer. févr. 16 18:54:25 UTC 2011 [jcharles@localhost ~]$ Found after having env | grep LANG HTH, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
make translation-status fails
Hello everybody, Wishing to update the translations status before 2.14 jumps out, since its last update was in November 2010, I get this error, which I'm unable to deal with: make translation-status PYTHONPATH=/home/jcharles/GIT/Traduc/python:/home/jcharles/GIT/Traduc/python/auxiliar /usr/bin/python /home/jcharles/GIT/Traduc/scripts/auxiliar/translations-status.py translations-status.py Reading documents... Generating status pages... translations-status.py:717: warning: using markup = TexiMarkup (): ugly HTML output, questionable PDF and info output. Consider using HTML-only markup = HTMLMarkup () Traceback (most recent call last): File /home/jcharles/GIT/Traduc/scripts/auxiliar/translations-status.py, line 727, in module updated = markup.paragraph (markup.emph (translation[l] (last_updated_string) % date_time)) TypeError: not all arguments converted during string formatting make: *** [translation-status] Erreur 1 Compilation exited abnormally with code 2 at Sat Feb 12 16:35:09 I've primarily updated all fatal objects and put the @c Translators when missing. Cheers, Jean-Charles ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
