Re: Support articulations, slurs and breaths in MIDI (issue 26470047)

2013-11-27 Thread Devon Schudy
Janek WarchoĊ‚ wrote: > i don't understand why would someone not want to have at > least tremolo repeats unfolded I think everyone does want tremolo and percent unfolded; only volta needs customization. The global context already knows (via its Output_def) whether it's doing layout or midi. So the

New template for 'lilypond' made available

2013-11-27 Thread Translation Project Robot
Hello, gentle maintainer. This is a message from the Translation Project robot. (If you have any questions, send them to .) A new POT file for textual domain 'lilypond' has been made available to the language teams for translation. It is archived as: http://translationproject.org/POT-files

Suggestion: Keep original breaks

2013-11-27 Thread Urs Liska
Hi all, I would like to suggest an enhancement in the handling of line breaks that is useful for copying scores from existing models. Currently LilyPond can decide about breaks herself or we can manually force or prevent breaks. But when copying from or proof-reading against an existing score i

Re: Suggestion: Keep original breaks

2013-11-27 Thread David Kastrup
Urs Liska writes: > I would like to suggest an enhancement in the handling of line breaks > that is useful for copying scores from existing models. > Currently LilyPond can decide about breaks herself or we can manually > force or prevent breaks. > But when copying from or proof-reading against a

Re: Suggestion: Keep original breaks

2013-11-27 Thread Trevor Daniels
Urs Liska wrote Wednesday, November 27, 2013 10:30 AM > I would like to suggest an enhancement in the handling of line breaks > that is useful for copying scores from existing models. > > I suggest a command line option -dkeep-original-breaks for this switch. > That way the user can add that op

Re: Suggestion: Keep original breaks

2013-11-27 Thread Urs Liska
Am 27.11.2013 11:55, schrieb Trevor Daniels: Urs Liska wrote Wednesday, November 27, 2013 10:30 AM I would like to suggest an enhancement in the handling of line breaks that is useful for copying scores from existing models. I suggest a command line option -dkeep-original-breaks for this switc

Re: Suggestion: Keep original breaks

2013-11-27 Thread Urs Liska
Am 27.11.2013 11:48, schrieb David Kastrup: Urs Liska writes: I would like to suggest an enhancement in the handling of line breaks that is useful for copying scores from existing models. Currently LilyPond can decide about breaks herself or we can manually force or prevent breaks. But when co

New Dutch PO file for 'lilypond' (version 2.17.96)

2013-11-27 Thread Translation Project Robot
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the Dutch team of translators. The file is available at: http://translationproject.org/latest/lilypond/nl.po (We can arrange things so that

Re: Suggestion: Keep original breaks

2013-11-27 Thread David Kastrup
Urs Liska writes: > Of course I can achieve the same with tags. But there will be many > instances where I don't "need them anyway" because I don't really > care about the state of the original score except for this > simplification while inputting/proofing. So what? Why hard code one particul

Re: Suggestion: Keep original breaks

2013-11-27 Thread Urs Liska
Am 27.11.2013 12:25, schrieb David Kastrup: Urs Liska writes: Of course I can achieve the same with tags. But there will be many instances where I don't "need them anyway" because I don't really care about the state of the original score except for this simplification while inputting/proofing

Re: Suggestion: Keep original breaks

2013-11-27 Thread David Kastrup
Urs Liska writes: > I'm not talking about pushing something into LilyPond just for my > personal convenience but about adding a usability feature for a wider > audience. Breaks, and only breaks, that have a special command that can be disabled from the command line, and that can in practice only

Re: Suggestion: Keep original breaks

2013-11-27 Thread David Kastrup
David Kastrup writes: > I see nothing wrong with giving a command line option for setting > tags. That sounds useful, and it would most certainly encompass your > use case. It would also fit into LilyPond's current tool set, and > consequently into the documentation. The way one would do that

Re: Suggestion: Keep original breaks

2013-11-27 Thread Urs Liska
Am 27.11.2013 14:54, schrieb David Kastrup: Urs Liska writes: What I actually want is to add that behaviour as an option to Frescobaldi's Layout Control Mode. So what? I know you don't care about usability features involving graphical tools such as Frescobaldi, Denemo or whatever. But ther

Re: Suggestion: Keep original breaks

2013-11-27 Thread Urs Liska
Am 27.11.2013 15:01, schrieb David Kastrup: David Kastrup writes: I see nothing wrong with giving a command line option for setting tags. That sounds useful, and it would most certainly encompass your use case. It would also fit into LilyPond's current tool set, and consequently into the doc

Re: Suggestion: Keep original breaks

2013-11-27 Thread David Kastrup
Urs Liska writes: > Am 27.11.2013 14:54, schrieb David Kastrup: >> Urs Liska writes: >> >>> What I actually want is to add that behaviour as an option to >>> Frescobaldi's Layout Control Mode. >> So what? > > I know you don't care about usability features involving graphical > tools such as Fres

Re: Suggestion: Keep original breaks

2013-11-27 Thread David Kastrup
Urs Liska writes: > Am 27.11.2013 15:01, schrieb David Kastrup: >> David Kastrup writes: >> >>> I see nothing wrong with giving a command line option for setting >>> tags. That sounds useful, and it would most certainly encompass your >>> use case. It would also fit into LilyPond's current too

Re: Suggestion: Keep original breaks

2013-11-27 Thread Carl Sorensen
On 11/27/13 8:04 AM, "David Kastrup" wrote: >Urs Liska writes: > >> >> >> But also in this case I would come back and suggest including functions >>like >> >> originalBreak = >> #(define-music-function (parser location)() >> ( #{ \tag #'keep-original-breaks \break #} )) >> >> in LilyPond so th

Re: Suggestion: Keep original breaks

2013-11-27 Thread Urs Liska
Am 27.11.2013 16:25, schrieb Carl Sorensen: On 11/27/13 8:04 AM, "David Kastrup" wrote: Urs Liska writes: But also in this case I would come back and suggest including functions like originalBreak = #(define-music-function (parser location)() ( #{ \tag #'keep-original-breaks \break #}

Re: Suggestion: Keep original breaks

2013-11-27 Thread Carl Sorensen
On 11/27/13 8:32 AM, "Urs Liska" wrote: > >For me this sounds good. >Requiring to write \include "original-breaks.ly" is significantly better >than requiring to define the commands. >But it would still need a separate switch, presumably through the >command line. This is true, but it would be po

New Esperanto PO file for 'lilypond' (version 2.17.96)

2013-11-27 Thread Translation Project Robot
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the Esperanto team of translators. The file is available at: http://translationproject.org/latest/lilypond/eo.po (We can arrange things so t

Re: Suggestion: Keep original breaks

2013-11-27 Thread Urs Liska
Am 27.11.2013 16:36, schrieb Carl Sorensen: On 11/27/13 8:32 AM, "Urs Liska" wrote: For me this sounds good. Requiring to write \include "original-breaks.ly" is significantly better than requiring to define the commands. But it would still need a separate switch, presumably through the command

Re: Suggestion: Keep original breaks

2013-11-27 Thread David Kastrup
Urs Liska writes: > Am 27.11.2013 16:36, schrieb Carl Sorensen: >> On 11/27/13 8:32 AM, "Urs Liska" wrote: >> >>> For me this sounds good. >>> Requiring to write \include "original-breaks.ly" is significantly better >>> than requiring to define the commands. >>> But it would still need a separat

Re: Suggestion: Keep original breaks

2013-11-27 Thread Urs Liska
Am 27.11.2013 16:52, schrieb David Kastrup: Urs Liska writes: Am 27.11.2013 16:36, schrieb Carl Sorensen: On 11/27/13 8:32 AM, "Urs Liska" wrote: For me this sounds good. Requiring to write \include "original-breaks.ly" is significantly better than requiring to define the commands. But it

Re: Suggestion: Keep original breaks

2013-11-27 Thread Carl Sorensen
On 11/27/13 8:45 AM, "Urs Liska" wrote: >Am 27.11.2013 16:36, schrieb Carl Sorensen: >> On 11/27/13 8:32 AM, "Urs Liska" wrote: >> >>> For me this sounds good. >>> Requiring to write \include "original-breaks.ly" is significantly >>>better >>> than requiring to define the commands. >>> But it

Re: Suggestion: Keep original breaks

2013-11-27 Thread Urs Liska
Am 27.11.2013 15:52, schrieb David Kastrup: Urs Liska writes: Am 27.11.2013 14:54, schrieb David Kastrup: Urs Liska writes: What I actually want is to add that behaviour as an option to Frescobaldi's Layout Control Mode. So what? I know you don't care about usability features involving g

Re: Suggestion: Keep original breaks

2013-11-27 Thread David Kastrup
Urs Liska writes: > Am 27.11.2013 15:52, schrieb David Kastrup: >> Urs Liska writes: >> >>> Am 27.11.2013 14:54, schrieb David Kastrup: Urs Liska writes: > What I actually want is to add that behaviour as an option to > Frescobaldi's Layout Control Mode. So what? >>> I kn

New French PO file for 'lilypond' (version 2.17.96)

2013-11-27 Thread Translation Project Robot
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the French team of translators. The file is available at: http://translationproject.org/latest/lilypond/fr.po (We can arrange things so that

LILY-GIT PITA

2013-11-27 Thread James
Hello, Am i the only one using lily-git.tcl of the *active* dev team? I ask because since it was changed a couple of years or so ago that it *always* assumes you want/need to be on dev/local_working it really makes it a PITA for me to work with. I've been trying to make a simple patch this ev

Re: LILY-GIT PITA

2013-11-27 Thread Phil Holmes
- Original Message - From: "James" To: "Devel" Sent: Wednesday, November 27, 2013 9:05 PM Subject: LILY-GIT PITA Hello, Am i the only one using lily-git.tcl of the *active* dev team? I ask because since it was changed a couple of years or so ago that it *always* assumes you want/n

New Dutch PO file for 'lilypond' (version 2.17.96)

2013-11-27 Thread Translation Project Robot
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the Dutch team of translators. The file is available at: http://translationproject.org/latest/lilypond/nl.po (We can arrange things so that