Some engraver brainstorming (was: Following voices in chords?)

Had a rather sleepless night after starting coding yesterday evening. And came up with some ideas. Idea#1 (that which I started coding on) is rather straightforward: replace all the data structures in the glissando_engraver by deques and work with them in the obvious manner. Now what if I want t

fixing the LM "verse and refrain" example

*** This refers to LM 3.2.3 "Voices and vocals" *** Trevor Daniels wrote: > I put this in after several questions on -user about how > this should be done, but I wasn't very happy with it. If > you can come up with a better way of coding a solo verse > going into a two-part refain let's change it

Re: MetronomeMark alignment (once again)!

On 5/7/10 3:35 PM, "Neil Puttock" wrote: > > I only have Gardner Read to hand, and he says the following: > > "The initial letter of the term (usually a capital) customarily is > aligned over the meter signature, or notational element of the measure, such as noteheads, accidentals, > repeat s

Re: Following voices in chords?

On 5/7/10 9:37 AM, "David Kastrup" wrote: > Carl Sorensen writes: > >> On 5/7/10 8:54 AM, "David Kastrup" wrote: >> >>> Carl Sorensen writes: >>> >>> I appreciate your consistent questioning as to how we might be able to get LilyPond to behave in a way that seems consistent wi

Re: MetronomeMark alignment (once again)!

On 6 May 2010 20:16, Xavier Scheuer wrote: > I'm not a developer but does this mean that: > >  1. the "break-align" support is ready for MetronomeMark, >  2. but that the PATCH has not been applied because MetronomeMark >     used to align on note columns (this means the notes, right?) >  3. and

Re: Issue 684: break-align-symbol support

On 5 May 2010 14:40, Kieren MacMillan wrote: > Has there been any progress/thinking towards >     > ?? Not from me, I'm afraid, though I might return to it once I've cleared up all my other half-finished patches. :) Cheers, Neil

Re: Doc: Reorganize music functions material. (issue1031044)

LGTM. http://codereview.appspot.com/1031044/show ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Aligning single systems?

"Boris Shingarov" writes: > Hi David, > >> for theoretical work it often is necessary to write several short > > systems in one line, interspersed with text.   > This is exactly what we are doing. > > > I don't manage to have > > a) new systems continue aligned to the previous system in a lin

Re: LSR texidocs missing -es suffix

On 4 May 2010 23:49, Francisco Vila wrote: > Yes, putting the suffix had only sense when the same file (located in > input/texidocs) mixed various translations, now they are kept away in > our lang/ directories. Ah yes, I'd completely forgotten they used to be lumped together. > If your patch l

Re: Doc: LM: Reformat ly code. (issue1056041)

On Fri, May 07, 2010 at 01:31:35PM -0700, Mark Polesky wrote: > Graham Percival wrote: > > http://codereview.appspot.com/1056041/diff/33001/27003#newcode2481 > > Documentation/learning/fundamental.itely:2481: << > > There is *still* an indentation mistake here. This is the > > third time I've poin

Re: Doc: Reorganize music functions material. (issue1031044)

On 2010/05/07 12:20:50, Graham Percival wrote: The patch looks ok, but I'm getting some weird build errors... quite possibly the same thing Werner noticed (wherein lilypond-book borks if it has two identical snippets). No problems here following a clean build. Cheers, Neil http://coderevi

Re: Doc: LM: Reformat ly code. (issue1056041)

Graham Percival wrote: > http://codereview.appspot.com/1056041/diff/33001/27003#newcode2481 > Documentation/learning/fundamental.itely:2481: << > There is *still* an indentation mistake here. This is the > third time I've pointed it out -- do we disagree on the > "two-space indents" rule? Graham,

Re: Following voices in chords?

Carl Sorensen writes: > On 5/7/10 8:54 AM, "David Kastrup" wrote: > >> Carl Sorensen writes: >> >> >>> I appreciate your consistent questioning as to how we might be able to >>> get LilyPond to behave in a way that seems consistent with our >>> expectations. I wish I had the time to understa

Re: Aligning single systems?

David: > Hi, for theoretical work it often is necessary to write several short > systems in one line, interspersed with text. > > I don't manage to have > a) new systems continue aligned to the previous system in a line, like > when doing ... > b) to have interspersed text appear at useful height

Re: Aligning single systems?

Hi David, for theoretical work it often is necessary to write several short > systems in one line, interspersed with text.   This is exactly what we are doing. > I don't manage to have > a) new systems continue aligned to the previous system in a line, like > when doing > \line { \score {

Re: Following voices in chords?

Graham Percival writes: > On Fri, May 07, 2010 at 04:29:42PM +0200, David Kastrup wrote: >> Well, looks like a fair piece of work. And if one invests all this >> work... I guess it would be nicer if one could write > e\glissando g\glissando> and notes got matched one by one. And >> possibly le

Re: Following voices in chords?

On 5/7/10 8:54 AM, "David Kastrup" wrote: > Carl Sorensen writes: > > >> I appreciate your consistent questioning as to how we might be able to >> get LilyPond to behave in a way that seems consistent with our >> expectations. I wish I had the time to understand the internals of >> parsing

Re: Following voices in chords?

On 5/7/10 8:55 AM, "Graham Percival" wrote: > On Fri, May 07, 2010 at 04:29:42PM +0200, David Kastrup wrote: >> Well, looks like a fair piece of work. And if one invests all this >> work... I guess it would be nicer if one could write > e\glissando g\glissando> and notes got matched one by o

Re: Following voices in chords?

On Fri, May 07, 2010 at 04:29:42PM +0200, David Kastrup wrote: > Well, looks like a fair piece of work. And if one invests all this > work... I guess it would be nicer if one could write e\glissando g\glissando> and notes got matched one by one. And > possibly let \glissando be the same as that

Re: Following voices in chords?

Carl Sorensen writes: > On 5/7/10 8:29 AM, "David Kastrup" wrote: >> Well, looks like a fair piece of work. And if one invests all this >> work... I guess it would be nicer if one could write > e\glissando g\glissando> and notes got matched one by one. >> And possibly let \glissando be the sa

Re: Following voices in chords?

On 5/7/10 8:29 AM, "David Kastrup" wrote: > Carl Sorensen writes: > >> I recognize that it takes a different tack than you want, because it only >> goes note for note instead of chord for chord. But it shows the way to get >> the spacing you want and to avoid the clashing note columns. >> >>

Re: Following voices in chords?

Carl Sorensen writes: > On 5/7/10 7:21 AM, "David Kastrup" wrote: >> >> Hi, how would I do something like the following _properly_: >> >> { \clef bass << >> { \glissando s4 4 } >> \new Voice { \hideNotes \glissando s4 4 } >> \new Voice { \hi

Re: Translation errors in German documentation

On 5/7/10 12:36 AM, "Marc Hohl" wrote: > I found some typos and translation errors in the German documentation > of the current development version. > > Should I create a patch to correct them, or should I inform the > current translator about my observations - or both? It seems to me that crea

Re: Following voices in chords?

On 5/7/10 7:21 AM, "David Kastrup" wrote: > > Hi, how would I do something like the following _properly_: > > { \clef bass << > { \glissando s4 4 } > \new Voice { \hideNotes \glissando s4 4 } > \new Voice { \hideNotes \glissando s4 4 } >>> >

Re: Following voices in chords?

Hi David, > this is already better than the snippet version for double glissandi Does Carl's recent "multi-gliss" snippet/macro not suffice to do what you need? Cheers, Kieren. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.or

Re: Following voices in chords?

Kieren MacMillan writes: > Hi David, > >> this is already better than the snippet version for double glissandi > > Does Carl's recent "multi-gliss" snippet/macro not suffice to do what > you need? That keyword does not ring a bell with either Google search or the Lilypond source tree, nor my mem

Aligning single systems?

Hi, for theoretical work it often is necessary to write several short systems in one line, interspersed with text. I don't manage to have a) new systems continue aligned to the previous system in a line, like when doing \line { \score { ... \layout {} } some text \score { ... \layout {} } } It m

Re: translation problems in website

On Fri, May 7, 2010 at 8:45 AM, Francisco Vila wrote: > 2010/5/6 Jean-Charles Malahieude : > >> There still remains a /big/ problem: > > We are talking about issue #1036, > http://code.google.com/p/lilypond/issues/detail?id=1036 > > http://lists.gnu.org/archive/html/lilypond-devel/2010-03/msg00219

Translation errors in German documentation

I found some typos and translation errors in the German documentation of the current development version. Should I create a patch to correct them, or should I inform the current translator about my observations - or both? Marc ___ lilypond-devel mail

Following voices in chords?

Hi, how would I do something like the following _properly_: { \clef bass << { \glissando s4 4 } \new Voice { \hideNotes \glissando s4 4 } \new Voice { \hideNotes \glissando s4 4 } >> } Note that this has several deficiencies: We

Re: Doc: LM: Reformat ly code. (issue1056041)

Looks (mostly) good to me, other than the below 2 items. http://codereview.appspot.com/1056041/diff/33001/27003 File Documentation/learning/fundamental.itely (right): http://codereview.appspot.com/1056041/diff/33001/27003#newcode1339 Documentation/learning/fundamental.itely:1339: @c TODO: This

Re: translation problems in website

2010/5/6 Jean-Charles Malahieude : > There still remains a /big/ problem: > I can get back and forth in the split-html versions. > But, with the big-page versions, as soon as a link contains any accented > character (e.g "Communauté" for me or "Código fuente" for Paco), it does not > reach it. > So

Re: Doc: Reorganize music functions material. (issue1031044)

The patch looks ok, but I'm getting some weird build errors... quite possibly the same thing Werner noticed (wherein lilypond-book borks if it has two identical snippets). My main goal today was to check Patrick's build system changes, so I'll have to leave it with this vague warning. If you can

Re: translation problems in website

2010/5/6 Jean-Charles Malahieude : > There still remains a /big/ problem: > I can get back and forth in the split-html versions. > But, with the big-page versions, as soon as a link contains any accented > character (e.g "Communauté" for me or "Código fuente" for Paco), it does not > reach it. > S

Re: Doc: LM: Reformat ly code. (issue1056041)

patch set 4 is up: http://codereview.appspot.com/1056041 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: Reorganize music functions material. (issue1031044)

patch set 4 is up: http://codereview.appspot.com/1031044 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel