Now that I am setting up a new environment on a new machine,
I am running into a problem again,
and I don't recall how I solved it last time.
When I compile a pdf locally, it looks fine.
But when I upload it to a site, then download it on an iPad, it shows
different fonts.
Is there a way to eith
Hi;
I have a piece of music from which I am engraving that confuses me.
At bar #13 there is the Segno sign.
At the end of bar #20 there is a "Fine".
At the end of the piece (bar #37) there is a "D.S. al Fine".
I'd like to have Lilypond generate midi output that would match this inten
Hi Kieren,
In my main include file, I have the following definition:
strut = \markup \transparent { Tj }
Then, in markups, I use
\combine $text \strut
to guarantee a consistent height/spacing.
One could do something like this:
\version "2.22"
#(define (squash-stencil-X stil)
Thanks Valentin!
Rachel
> On Jan 21, 2022, at 10:31 AM, Valentin Petzel wrote:
>
> Hello Rachel,
>
> The reason why offsetting the X-offset value does not work is because it is
> not
> used for placing Breathing marks. You can see from the output that the offset
> command fails, as no offset
Jean Abou Samra writes:
> Le 21/01/2022 à 08:57, Bernhard Fisseni a écrit :
>> Good morning,
>>
>> Consequence: There is no collision between an auxiliary function
>> CMD and a homonymous markup command \CMD, as they are (CMD ...) and
>> (make-CMD-markup ...), respectively, in scheme.
>
>
> Yes
Hi Valentin,
repeats in NNS are specified with standard repeat signs, displayed
inline, and volta brackets above in case of an \alternative {{}{}}.
Repeats of 2nd order are displayed with segno and coda sign.
Short repeats can be achieved with percent style.
Cheers,
Amy
On 21.01.22 18:58, V
plans of similar scope, and [I] work on LilyPond as a
hobby in otherwise already LilyPond development
is for me a hobby in already otherwise busy weeks.
Talk about busy weeks...
Le 21/01/2022 à 08:57, Bernhard Fisseni a écrit :
Good morning,
trying to understand the programming a bit better, I managed to
transform the mixed command definitions to scheme code (see below).
I've learnt the following in the process; should some of it be made
more explicit in the manual?
Hi,
Unfortunately, I do not really have the skills to put together a recipe
myself from the templates available (emphasis on "I do not have the
skills").
If others who are interested, who have the skills, would like to take
this on, I am happy to advise and introduce to the Kite Guitar team, who
Hello Rachel,
The reason why offsetting the X-offset value does not work is because it is not
used for placing Breathing marks. You can see from the output that the offset
command fails, as no offset is calculated in the first place.
You can still use something like \tweak extra-offset #' (x-of
Also note that your function, if called with \strut-line { hello world
}, actually adds your invisible strut to every word of the line. (Just
remove the make-transparent-markup in your function to see this, or,
more easuily, remove the #:transparent in my version). Compare:
\markup \strut-l
Hi Bernhard,
unfortunately I don't have much time at the moment (and there's always
the chance that Jean or someone else more knowledgeable than me is
already working on an exhaustive answer), but there's one thing I'd like
to point out:
#(define-markup-command (strut-line layout props line
Good morning,
trying to understand the programming a bit better, I managed to
transform the mixed command definitions to scheme code (see below).
I've learnt the following in the process; should some of it be made more
explicit in the manual? (If so, I could try to think of suggestions.)
-
Hello again,
I haven't been able to solve the problem yet, but I did a little bit of
testing. It seems that the issue has something to do with multiple voices;
however, I cannot really pinpoint it.
The issue in my sample code is resolvable by placing more than a few notes
inside parts with multip
14 matches
Mail list logo