Re: lilypad is localized?

Federico Bruni writes: > I can't remember if LilyPad for Windows is localized and I don't have > Windows machines to test it myself. > Just to know if I should translate the lilypad menus in the Documentation > or not. That question is easy to answer: _you_ should not translate the Lilypad menu

lilypad is localized?

I can't remember if LilyPad for Windows is localized and I don't have Windows machines to test it myself. Just to know if I should translate the lilypad menus in the Documentation or not. Thanks Federico ___ lilypond-devel mailing list lilypond-devel@gnu

Make "Adding extra fingering with scheme" snippet do something useful (issue 13826047)

LGTM Question: considering LSR-update, I recently added an earlier version of it to the LSR http://lsr.dsi.unimi.it/LSR/Item?id=887 Should I replace it with this one? https://codereview.appspot.com/13826047/ ___ lilypond-devel mailing list lilypond-de

Re: Stem direction snippet

Phil Holmes wrote Friday, September 27, 2013 8:54 PM > I've added a snippet (http://lsr.dsi.unimi.it/LSR/Item?id=751) to master > that explains how to set stem direction based on surrounding notes. Anyone > object to my adding it to selected snippets in > http://www.lilypond.org/doc/v2.16/Doc

Stem direction snippet

I've added a snippet (http://lsr.dsi.unimi.it/LSR/Item?id=751) to master that explains how to set stem direction based on surrounding notes. Anyone object to my adding it to selected snippets in http://www.lilypond.org/doc/v2.16/Documentation/notation/inside-the-staff#stems - I think it makes

Re: Add backup option to convert-ly (Issue 3572) (issue 14040043)

This suggestion from David sounded like a good default: Make numbered backups for files that have numbered backups already. https://codereview.appspot.com/14040043/diff/1/scripts/convert-ly.py File scripts/convert-ly.py (right): https://codereview.appspot.com/14040043/diff/1/scripts/convert-ly

Re: Release News - to include something about convert.ly

I did mean to consider doing something like that with the most recent release, but also forgot... "Please remember that new releases can require syntax changes. Please use convert-ly (web link) to make most of these automatically." -- Phil Holmes - Original Message - From: James

Release News - to include something about convert.ly

Hello, Would it be worthwhile that we add an extra sentence in the 'release news' (Documentation / web / news-front.itexi) informing users that they might need to use convert.ly - just that we occasionally get users 'forgetting' or not knowing that they _might_ need to use convert.ly for newer ver

Re: [Lilypond-auto] Issue 3566 in lilypond: Grace notes should beautobeamed

> Comment #6 on issue 3566 by d...@gnu.org: Grace notes should be autobeamed > I don't think the current state warrants a convert-ly rule: it does not > seem like the previous behavior is used to any reasonable degree, and it > can always be reverted by removing the engraver. Anything that h

Re: no critical: 2.18 is close?

David Kastrup wrote Friday, September 27, 2013 1:33 PM > I think after letting 2.17.27 settle for a few days, we are ready to > create the branch. We still might make another 2.17 release afterwards > to get some exposure to final fixes (like the \fill-line markup), but it > better not have any

Add backup option to convert-ly (Issue 3572) (issue 14040043)

Reviewers: Julien Rioux, dak, Message: Initial patch to check the principle is OK. Will require documentation updates before it's pushed. Please review Eluze's Python. Description: Add backup option to convert-ly (Issue 3572) Please review this at https://codereview.appspot.com/14040043/ Aff

Re: no critical: 2.18 is close?

- Original Message - From: "David Kastrup" To: "Federico Bruni" Cc: "lilypond-devel" Sent: Friday, September 27, 2013 1:33 PM Subject: Re: no critical: 2.18 is close? Federico Bruni writes: I see there's no critical issue in the tracker. I remember that you used to publish releas

Re: no critical: 2.18 is close?

Federico Bruni writes: > I see there's no critical issue in the tracker. > I remember that you used to publish release candidates of next stable when > we have no critical issues. > So I wonder if the releae of 2.18 is close or there's something that it's > blocking it.. The release of 2.18 is n

no critical: 2.18 is close?

I see there's no critical issue in the tracker. I remember that you used to publish release candidates of next stable when we have no critical issues. So I wonder if the releae of 2.18 is close or there's something that it's blocking it.. Just curious.. and also I want to organize my translation w

scripts: improve strip-whitespace.py (issue 13720049)

LGTM. You might want to add to your comment at the top: "Also convert the file to Unix line endings." https://codereview.appspot.com/13720049/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: improving our contributing tools and workflow

On 27/09/13 03:44, Graham Percival wrote: On Thu, Sep 26, 2013 at 03:12:27PM +0200, Joseph Rushton Wakeling wrote: This risks becoming another corrosive discussion, Then WTF are you starting it? Because I had hoped that what I said was sufficiently qualified not to create bad feeling. Obvi

PATCHES: Countdown for October 1st - 06:00 GMT

Hello, *Countdown – October 1st – 06:00 GMT* * * * * * * * * * * * * * * * * * * 3582 Enhancement David Kastrup countdown Pat

Re: Quarter-tone arrow notation [was: Re: improving our contributing tools and workflow]

Joseph Rushton Wakeling writes: > On 26/09/13 18:38, David Kastrup wrote: >> You commented on the issue where this patch originated as late as July: >> http://code.google.com/p/lilypond/issues/detail?id=1278#c7>. So >> it's hard to argue that it was not discoverable to you. > > This July I got a

Re: Quarter-tone arrow notation [was: Re: improving our contributing tools and workflow]

On 26/09/13 18:38, David Kastrup wrote: You commented on the issue where this patch originated as late as July: http://code.google.com/p/lilypond/issues/detail?id=1278#c7>. So it's hard to argue that it was not discoverable to you. This July I got an email update from the issue, and responded.

Re: Microtonality

On 27 Sep 2013, at 08:45, David Kastrup wrote: > Hans Aberg writes: > >> On 26 Sep 2013, at 17:16, Phil Holmes wrote: >> The section originates with me but I got diverted into trying to create a more elegant solution for how to rewrite accidentals in transposed music. It was al

Re: arrow notation for quarter-tones, issue 1278 (was: improving contributing tools)

On 27 Sep 2013, at 00:05, Janek Warchoł wrote: > Hi, > > 2013/9/26 Hans Aberg : >> On 26 Sep 2013, at 17:16, Phil Holmes wrote: >>> Joseph Wakeling wrote: >>> I was also rather discouraged by the fact that the quarter-tone arrow >>> notation issue didn't find a solution -- see: https://c