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 >'

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

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 Modu

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://li

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 D

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 correc

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 _

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/rh

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

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 T

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-li

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 : \sourcefilelin

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 merg

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 rig

Re: Download links missing at http://lilypond.org/index.de.html

rom ae0ced1be1617970e9ff8748ae018399e3ab1f46 Mon Sep 17 00:00:00 2001 From: Jean-Charles Malahieude 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 --gi

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 poin

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/ex

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

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

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, Je

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

Re: lyrics extender and acciaccatura

Le 11/11/2014 17:22, David Kastrup a écrit : David Nalesnik writes: On Tue, Nov 11, 2014 at 9:53 AM, David Nalesnik 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 tha

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

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

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'

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 e

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

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 h

Re: 3648 – revolution revisited

Le 08/07/2014 08:11, David Kastrup disait : Simon Albrecht writes: I currently try out the consequences of issue 3648 , namely the possibility to use isolated durations as frequently as has been normal for isolated pitches. It certainly

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

Re: lilypond-invoke-editor requires emacs?

Le 20/10/2013 19:50, Federico Bruni disait : 2013/10/20 Jean-Charles Malahieude 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 .bashr

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-edit

Re: quoteDuring: no midi nor repeats

Le 25/08/2013 08:34, Keith OHara disait : Jean-Charles Malahieude 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" { \unfoldRepea

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.2

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 {

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

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 d

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/

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

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/

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 anyon

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

Re: Footnote oddity

Le 18/05/2013 18:29, David Kastrup disait : Jean-Charles Malahieude 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

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 <>\version "2.17.16" #(set-default-paper-size "a6")

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. <>\version "2.17.16" #(set-default-paper-size "a6") FootA = \markuplist { \justified-lines { % \supe

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

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/Men

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 migh

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 @ig

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

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 e

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,

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 \ve

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 giv

[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

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

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 ke

Re: issues 2266 and 1721

Le 15/04/2012 14:56, Phil Holmes disait : - Original Message - From: "Jean-Charles Malahieude" To: "Phil Holmes" Cc: "Lily Bugs" ; "lilypond-devel" Sent: Saturday, April 14, 2012 5:46 PM Subject: Re: issues 2266 and 1721 It might have someth

Re: issues 2266 and 1721

Le 13/04/2012 19:54, Phil Holmes disait : - Original Message - From: "Jean-Charles Malahieude" To: "Lily Bugs" ; "lilypond-devel" Sent: Saturday, March 31, 2012 6:47 PM Subject: Re: issues 2266 and 1721 Hi all, I just noticed something: 1- I

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}.

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

Re: Issue 2391 in lilypond: Add Appendix entry for Predefined Paper Sizes

Hi all! 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). Cheers, Jean-Charles __

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

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 snippet

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 u

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

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

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

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

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

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 belon

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" o

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/u

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 t

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 pas

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

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" b

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 b

[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 Docume

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 co

Re: Issue 2038 in lilypond: Czech translation of learning never builds

Le 16/11/2011 20:12, Phil Holmes disait : - Original Message - From: "Jean-Charles Malahieude" And I already have 7 commits awaiting to be pushed (I want to build from scratch before). Following Julien's work on http://code.google.com/p/lilypond/issues/detail?id=1852, yo

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

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" I think I've found the cause: replacing all instances of "Začátek" in @nodes or @refs by "T

Re: Issue 2038 in lilypond: Czech translation of learning never builds

Le 15/11/2011 17:37, Phil Holmes disait : - Original Message - From: "Jean-Charles Malahieude" 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 link

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

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

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/bu

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 { \ita

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?

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 ch

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

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 instal

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

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

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

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 htt

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 {

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

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.baseMo

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)

  1   2   >