Thanks, Martin - that would be a great suggestion except that the numbers
will change depending on the position of the note on the staff, and its
surrounds - even including the direction of the stem. Every time the
symbol appears it will need to be carefully placed by hand, so to speak, to
ensure
Hi,
> Op 2 sep. 2020, om 21:07 heeft David Kastrup het volgende
> geschreven:
>
> Maurits Lamers writes:
>
>> Hi,
>>
>>> convert-ly does text replacements. It is not a full parser. If text
>>> replacements are supposed to work, you need to write your text in a way
>>> that the replacement
David Kastrup writes:
> Maurits Lamers writes:
>
>> Hi,
>>
>>> convert-ly does text replacements. It is not a full parser. If text
>>> replacements are supposed to work, you need to write your text in a way
>>> that the replacement patterns cover. Stuff like putting # on one line
>>> and a co
Maurits Lamers writes:
> Hi,
>
>> convert-ly does text replacements. It is not a full parser. If text
>> replacements are supposed to work, you need to write your text in a way
>> that the replacement patterns cover. Stuff like putting # on one line
>> and a corresponding opening paren on the
Hi,
> convert-ly does text replacements. It is not a full parser. If text
> replacements are supposed to work, you need to write your text in a way
> that the replacement patterns cover. Stuff like putting # on one line
> and a corresponding opening paren on the next line are just too weird
> f
Thank you very much! The 'alignAboveContext' bit did the trick!
Best regards,
Leszek.
On Wed, 2 Sep 2020 at 12:06, Leo Correia de Verdier <
leo.correia.de.verd...@gmail.com> wrote:
> Something like:
>
> \version "2.20.0"
> <<
> \new Staff = "basso" {
> \clef bass c1 }
> \new FiguredBass
Errr... because I don't know enough about Lilypond to distinguish between
an override and a tweak. I just happened to have found a Lilypond score
(admittedly an old one) which uses overrides to place special symbols next
to notes, and I'm doing that because I can see that it works. But if
tweakin
Maurits Lamers writes:
> Hi all,
>
> In order to have my braille generator not have to support Lilypond 2.14 I
> tried to upgrade my music library I am building this braille generator on.
>
> However, because of (a lot of) specific "hacks" on the layout, simply running
> convert-ly on the entir
Alasdair McAndrew writes:
> In my attempt to typeset some early 18th century French music for viola da
> gamba, I'm trying to keep to the original notation as closely as possible.
> Thus I'm using a breath mark to indicate a trill, and a sans-serif x for a
> mordent. So for example, I have
>
> m
Something like:
\version "2.20.0"
<<
\new Staff = "basso" {
\clef bass c1 }
\new FiguredBass \with { alignAboveContext = "basso" }
\figuremode {
<7>2 <6-> }
>>
> 2 sep. 2020 kl. 11:25 skrev Leszek Wroński :
>
> Dear Experts,
>
> I would like to have the figures in my figur
Dear Experts,
I would like to have the figures in my figured bass to be engraved above
the staff. This piece of documentation:
http://lilypond.org/doc/v2.18/Documentation/snippets/contexts-and-engravers
says the following:
"When writing a figured bass, you can place the figures above or below the
Hi all,
In order to have my braille generator not have to support Lilypond 2.14 I tried
to upgrade my music library I am building this braille generator on.
However, because of (a lot of) specific "hacks" on the layout, simply running
convert-ly on the entire library doesn't completely finish t
Oh sorry - you were actually asking about \once \override. SORRY!
there's a huge discussion about the abbreviation of this on the
development list and I had that in mind.
Andrew
Didn't we already have this conversation? You can make an engraver to
do all the French ornaments. The outline is on Scores of Beauty. I can
help you do it if you like. Anything like what you have suggested is a
just a sort of hack. Even though you can force it to work, it is
suboptimal. It ca
14 matches
Mail list logo
