> Hi :)
>
> In case you didn't read my original post:
>
> I am creating a score for a piece of H. Schütz with Lilypond 2.2.5
> (with Fink on Mac). When setting this old kind of music it is often
> better to not use a standard Choirstaff, but to use the bar lines only
> between the bars. As far
Hello,
I run lilypond on a debian woody. I am very pleased with this software (big
thanks to all the people involved in this project, it's *great* :-)
It seems i have a problem with the font in the pdf files: everything
looks fine, except
for the letter 'u' in the titles, which looks weird.
This a
Hello.
> But this did not help me. The problem remains (with 2.4.2 version)
> exactly the same. I have the very same warning message during
> compilation (translated from french) :
>
> Warning : too much "column-note" collisions. Will be ignored.
I would guess that this warning comes from so
Gilles Harfang a écrit :
Modify the "basse" \context, as follows:
%-
\context Staff = "basse" <<
\global
\clef bass
\context Voice = "basse" { \voiceTwo \basse }
\context Voice = "choral" { \voiceOne \choraltheme }
>>
%-
I tried to use the following instruction
[EMAIL PROTECTED] (Pedro Kröger) writes:
> Nicolas Sceaux <[EMAIL PROTECTED]> writes:
>
>> IHMO, there's two possible paths when one wants to generate music
>> expressions (at least, that's what I'm doing in my own scores):
>
> thanks a lot for the answer!!
>
> (soon I'll post the scheme hacks I'v
Hi :)
In case you didn't read my original post:
I am creating a score for a piece of H. Schütz with Lilypond 2.2.5
(with Fink on Mac). When setting this old kind of music it is often
better to not use a standard Choirstaff, but to use the bar lines only
between the bars. As far as I know this is
