On 14.02.2014 18:46, Pierre Perol-Schneider wrote:
I cannot find where the problem comes from.
Me neither; convert-ly doesn't rearrange anything.
If you move the "cue" voice down past the other
(anonymous) voice, then \lyricsto can find it.
But surely you shouldn't have to do that?
Cheers,
2014-02-14 20:56 GMT+01:00 Robin Bannister :
>
> If you are referring to the horizontal distortion,
> this is cured by prefixing the extra-spacing-width
> override with "Staff.".
>
>
Thanks Robin.
In fact but I was more concern by the long comments :
%%
On 14.02.2014 20:05, Pierre Perol-Schneider wrote:
[...] ask him how
he would see his snippet upgraded ?
http://lsr.dsi.unimi.it/LSR/Item?id=651
If you are referring to the horizontal distortion,
this is cured by prefixing the extra-spacing-width
override with "Staff.".
Cheers,
Robin
__
Hi to All,
Do anyone of you have contact with Alexander Kobel in order to ask him how
he would see his snippet upgraded ?
http://lsr.dsi.unimi.it/LSR/Item?id=651
Cheers,
Pierre
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/ma
On 14/02/14 17:46, Pierre Perol-Schneider wrote:
Dear All,
I'm stuck with this fairly small code :
http://lsr.dsi.unimi.it/LSR/Item?id=347
Conversion to v2.16 works fine.
Conversion to v2.18 gives me :
.../cue-with-lyrics.ly:33:37: warning: cannot find Voice `cue'
\context Lyrics = cueLyrics
\l
Dear All,
I'm stuck with this fairly small code :
http://lsr.dsi.unimi.it/LSR/Item?id=347
Conversion to v2.16 works fine.
Conversion to v2.18 gives me :
.../cue-with-lyrics.ly:33:37: warning: cannot find Voice `cue'
\context Lyrics = cueLyrics
\lyricsto "cue" {
It's probably very simple but I th
2014-02-14 17:44 GMT+01:00 David Kastrup :
>
> Wasn't part of that snippet involved with that?
>
Indeed.
It was just the reflection of what I've read here :
http://www.lilypond.org/doc/v2.18/Documentation/notation/what-goes-into-the-midi-output_003f.html
Uncomment "\music" will give a midi output
Pierre Perol-Schneider writes:
> %% Tremolos entered with ‘:[number]’ are not are reflected in the MIDI
> output :
> and compare with the link.
Looks like an improvement overall, but what's with the "are not
reflected in the MIDI output" bit?
Wasn't part of that snippet involved with that?
--
2014-02-14 17:14 GMT+01:00 James :
> What 'changed'?
>
>
Check the *.ly file I've sent :
%%%
\version "2.18.0"
music = \relative c' {
c4:16 d2: e4:
f1:
g8: f: e: d: d2:
}
musicMidi = \relative c' {
\repeat tremolo 4 c16
\repeat tremolo 8 d
\repeat tremolo 4 e
\repeat
Pierre,
On 14/02/14 13:54, Pierre Perol-Schneider wrote:
Hi Squad,
Please find herewith my update proposition for the following snippet :
http://lsr.dsi.unimi.it/LSR/Item?id=604
Thanks in advance for your approval.
Pierre
___
bug-lilypond mailing l
Hi Squad,
Please find herewith my update proposition for the following snippet :
http://lsr.dsi.unimi.it/LSR/Item?id=604
Thanks in advance for your approval.
Pierre
music = \relative c' {
c4:16 d2: e4:
f1:
g8: f: e: d: d2:
}
musicMidi = \relative c' {
\repeat tremolo 4 c16
\repeat t
Original-Nachricht
David Kastrup writes:
Thomas Scharkowski writes:
Sorry,
his and hisis do work, as opposed to heses, which does not.
Could you check your statements before making them? It makes the
discussion less awkward.
There must have been a typo in my test
Hi James,
Hi Harm,
Hi David,
On 2014-02-13 22:47 GMT+01:00 James wrote:
*Isn't there a standard practice for making a snippet shown as deprecated?*
Never heard of.
On 2014-02-14 0:10 GMT+01:00 Harm wrote:
*Did you succed contacting Seba already? *
No I don't. No answer up to now.
On 2014-02-14
"Phil Holmes" writes:
> "David Kastrup" wrote in message
> news:87y51e5h6e@fencepost.gnu.org...
>> Thomas Morley writes:
>>
>>> Regarding the snippet:
>>> Because it is _not_ tagged docs I'd simply delete it.
>>
>> Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so
>> on
"David Kastrup" wrote in message
news:87y51e5h6e@fencepost.gnu.org...
Thomas Morley writes:
Regarding the snippet:
Because it is _not_ tagged docs I'd simply delete it.
Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so
one should just take them from Documentation/sn
David Kastrup writes:
> Thomas Scharkowski writes:
>
>> Sorry,
>>
>> his and hisis do work, as opposed to heses, which does not.
>
> Could you check your statements before making them? It makes the
> discussion less awkward.
Rereading the above, my point is non-obvious: heses works just as wel
Thomas Scharkowski writes:
> Sorry,
>
> his and hisis do work, as opposed to heses, which does not.
Could you check your statements before making them? It makes the
discussion less awkward.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypo
Original-Nachricht
Thomas Scharkowski schrieb:
Sorry,
his and hisis do work, as opposed to heses, which does not.
There is no "hes" :-)
Yeah, _if_ one would consider this a bug then it would be in the German naming
conventions outside of LilyPond :-)
We all know
Thomas Scharkowski writes:
> Original-Nachricht
>
>> It would be nice if you could add support for the german style notation.
>> What do I mean exactly? By default (english notation) the notes are:
>> C D E F G A B
>>
>> in german notation:
>> C D E F G A H
>>
>> See the differe
Thomas Scharkowski schrieb:
>Sorry,
>
>his and hisis do work, as opposed to heses, which does not.
>There is no "hes" :-)
>
Yeah, _if_ one would consider this a bug then it would be in the German naming
conventions outside of LilyPond :-)
>
> Original-Nachricht
>
>> \langua
Sorry,
his and hisis do work, as opposed to heses, which does not.
There is no "hes" :-)
Original-Nachricht
\language "deutsch"
{h his hisis asas}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/
Zsolt Tempfli writes:
> It would be nice if you could add support for the german style notation.
> What do I mean exactly? By default (english notation) the notes are:
> C D E F G A B
>
> in german notation:
> C D E F G A H
>
> See the difference between the two last notes: B and H. Now here are
Original-Nachricht
It would be nice if you could add support for the german style notation.
What do I mean exactly? By default (english notation) the notes are:
C D E F G A B
in german notation:
C D E F G A H
See the difference between the two last notes: B and H. Now here
On 14 February 2014 09:46, Zsolt Tempfli wrote:
> It would be nice if you could add support for the german style notation.
> What do I mean exactly? By default (english notation) the notes are:
> C D E F G A B
>
> in german notation:
> C D E F G A H
>
> See the difference between the two last note
James writes:
>> Actually 2.16 is what we want, so we get lucky here. But the point is
>> that most snippets will not be what is wanted. What one can do for any
>> particular snippet is something like
>>
>> git log -S '\version "2.16.0"' -p
>> Documentation/snippets/new/chant-or-psalms-notation
It would be nice if you could add support for the german style notation.
What do I mean exactly? By default (english notation) the notes are:
C D E F G A B
in german notation:
C D E F G A H
See the difference between the two last notes: B and H. Now here are some
equivalences:
English: BESES - B
On 14/02/14 08:27, David Kastrup wrote:
James writes:
On 14/02/14 06:42, David Kastrup wrote:
Thomas Morley writes:
Regarding the snippet:
Because it is _not_ tagged docs I'd simply delete it.
Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so
one should just take them
James writes:
> On 14/02/14 06:42, David Kastrup wrote:
>> Thomas Morley writes:
>>
>>> Regarding the snippet:
>>> Because it is _not_ tagged docs I'd simply delete it.
>> Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so
>> one should just take them from Documentation/snipp
28 matches
Mail list logo
