Re: MusicXML test suite: Bug in 41f-StaffGroups-Overlapping.xml

On 26/10/14 16:50, Andreas Wenger wrote: > The test description is wrong: "In this case, one group (with a square > bracket) goes from staff 2 to 4) and another group (with a curly bracket) > goes from staff 3 to 5." > It should be "one group ... goes from staff 1 to 4", since group 1 starts > alre

Re: More bugs on first page of German lilypond website

On 29/10/14 18:13, Markus Olbrich wrote: > Hi! > > Today, I observed that the sentence has been corrected. Thank you very > much. I think it is important to give a good first impression on the > website. > > However, I recognized that there are some more mistakes: > > In the header: > Incorrect

Re: suprising touch of rest with accidentals

On 02/11/14 08:44, Trevor Daniels wrote: > > Werner LEMBERG wrote Sunday, November 02, 2014 7:03 AM > >> [release/2.19.15-1-13-gdd5a6e7] >> >> with this input >> >> \relative c' { >>8[ r ] >> } >> >> I would expect that there is at least a tiny distance between the rest >> and the sharp, b

Re: LSR : Dashed slurs indicating optional slurs between lyric lines

___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: multiple issues with MIDI channel assignment

Hello, On 22/11/14 05:08, Sean Barrettt wrote: >> I'm not top-posting. > > Because these issues relate to overflowing the 16 MIDI channels, > the minimal example would still be 18+ lines. As I've found these > issues in my first 5 minutes of using lilypond, it doesn't make > sense to spend my ti

Re: Elaine Gould: "Behind bars" after three years not yet in litterature list

On 27/11/14 19:11, Villum Sejersen wrote: > Hello lilyponders > > As an appendix to the Essay there is a shorter litterature list... > > Isn't it high time that Elaine Gould: "Behind Bars" (2011) is added to > that? It already is referenced somewhere in the NR. > > I recently invested in this vo

Re: Fwd: 3 new lilypond issues

Jan, On 06/12/14 06:59, Urs Liska wrote: > forwarding ... > > > Ursprüngliche Nachricht > Von: Jan Hakenberg > Gesendet: 6. Dezember 2014 07:35:15 MEZ > An: James > CC: Urs Liska > Betreff: 3 new lilypond issues > > Hi, > > I briefly searched the "open issues", but did no

Re: footnotes should work on markup attached to a note

On 07/12/14 03:59, Eugene Cormier wrote: > Hey guys, > > this works: > { \markup { "rit" \footnote "*" "* text" } > > this does not: > { c4_\markup { "rit" \footnote "*" "* text" } } > > should it? I think so... > > (tested on lilypond v2.18) > > I think this is https://code.google.com/p/li

Re: Update guile version dependency info in docs from "1.8.2 or newer" to "1.8.2"

On 17/12/14 19:23, Paul Morris wrote: > In the docs, update dependency info from guile “(1.8.2 or newer)” to just > “(1.8.2)” until guile 2.0 support is stable. As reported on the user list > here: > > http://lilypond.1069038.n5.nabble.com/Kubuntu-GCC-compile-with-guile-2-td169498.html > >

Re: LM 2.1.3 - bare durations

Federico, On 25/12/14 10:10, Federico Bruni wrote: > LM 2.1.3 > I don't understand well the second sentence in this paragraph (in master > only at the moment): > > "This shorthand may be useful in other places where the rhythm changes > with an unchanging pitch, but remember a bare duration will

Re: LSR printing-a-repeat-sign-at-the-beginning-of-a-piece.ly

On 29/12/14 21:56, Federico Bruni wrote: > Il giorno sab 27 dic 2014 alle 16:04, Thomas Morley > ha scritto: >> Why not delete it? >> We have something smiliar in the NR >> http://www.lilypond.org/doc/v2.19/Documentation/notation/long-repeats >> > > I'm in favor of deleting it. > Pierre asked the

Re: [PATCH] Reduce size of *TeX generated pdfs, Version 2

On 08/01/15 19:10, Knut Petersen wrote: > On 08.01.2015 19:10, James wrote: >> On 08/01/15 12:18, Knut Petersen wrote: >>> So here is Version 2 >>> >>> >>> I fixed a few issues with version 1, added a command line option >>> --bigpdf / -b, and documented that option in the german a

Re: allow changes of scripts by type

On 28/01/15 18:12, David Nalesnik wrote: Hi, It is a common request to be able to change the defaults of specific scripts globally. An example would be changing the padding and font-size of "tenuto" throughout a file. Currently, the user needs to tweak each instance of the right Script, a pr

Re: Apologies for Issues 4279 and 4280

Ralph, On 06/02/15 14:04, Ralph Palmer wrote: Greetings - I didn't realize that Google was using my private email address, so Issue 4279 was not submitted correctly (no issue label), and 4280 was a complete mistake. I do not know how to delete an issue, so please, someone either delete or recy

Re: systems-per-page and blank-page-penalty

On 09/02/15 10:19, Werner LEMBERG wrote: > consider the following snippet. > > #(set-default-paper-size "a6") > > \paper { systems-per-page = 6 blank-page-penalty = 1000 > > #(define page-breaking ly:page-turn-breaking) > > copyright = "" footer = "" tagline = "" } > > m = \relative c' { f'8 f

Re: systems-per-page and blank-page-penalty

On 09/02/15 22:40, Werner LEMBERG wrote: Maybe I'm being a bit hasty but https://code.google.com/p/lilypond/issues/detail?id=4285 Thanks. It perhaps makes sense to add the PDF file also... Werner Done. ___ bug-lilypond mailing list bug

Re: [LSR] remove snippet 142

On 17/02/15 20:32, Federico Bruni wrote: > Hi all > > This snippet sounds out-of-date: > http://lsr.di.unimi.it/LSR/Item?id=142 > > As hammer-on and pull-off in tablature are documented: > https://code.google.com/p/lilypond/issues/detail?id=2594 > http://lilypond.org/doc/v2.19/Documentation/notat

Re: DynamicLineSpanner.outside-staff-priority = ##f fails since 2.19.14

On 06/03/15 21:25, Simon Albrecht wrote: > Hello, > > after Phil and Thomas could do some more to enlighten the problem I had, > and confirmed that it seems to be a regression, I now direct this again > to the bug-list. Thomas made a minimal example (see at the bottom, with > output attached). >

Re: New Production with LilyPond

On 06/03/15 15:57, Phil Holmes wrote: > "Aurélien Bello" wrote in message > news:0ada497a-fbaf-4a88-925a-f32d39d73...@aurelienbello.com... >> Dear all, >> I would like to inform about an exciting project I made with LilyPond. >> Every year, the Berlin Philharmonic Orchestra has its own Eastern >>

Re: partcombine: incorrect glissando attachment

On 14/03/15 04:34, Dan Eble wrote: > \version "2.19.16" > > \score { > \partcombine > \relative { e'' e e c' } > \relative { b'~ b \glissando e, g } > } > > > ___ > bug-lilypond mailing list > bug-lilypond@gnu.org > https://lists.gnu.org/mail

Re: website: two minor errors in productions page

On 14/03/15 09:43, Federico Bruni wrote: > Hello > > From: > http://lilypond.org/productions.html > > Joe Smeets created sheet music for the children’s book Zing Mee (Sing > along) by Annie M.G. published by Querido – ISBN 9789045106205: > www.queridokinderenjeugdboeken.nl; choir rehearsal scores

Re: NR 2.1.1: Lyric Tie and other languages

On 06/05/15 00:01, Simon Albrecht wrote: > Hello, > > > has an example covering the use of LyricTie with Italian text. Using the > same feature with German text (and probably other

Re: English note names generate errors

On 11/05/15 16:15, David Kastrup wrote: >> error: unrecognized string, not in text script or \lyricmode > That's because the long note names have been changed. If you had used > convert-ly for converting the syntax, you'd hopefully not have seen a > problem ("hopefully" since the conversion rule c

Re: musicxml2ly tremolo tag on notes shorter than quarter

On 07/05/15 23:21, pls wrote: > Hi Jörn, > > On 03.05.2015, at 00:23, Jörn Eichler wrote: > >>> I'm not top posting. >> >> For music XML input "2" on an eighth note >> of C, musicxml2ly creates "c8 :16" which, I think, is incorrect, because the >> 2 tremolo marks make it a 32th tremolo. > > tha

Re: Possible bug: using articulate.ly, acciaccatura, and \barNumberCheck

On 06/05/15 18:54, Knute Snortum wrote: > I have a possible bug here. This may be another "Yeah, we know there are > problems with acciaccatura." > > When using articulate.ly and \barNumberCheck, you can get into a pickle > where the bar check never reports correctly. In my sample, the bar numbe

Re: PostScript circle printed with unwanted line

On 06/05/15 16:04, ArnoldTheresius wrote: > James Lowe wrote >> ... >> Or add a note in the documentation in the appropriate place? >> >> James >> >> ___ >> bug-lilypond mailing list > >> bug-lily

Re: \partcombine causes wrong tuplet bracket when tuplet begins with rest

On 15/05/15 22:38, H. S. Teoh wrote: > % The triplet in the first argument to \partcombine is wrongly > % formatted in the output; the tuplet bracket only spans the two quarter > % rests, whereas it should span both rests and the single note. > % > % - Note: this is not the same as issue 913; paddi

Re: Hairpins ending on key changes

On 20/05/15 06:28, Connor Harris wrote: > In Lilypond 2.18.2 and possibly later versions, hairpins that end at the > beginning a measure are engraved with their right ends slightly left of > the barline. This looks bad if the note follows a key change, as there may > be considerable space (depen

Re: engraving ends too early

On 25/05/15 08:58, David Kastrup wrote: > Dan Eble writes: > >> % 2.19.20 does not engrave the lyrics and stops engraving the vocal >> % staff before the end. (Compare to 2.18.2.) I haven’t tested MIDI. >> >> \version "2.18.0" >> \include "english.ly" >> >> vocal = \relative c'' { R1 | f2 c } >

Re: [feature request]: set grace note duration for MIDI playback

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/06/15 21:21, Gilberto Agostinho wrote: > Currently, the MIDI output from LilyPond uses a hard coded value to > calculate the duration for the grace notes (1/4 of their duration > according to the documentation or 9/40 according to David Kastrup).

Re: [feature request]: set grace note duration for MIDI playback

On 12/06/15 11:11, Gilberto wrote: > Hi James, > > Thanks for the suggestion, but I believe you are talking about > something different than I meant. This property in articulate.ly > simply changes the proportion of which note should have its value > stolen by the grace notes. In old music, for in

Re: lyluatex [Fwd: Re: Lilypond and LaTeX - margins]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, On 26/07/15 09:28, Federico Bruni wrote: > Should this be added somewhere in the docs? In the easier editing > page of the website there's no section for this. I think that this > chapter of Usage would be better: > http://lilypond.org/doc/v2.

Re: lyluatex [Fwd: Re: Lilypond and LaTeX - margins]

On 26/07/15 10:52, James Lowe wrote: > Hello, > > On 26/07/15 09:28, Federico Bruni wrote: >> Should this be added somewhere in the docs? In the easier >> editing page of the website there's no section for this. I think >> that this chapter of Usage would be bet

Re: Documentation missing for extra \header fields available for customizing PDF metadata

Sorry I forgot to reply all and include the 'bug list'. Hello Heikki, On 08/08/15 09:53, Heikki Tauriainen wrote: > Hi, > > While examining the source code on how \header blocks are used to > extract information for PDF metadata (to implement the enhancement > #4539), I discovered that LilyPo

Re: *.eps and *.svg .gitignore patterns match files in repo

Hello 'bug' and Mark, On 21/08/15 08:56, markdblackwell wrote: >> Any chance to see an uncensored version of this on the actual >> mailing list? Not everybody uses Nabble, and you can see what got >> actually sent out on the list by looking at >> http://lists.gnu.org/archive/html/bug-lilypond/201

Re: Clear fret-diagram- and harp-pedal-input-strings from whitespace

On 23/08/15 15:11, Thomas Morley wrote: > 2015-08-23 16:05 GMT+02:00 Thomas Morley > : >> As suggested by David >> http://lilypond.1069038.n5.nabble.com/Patch-issue-procedures-was-Randomness-in-layout-td179920.html >> >> I'll upload the patch to Rietveld and post the link here. > > Here we go: >

PATCHES: Countdown for August 26th 2015 - IMPORTANT UPDATE TO PATCH REVIEW PROCESS - PLEASE READ

Hello, ***Important do please read*** Google Tracker will be 'read-only' on the 25th August. At the moment, as I understand it we are still 'transitioning' to a new tracker system for issues but Rietveld is still working as normal. This will make keeping track of patches a bit more involved for

Re: *.eps and *.svg .gitignore patterns match files in repo

Hello, On 25/08/15 18:48, markdblackwell wrote: > Per > https://www.kernel.org/pub/software/scm/git/docs/gitignore.html > > "A gitignore file specifies intentionally untracked files that Git > should ignore. Files already tracked by Git are not affected" > > A

Re: New issue submission process?

On 27/08/15 19:48, Simon Albrecht wrote: > Am 27.08.2015 um 20:27 schrieb Ralph Palmer: >> Greetings - >> >> Is there a new "official" submission process and / or location >> (web site)? > Not yet. >> >> If so, could someone please let me (us?) know? >> >> If a new site is on the horizon, but no

Re: Allura at SF is ready

Trevor, On 30/08/15 16:57, Trevor Daniels wrote: > > James wrote Sunday, August 30, 2015 4:22 PM > >> I've 'synced' my list of Patches I've been keeping track of >> manually with the issues list now. >> >> Is this set of issues going to be the one we migrate to the 'new' >> non-SF system? >> >

Re: 2.19.26 regtests

On 31/08/15 15:35, Phil Holmes wrote: > I've forwarded this to the bug list so someone should create a tracker. > > Please note the bug list is now at > http://sourceforge.net/p/testlilyissues/issues/ I created https://sourceforge.net/p/testlilyissues/issues/4585/ You cannot yet use git-cl to u

Re: [ISSUE]: Doc string fix in wake of issue 4426

On 04/09/15 21:10, David Kastrup wrote: > > Type: Documentation > Patch: New > Owner: d...@gnu.org > Status: Started > Rietveld issue: 262310043 (https://codereview.appspot.com/262310043) > Issue description: > Doc string fix in wake of issue 4426 > > This is now https://sourceforge.net/p/tes

Re: feature request: turn partcombine to partCombine (camelCase)

Malte, On 13/08/15 21:42, Malte Meyn wrote: > Hi list, > > the case of the ‘c’ in partcombine is inconsistent, confusing me every > time I use \partcombine(Apart|Chords|…): > > \partcombine, \partcombineApart, … but > \partCombineTextsOnNote, \partCombineListener > > I would suggest to change a

Re: verkeert is wrong

On 22/09/15 07:47, Martin Tarenskeen wrote: > > Where do I report translation errors? translati...@lily.net is probably the best place. Simple documentation edits can be made by some of the native speaking developers - in which case I'd suggest an 'issue tracker', but when it comes to these 'po'

Re: verkeert is wrong

On 22/09/15 10:24, Federico Bruni wrote: > It's the program po file which is handled by the Translation Project. > Only the person in charge for the dutch language can send updates to the > TP robot, see: > http://translationproject.org/domain/lilypond.html I notice that we're missing Hungarian in

Re: LM Orchestral template

On 22/09/15 20:51, Simon Albrecht wrote: > On 22.09.2015 21:42, Trevor Daniels wrote: >> Simon Albrecht wrote Tuesday, September 22, 2015 7:35 PM >> >>> I just came across the Orchestral template in LM A.6.I, and noticed two >>> flaws, one minor and one serious: >>> – Double basses usually aren’t n

Re: [Issue 4131] Patch new

On 26/09/15 08:56, David Kastrup wrote: > Issue 4131 [Reimplement forced partcombine decisions via context properties] > Patch: new > Rietveld issue: 144600043 (https://codereview.appspot.com/144600043) > Comment: > Reimplement after issue 4609 makes this possible > Updated. Thanks. -- James -

Re: [ISSUE]: Don't dump Midi data to screen on write error

On 27/09/15 11:25, David Kastrup wrote: > Status: New > Owner: dakas > Type: Defect > Patch: new > Rietveld issue: 266150043 (https://codereview.appspot.com/266150043) > Summary: > Don't dump Midi data to screen on write error > Et voila! https://sourceforge.net/p/testlilyissues/issues/4623/ --

Re: svg-woff error (Unbound variable: paper in output-svg.scm:448)

On 24/10/15 02:30, Ophir Lifshitz wrote: > Hello, > > I'm using Lilypond 2.18.2 on Mac Yosemite. I am not able to use the > svg-woff option. See the MWE here: http://pastie.org/pastes/10503035/text > > Thanks, > Ophir Do you get the same thing using latest 2.19.x? http://lilypond.org/development.

Re: svg-woff error (Unbound variable: paper in output-svg.scm:448)

Eugene, On 24/10/15 12:45, Eugene Cormier wrote: > On Sat, Oct 24, 2015 at 11:29:04AM +0100, James Lowe wrote: >> On 24/10/15 02:30, Ophir Lifshitz wrote: >>> Hello, >>> >>> I'm using Lilypond 2.18.2 on Mac Yosemite. I am not able to use the &g

Re: [feature-request] optional duration for temporary

On 11/11/15 02:58, Kieren MacMillan wrote: > Hello all, > > Rather than having to \revert an \override (or set of \override-s), might it > be possible to set an optional duration for which the override would be in > effect? e.g. > > \temporary #’(10 1/8) \override LyricText.extra-offset = #’(0

Re: Big in repeat bar

Hello George, On 14/11/15 07:17, George Podkolzin wrote: > \version "2.18.2" > > \relative c' { > c e c e > \repeat volta 2 { \bar "[|:" c e g c } > \alternative { > % If I use \bar ":|]" instead of default repeat bar, there is no > space between volta brackets. > { c e, g2 \bar ":|

Re: SVG with leading/trailing spaces should use non-break spaces

Hello, On 20/11/15 21:15, Ophir Lifshitz wrote: > Hello, > > Has anyone been able to repro this bug? On latest unstable (2.19.31) this does not seem to happen (and I get your 'correct' example). James > > Thanks, > Ophir > > On Mon, Nov 2, 2015 at 7:27 PM, Ophir Lifshitz > wrote: > >> Hello al

Re: typo in NR 3.2.6, input.itely

On 28/11/15 21:13, Federico Bruni wrote: > Hi > > In this line of Documentation/notation/input.itely: > > \tocItem \markup { Cesare. Presti omai l'Egizzia terra } > > Egizzia should be changed to Egizia > > Can anybody just fix and push it? I'll make a patch (and an issue) and include it with you

Re: typo in NR 3.2.6, input.itely

Hello, On 29/11/15 13:04, James Lowe wrote: > On 28/11/15 21:13, Federico Bruni wrote: >> Hi >> >> In this line of Documentation/notation/input.itely: >> >> \tocItem \markup { Cesare. Presti omai l'Egizzia terra } >> >> Egizzia should be change

Re: SVG with leading/trailing spaces should use non-break spaces

Hello, On 21/11/15 08:41, Ophir Lifshitz wrote: > Hello, > > Weird, I just downloaded 2.19.31 and still see the bug (line 27). > > Ophir Yes you are right. I have created https://sourceforge.net/p/testlilyissues/issues/4678/ James ___ bug-lilypond

Re: Example in section "Printing stanzas at the end in multiple columns" doesn't align text baselines precisely

Hello Márton, On 01/11/15 23:38, MártonKároly wrote: > Notation Reference 2.1.3. example, slightly modified > > The 5th verse is printed slightly BELOW the 3rd! (the bottom of the > letter 'g' is below the bottom of the letter 'l' and distances are > measured from the bottom of the letters and

Re: Fontmap entry for Fontmap.local ends prematurely!

Hello Karl, On 30/11/15 00:43, Karl Berry wrote: > I installed lilypond from your lilypond-2.18.2-1.linux-x86.sh (from > http://www.lilypond.org/unix.html) on centos 6.7. Running lilypond -V --pdf > test.ly with the test.ly file from that same page ends with: > > Converting to `./newtest.pdf

Re: accidental changes beam slope in other staff

Malte, On 11/12/15 14:48, Malte Meyn wrote: > Hi list, > > I found a small but weird bug concerning beam slopes: In the following > code, every accidental sign (including quarter tones) except natural > and semisharp will change the direction of beam slope the other staff. > IMO the changed beam s

Re: Doc: CG 2.1 LilyDev minor corrections

Greg, On 21/12/15 18:15, Greg wrote: > I have made some minor corrections to the Contributors' Guide – 2.1 > LilyDev. A patch file is attached. > > This is my first patch so please let me know if there is anything else I > should do. > > Thanks, > Greg. > > > __

Re: Install confirmation test file misleading

Hello Paul, On 03/02/16 22:48, Paul Booker wrote: tisimst gmail.com> writes: Paul, The very first time compiling any .ly file should take longer because LP creates a font cache (note that this also applies whenever you change the contents of the system font directory). After that you should

Re: \markup \sans ... does not always give sans-serif output in svgs in 2.19.36

Hello, On 13/02/16 20:50, Paul Morris wrote: Looking closer at the SVG files produced... In 2.18 we have this: some text And when I manually edit the 2.19 svg file so it has font-family="sans-serif” then that fixes it and the text appears as sans-serif. Elsewhere in the svg files I s

Re: \markup \sans ... does not always give sans-serif output in svgs in 2.19.36

On 17/02/16 04:04, Paul Morris wrote: On Feb 16, 2016, at 4:17 PM, James Lowe <mailto:p...@gnu.org>> wrote: From usage: http://lilypond.org/doc/v2.19/Documentation/usage-big-page#advanced-command-line-options-for-lilypond *Note for backend svg output:*LilyPond’s default fonts (

Re: Manual Chapter 2.10.2 Arabic music

Hello, On 21/02/16 18:41, Blöchl Bernhard wrote: % Chapter 2.10.2 Arabic music % subchapter Selected Snippets % Non-traditional key signatures % http://www.lilypond.org/doc/v2.19/Documentation/snippets/world-music % The shown snippet unhappily does not fit to the Chapter headline: % 1st \include

Re: Request: Accepting isolated durations as ly:music?

Hello, On 19/02/16 03:11, Peter Crighton wrote: % As discussed on the User mailing list, isolated durations are currently not % accepted as expressions of type ly:music?, thus making it impossible to % create functions expecting either music or isolated durations with an % arbitrary number of po

Re: A bug in event-listener.ly

Fwding to bug list On 17/12/15 13:39, Richard Shann wrote: While developing a Playback View in Denemo (music plays back while LilyPond-typeset SVG is animated, building on Mathieu Demange's work) I came across a bug in event-listener.ly: In this procedure #(define (format-tempo engraver event)

Re: MusicXML regression test 42a-MultiVoice-TwoVoicesOnStaff-Lyrics.xml is missing the first note in voice 2

Hello Tobias, On 23/02/16 15:13, Tobias Kretschmar wrote: I'm not top posting. Hello Is it intended that MusicXML regression test 42a-MultiVoice-TwoVoicesOnStaff-Lyrics.xml is missing the first note in voice 2? Subsequently the lyrics of voice 2 is moved one note to the right. Regards, Tobias

Re: MusicXML regression test 42a-MultiVoice-TwoVoicesOnStaff-Lyrics.xml is missing the first note in voice 2

Hello Tobias, On 26/02/16 07:41, Tobias Kretschmar wrote: Hello James, 42a-MultiVoice-TwoVoicesOnStaff-Lyrics.xml is missing the first note in voice 2? Subsequently the lyrics of voice 2 is moved one note to the right. This might be a mistake in the xml file. Sorry if I could not make me cl

Re: MusicXML regression test 42a-MultiVoice-TwoVoicesOnStaff-Lyrics.xml is missing the first note in voice 2

Tobias, On 27/02/16 15:19, Tobias Kretschmar wrote: Hello Werner Please resend the patch using diff option `-u'. I have found a switch in WinDiff that sounds like -u option. Please find attached a new patch. Is it right? Tobias ___ bug-lilypond m

Re: MusicXML test suite: Bug in 24e-GraceNote-StaffChange.xml

Andreas On 03/03/16 17:53, Andreas Wenger wrote: In the Unofficial MusicXML test suite, 24e-GraceNote-StaffChange.xml is missing the element 2 after Otherwise, only a single staff is assumed. See http://www.musicxml.com/UserManuals/MusicXML/Content/EL-MusicXML-staves.htm _

Re: Broken link on GSOC page

Paul, On 03/03/16 04:16, Paul Morris wrote: On the LilyPond GSOC page: http://lilypond.org/google-summer-of-code.html Under "Improve default beam positioning” the link to "section 2.2 here” goes to: http://icking-music-archive.org/lists/sottisier/sottieng.pdf Which no longer exists, because as

Re: No staccato on chords in MIDI

Hello, On 06/03/16 01:00, Dan Eble wrote: On Feb 7, 2016, at 09:59 , Dan Eble wrote: On Feb 7, 2016, at 09:57 , Thomas Morley wrote: 2016-02-07 15:43 GMT+01:00 Dan Eble : % Lilypond does not apply staccato to chords in the MIDI output. % A shot of opening LP output in another program is a

Re: Grace notes and staff miss-alignment

Hello, On 08/03/16 00:38, Karol Majewski wrote: I think that tracker has to be created for this issue. Perhaps it should be marked as critical as one gets different output depending on platform. From the Contributor Guide: --snip-- Type-Critical: normally a regression against the

Re: Doc: Extending: "sole ‘real’ argument" should be simply "argument"

On 12/03/16 19:57, Mark D. Blackwell wrote: The Extending LilyPond manual, in section 1.3.4: http://www.lilypond.org/doc/v2.19/Documentation/extending/adding-articulation-to-notes-_0028example_0029 currently states: "Now we transform the add-accent function into a music function (a matter of s

Re: Strange Windows crash

Hello Mark, On 30/05/16 23:59, Mark Green wrote: I'm not top posting. I'm having a strange problem with the latest LilyPond in Frescobaldi crashing with a nonsense return code (-1073741819). Unfortunately it only happens on a rather large file and I haven't been able to produce a tiny example.

Re: Doc: Missing NR documentation for customizing the behavior of articulations in MIDI

Hiekki, replying via email than the tracker Ralph created (in case this is just noise I am adding). On 05/07/16 15:42, Heikki Tauriainen wrote: Hi, The post-2.18 changes to the default handling of articulations in MIDI (without using articulate.ly) are currently mentioned only near the botto

Re: additional entry in lilypond.org/productions.html?

On 08/07/16 11:36, Marc Hohl wrote: Hi list, I have written some musicals for children and adolescents in the past and have two more musicals in the pipeline, to be released at the end of 2016. https://sourceforge.net/p/testlilyissues/issues/4935/ Thanks. -- -- James _

Re: Manual page breaking causing assertion failure

David, On 21/07/16 20:41, David Kastrup wrote: Chris Yate writes: Hey Abraham / BugsList people, I'm guessing nobody had a chance to look at this problem. I'm experiencing it again, and it's really slowing me down. Is there anything else I can do to help debug / isolate the issue? It's stil

Re: doc clarification

Hello Martin, On 29/07/16 21:32, catalaco - wrote: The last paragraph of 1.2.2 LilyPond variables in Extending LilyPond is very hard to understand. The whole

Re: Fw: [PATCH] Eliminate accidental power chords in musicxml2ly.

Johan, On 30/09/16 07:37, Johan Vromans wrote: > Date: Thu, 18 Aug 2016 13:38:21 +0200 > From: Johan Vromans > To: David Kastrup > Subject: Re: [PATCH] Eliminate accidental power chords in musicxml2ly. > > > Hi David, > > On Thu, 18 Aug 2016 07:10:45 +0200 > David Kastrup wrote: > >>> > > I'll

Re: new italian translator

Federico, On 25/10/16 21:45, Federico Bruni wrote: > Hi folks > > Please add to Documentation/included/authors.itexi a new contributor, > who recently translated the whole Essay manual in italian: > > http://git.savannah.gnu.org/cgit/lilypond.git/commit/?h=translation&id=c72179ccf41124936a43bb7279

Re: Font cache issues on Windows 10

Hello, On 07/11/16 20:27, Gianmaria Lari wrote: > [Lilypond 2.19.49 slow compilation time and font cache] > > But the solution seems >> to be to simply delete the cache, prompting a rebuild, so it's not >> a big deal for most of us. > > It's not a big deal if you know it! > > Because it's a very a

Re: Error in printing ff

Hello Friedrich, On Sun, 19 Feb 2017 19:09:39 +0100 Friedrich Kink wrote: > Dear Simon, > > thanks for the fast answer. By chance I found another example which I > try to present as a snippet: > > \layout { > ragged-right = ##t > } > > \header { >title = \markup \sans { "Ach wie flücht

Re: DOC: Correcting spelling of Harmonia Sacra in NR 1.1.4 Shape note heads

Hello, On Sat, 30 Sep 2017 17:14:02 -0500, Karlin High wrote: > This is a nitpick. The places in the documentation that reference the > "Harmonia Sacra" songbook by Joseph Funk have the spelling Harmonica > Sacra. Harmonia does not have a "c" here. A few references are below. > There are enough

Re: DOC: Typo in CG 2.2 Where to get lily-git, "auxiliar" not "auxillar"

Hello On Fri, 22 Sep 2017 17:41:01 -0500, Karlin High wrote: > It's just ONE letter: > > lily-git is part of the LilyPond source code and is located in > ‘$LILYPOND_GIT/scripts/auxillar/lily-git.tcl’. > > But since it's command text, I tripped over it. I remember reading > that the main LilyPo

Re: conversion rule for set-octavation/ottava with wrong version number?

Alex, On Tue, 31 Oct 2017 22:35:59 +0100, Alex Schreiber wrote: > A file with content > > {c''' #(set-octavation 1) c''' #(set-octavation 0) c'''} > > compiles just fine in lilypond 2.12.0, but not in lilypond 2.18.2. However, > > convert-ly --from=2.12.0 --to=2.18.2 file.ly > > does not cha

Re: conversion rule for set-octavation/ottava with wrong version number?

Alex, On Tue, 31 Oct 2017 22:35:59 +0100, Alex Schreiber wrote: > A file with content > > {c''' #(set-octavation 1) c''' #(set-octavation 0) c'''} > > compiles just fine in lilypond 2.12.0, but not in lilypond 2.18.2. However, > > convert-ly --from=2.12.0 --to=2.18.2 file.ly > > does not cha

Re: a contribution

Phil, On Wed, 15 Nov 2017 11:04:17 -, "Phil Holmes" wrote: > > Betreff: a contribution > > Datum: Tue, 14 Nov 2017 10:28:15 -0800 > > Von: Bill Palmer > > An: u...@openlilylib.org > > > > The music sample shown on the page http://lilypond.org/text-input.html > > does not correspond with th

Re: What the docs say about markuplist

Mr Bannister On Wed, 13 Dec 2017 12:28:36 +0100, Robin Bannister wrote: > Hallo, > > http://lists.gnu.org/archive/html/lilypond-user/2017-12/msg00298.html > This user thread prompted me to look up \markuplist because >- I didn't recognise it >- from the example I couldn't guess what it

Re: make top-doc fails: could not open out/NEWS.texi: No such file or directory

David, On Sun, 31 Dec 2017 13:29:23 +0100, David Kastrup wrote: > Karl Lindén writes: > > > I found that installing the pdflatex program fixes the issue, but the > > failure is hardly user-friendly. Instead the build system should say > > something along the lines: "pdflatex was not found. Ple

Re: make top-doc fails: could not open out/NEWS.texi: No such file or directory

David, On Sun, 31 Dec 2017 13:29:23 +0100, David Kastrup wrote: Karl Lindén writes: I found that installing the pdflatex program fixes the issue, but the failure is hardly user-friendly. Instead the build system should say something along the lines: "pdfl

Re: Documentation clarification for variables

Joseph, On Thu, 25 Jan 2018 09:19:39 -0500, Joseph Austin wrote: > In LM 2.4.1 the discussion of variables leaves out essential information, the > "entry mode" of the data Without looking at that section and not being a big user of the LP software as such (what I do is very simple), is the in

Re: articulations above ledger lines

Hello, On Tue, 6 Feb 2018 15:47:45 +, Gilberto Agostinho wrote: > Hi all, > > According to Elaine Gould's /Behind Bars/, articulations should not > obscure ledger lines. I believe this is quite justifiable as though we > want them as close as possible to the note heads for quick recognit

Fwd: Re: articulations above ledger lines

keeping 'bug' in the loop Hi James, Thanks for your reply! On 06/02/18 18:30, James Lowe wrote: > We have a number of issue already about what looks similar to this - > basically Leger lines colliding with 'stuff'. > > E.g > > https://sourceforge.net/p

Re: Tremolo and partcombiner: core dump (assertion failure)

Rutger, On Sat, 10 Feb 2018 14:30:13 +0100, Rutger Hofman wrote: > Good afternoon list, > > the following combination of \partcombine and \tremolo gives a core dump > with the following error message: > > Preprocessing graphical objects...lilypond: > /home/gub/NewGub/gub/target/linux-64/src/

Re: Doc: 2.19 changes cuts off varC clef

Hello Malte On Sat, 24 Feb 2018 09:02:55 +0100, Malte Meyn wrote: > Hi list, > > the four varC clefs at > http://lilypond.org/doc/v2.19/Documentation/changes/ are cut off at the > top (all) and bottom (varC/altovarC). > > Cheers, > Malte I'm not seeing it __

Re: Doc: 2.19 changes cuts off varC clef

Hello On Sat, 24 Feb 2018 16:19:44 +0100, Noeck wrote: > Hi James, > > > I'm not seeing it > > But your picture shows it. > > All the varC-clefs have round "dots". In your picture, the lower two > (tenorvarC and baritonevarC) have the lower "dot" inside the staff. All > others are cropped and

Re: Doc: 2.19 changes cuts off varC clef

On Sat, 24 Feb 2018 15:14:37 + (GMT), "James Lowe" wrote: > Hello Malte > > On Sat, 24 Feb 2018 09:02:55 +0100, Malte Meyn wrote: > > > Hi list, > > > > the four varC clefs at > > http://lilypond.org/doc/v2.19/Documentation/changes/ are

Re: Doc: 2.19 changes cuts off varC clef

Hello On Sat, 24 Feb 2018 17:32:35 +0100 (CET), Werner LEMBERG wrote: > > This is a problem of bounding boxes. > > Well... > > > All the graphics files are being automatically cropped according to > > the characters' bounding boxes and as all the varC clefs don't have > > their proper heights

Re: Documentation error in PDF files

Hello Peter, On Sat, 17 Feb 2018 10:26:05 +, Peter Toye wrote: > The indexes in the PDF versions of the learning and notation manuals (and > maybe others) do not have the alphabetical "jump to" headers, which makes > scrolling a pain. They're in the HTML versions, so I can only assume this

  1   2   3   >