n the languages supported in my
Frescobaldi installation) plus dagger and double dagger that might be
used as footnote marks.
Cheers,
Alexander
On 2016-12-09 00:50, Thomas Morley wrote:
2016-12-07 1:07 GMT+01:00 Alexander Kobel :
Hi all,
yet another semi-feature request where I'm runn
On 2016-12-07 23:59, Thomas Morley wrote:
2016-12-07 22:03 GMT+01:00 Simon Albrecht :
On 07.12.2016 11:45, Alexander Kobel wrote:
I'm not sure whether Harm's proof of concept also involved
pre-compile-time modifications.
It certainly didn’t; Harm is a Schemer, not a C++ guy :-
Hi all,
On 2016-12-10 08:33, Noeck wrote:
Dear Alexander,
a very nice score!
thanks Joram and Knut.
I don't like to spoil it but in the last line (measure 30) I see an
extra hyphen.
I like that you spoil, that's why I posted it - always better to hame
some more pairs of eyes look at it a
On 2016-12-10 11:50, Michael Gerdau wrote:
And with this, all of this week's issues of mine are worked around, and
I can proudly present a beautiful little setting of a beautiful little
piece by Reger... :-)
Nice one
(Others already mentioned the two hyphen in bar 30)
Would you share the sourc
On 2016-12-10 09:40, Knut Petersen wrote:
Am 10.12.2016 um 00:36 schrieb Alexander Kobel:
[...] And with this, all of this week's issues of mine are worked
around, and I can proudly present a beautiful little setting of a
beautiful little piece by Reger... :-)
Those old settings by Max
On 2016-12-10 20:20, Noeck wrote:
Hi Alexander,
where is this from: conditional-kill-lyric-extender-callback?
Does it have any drawback?
Hi Joram,
glad it helped. It seems that I wrote it, probably modeled after a
suggestion by Kieren:
https://lists.gnu.org/archive/html/lilypond-user/2012
Hi again,
On 2016-12-10 23:33, Alexander Kobel wrote:
On 2016-12-10 20:20, Noeck wrote:
Hi Alexander,
where is this from: conditional-kill-lyric-extender-callback?
[...]
It is a perfect solution for a problem I had for quite some time:
In chorales (4 voices, mostly homophone), I often have
Hi Joram.
On 2016-12-11 09:28, Noeck wrote:
Hi Alexander,
Am 11.12.2016 um 01:17 schrieb Alexander Kobel:
Ah, no, here's the problem, as can be readily seen in the "Brich an, o
schönes Morgenlicht", first full measure
I don't think so. Because for notes like the secon
On 2016-12-11 11:04, Alexander Kobel wrote:
Hi Joram.
On 2016-12-11 09:28, Noeck wrote:
Hi Alexander,
Am 11.12.2016 um 01:17 schrieb Alexander Kobel:
Ah, no, here's the problem, as can be readily seen in the "Brich an, o
schönes Morgenlicht", first full measure
I don'
On 2016-12-10 23:33, Alexander Kobel wrote:
On 2016-12-10 20:20, Noeck wrote:
[...]
Would it be possible to have automatic extender lines? For every melisma
there is an extender line if it would be longer than the minimum-length?
Hm. Iterate over lyrics and add Extender events for each
On 2016-12-11 17:24, Knut Petersen wrote:
Am 11.12.2016 um 09:05 schrieb Simon Albrecht:
Sorry to ask so bluntly, but can it really be that simple? I thought a
solution must consider the x-extent of the syllable vs. the melisma as
well…
I think this is sufficiently easy to handle with the sche
Hi Knut, hi all.
On 2016-12-12 00:52, Knut Petersen wrote:
Hi Alexander
IIUC (I didn't compile it in), your patch inhibits extenders on a
single note, correct?
Yes.
Is that really what we want unconditionally,
Currently we get a short extender ... that is imho of no use and should
be kill
Hi,
On 2016-12-12 12:24, Peter Toye wrote:
Andrew, Urs,
Thanks both for the ideas. It's interesting.
Andrew's method works but gives a warning about clashing note columns
but the layout is fine.
you can add a
\once \override NoteColumn.ignore-collision = ##t
before \stemDown; this will sup
Hi,
On 2016-12-12 13:27, Andrew Bernard wrote:
On 12 December 2016 at 23:24, Alexander Kobel mailto:a-ko...@a-kobel.de>> wrote:
BTW: Has this warning been disabled somewhere in the unstable
versions? From 2.19.49, I get no complaint even for
<< { \stemDown b' } \
On 2016-12-12 13:42, Urs Liska wrote:
[...]
BTW: Has this warning been disabled somewhere in the unstable
versions?
From 2.19.49, I get no complaint even for
<< { \stemDown b' } \\ a' >>
which clearly collides...
I think in this example there actually is no colliding-note-column clash
bec
On 2016-12-12 13:48, Knut Petersen wrote:
Hi everybody!
Please test and comment, patch and examples attached.
Hi Knut,
works beautifully, as far as your code is concerned. But I found a bug
in my function (add-lyric-extenders): Unintuitively, adding an extender
after _ makes extenders disap
Hi.
On 2016-12-10 20:23, Knut Petersen wrote:
Am 07.12.2016 um 23:59 schrieb Thomas Morley:
So here a very first shot.
Thanks for your work. I think the attached code shows a problem of your
code ...
Back on the topic for this thread. I also noticed that behavior, and I
thought I have a fi
Dear all,
On 2016-12-10 00:12, Alexander Kobel wrote:
[...]
AFAICS, everything works beautifully as expected, with one strange
exception: in a chord with two equal notes, the default algorithm
chooses the right one as reference, your method chooses the reference
point depending on the stem
On 2016-12-14 07:50, Knut Petersen wrote:
Hi Alexander!
add-lyric-extenders =
#(define-music-function (parser location lyrics) (ly:music?)
You don't need "parser location".
Hi Knut,
I think I do - see the post on lily-devel. AFAIK, the type check (here:
ly:music?) is applied to the third
On 2016-12-14 07:12, Knut Petersen wrote:
Am 13.12.2016 um 22:43 schrieb Alexander Kobel:
On 2016-12-12 13:48, Knut Petersen wrote:
Hi everybody!
Please test and comment, patch and examples attached.
Hi Knut,
works beautifully, as far as your code is concerned. But I found a bug
in my
On 2016-12-14 11:03, Urs Liska wrote:
Am 14.12.2016 um 10:45 schrieb Alexander Kobel:
On 2016-12-14 07:50, Knut Petersen wrote:
Hi Alexander!
add-lyric-extenders =
#(define-music-function (parser location lyrics) (ly:music?)
You don't need "parser location".
Hi Knut
Dear all,
is there any way to recreate the attached situation in "pure" LilyPond?
What I'm after is a startStaff on steroids that can reinstantiate an entire
ChoirStaff or GrandStaff, including the brace or bracket. I've mostly seen this
in dense D.S. al coda situations, but also in certain othe
Hi Kieren, all,
On 2024-06-26 02:36, Kieren MacMillan wrote:
> Hi Alex,
>
>> is there any way to recreate the attached situation in "pure" LilyPond?
>
> Do you mean other than three markups with scores in them?
right. Three markups would essentially lead me to reinventing lyLuaTeX, which
doubl
024 at 10:42, Alexander Kobel <mailto:a-ko...@a-kobel.de>> wrote:
>>
>> So, first question "simply" is: Does anyone know a way to produce a
>> ChoirStaff bracket at the beginning of measure 2? ;-)
>
> Hello,
>
> See
> https://lists.gnu.org/arc
Hi David,
> # re-collate into book signature
> pdfjam $1-out-2up.pdf --signature $2 --paper a3 --landscape --outfile
> $1-sig.pdf
> It *appears* to work perfectly. The final output looks fine on my PDF viewer
> (Sumatra). When printed out, however, the scores themselves are undersize.
>
401 - 425 of 425 matches
Mail list logo
