Hello,
in Italy it's very common to have a printed score with the very first page
formatted as this image shows:
https://www.stretta-music.com/media/images/712/776712_detail-00.jpg
Basically, it is a sequence of fields, all horizontally centered, following
this order, from top to bottom:
1)
Hello Leonid,
Do \override Staff.TimeSignature.font-size = #-2 (or any other number). If you
want it to apply to all Staves you can also to \overrider Score.etc
Cheers,
Valentin
Am Dienstag, 23. November 2021, 01:40:13 CET schrieb Leonid Hrabovsky:
> Hi everyone, who may instruct me on how to
Hi everyone, who may instruct me on how to reduce the size of
timesig.neomensural94 grob (Notation pg. 454) if it is possible?
*Леонід - Leonid*
Hello Jean,
About the difference in horizontal skylines:
As regular accidentals get be parenthesized and cautionary accidentals can be
unparenthesized I think it is still legitimate to let behave
AccidentalCautionary behave the same way. According to the source flats and
double flats get a bit
Hello Harm,
I tested it with 2.19.45 version, this is why I added "(at least)" in my
previous post. I don't know if the same behavior occurs in older versions...
Second, comparing the two NoteColumns in your example I notice a
> different positioning of the accent in y-axis direction, but no
>
Am Mo., 22. Nov. 2021 um 23:29 Uhr schrieb Paolo Prete :
>
> Hello,
>
> Please, have a look at this:
>
> { c'''!-> s c'''?-> }
>
> From (at least) 2.19.45 on it adds an unwanted space between the cautionary
> accidental and the ">" script. Any Idea of how to fix this without tweaking?
>
> Thanks!
Great! Thanks!
On Tue, Nov 23, 2021 at 12:05 AM Valentin Petzel wrote:
> Accidental and AccidentalCautionary grob definitions differ in three ways,
> the Accidental grob has these three additional properties:
>
> (extra-spacing-width . (-0.2 . 0.0))
> (horizontal-skylines .
Hello Jean,
I’m working on submitting a patch. Should I add a regtest for this issue? If
so, does it suffice to create a new regtest ly file for this?
Valentin
Am Dienstag, 23. November 2021, 00:33:09 CET schrieb Jean Abou Samra:
> Le 23/11/2021 à 00:05, Valentin Petzel a écrit :
> >
Le 23/11/2021 à 00:05, Valentin Petzel a écrit :
Accidental and AccidentalCautionary grob definitions differ in three ways, the
Accidental grob has these three additional properties:
(extra-spacing-width . (-0.2 . 0.0))
(horizontal-skylines . ,(ly:make-unpure-pure-container
Hello Paolo,
If you want to do this for any font you’ll have no other option but to
basically do what font-config does, and that is to try to estimate how distant
two font names are. I would be very useful if we could get font-config to give
us the actual distance.
Cheers,
Valentin
Am
Hello Valentin,
>From what I understand, your procedure relies on the convention that the
name of the font file has to be very similar to the descriptive name of the
font; unfortunately, this adds unsafety to the procedure I wrote before
(which is already unsafe), even if it shortens that
> On 22 Nov 2021, at 23:31, Valentin Petzel wrote:
>
> Hello Paolo,
>
> This behaviour actually comes from font-config and not from Lilypond. It is
> somewhat sensible, since we want to be able to specify a font intuitively and
> not by some set identifier.
Somewhat sensible… but someone
Accidental and AccidentalCautionary grob definitions differ in three ways, the
Accidental grob has these three additional properties:
(extra-spacing-width . (-0.2 . 0.0))
(horizontal-skylines . ,(ly:make-unpure-pure-container
ly:accidental-interface::horizontal-skylines))
(vertical-skylines .
Hello Paolo,
This behaviour actually comes from font-config and not from Lilypond. It is
somewhat sensible, since we want to be able to specify a font intuitively and
not by some set identifier.
One hacky way to get what you want if you are checking for very specific fonts
could be this,
Hello,
Please, have a look at this:
{ c'''!-> s c'''?-> }
>From (at least) 2.19.45 on it adds an unwanted space between the cautionary
accidental and the ">" script. Any Idea of how to fix this without tweaking?
Thanks!
P
Hello Valentin,
I looked at the src code as well. I don't see an easy way to by-pass the
problem, given that
ly:font-config-get-font-file is bound to a C++ code that can't be
dynamically overridden. In addition, The procedure explained in
On 2021-11-22 11:24 am, Rajesh Baskar wrote:
I had another question. The MeasureCounter boxify function does not
work if we change the staff to Rhythmic staff.
You need to scope the grob to the appropriate context. \boxifying
something within Staff only affects Staff. If you need it to work
From: lilypond-user
on behalf of Rajesh Baskar
Date: Monday, November 22, 2021 at 12:45 PM
To: Aaron Hill
Cc: "lilypond-user@gnu.org"
Subject: Re: Box around MeasureCounter
Aaron,
I had another question. The MeasureCounter boxify function does not work if we
change the staff to Rhythmic
Aaron,
I had another question. The MeasureCounter boxify function does not work
if we change the staff to Rhythmic staff.
\version "2.22.0"
boxify =
#(define-music-function
(grob-path) (key-list?)
(define proc (grob-transformer 'stencil
(lambda (grob orig) (grob-interpret-markup grob
Thanks Jean!
JM
> Le 22 nov. 2021 à 14:13, Jean Abou Samra a écrit :
>
> Le 22/11/2021 à 14:01, Jacques Menu a écrit :
>> Hello folks,
>>
>> I can’t find the list of all possible values for DynamicTextSpanner.style in
>> the LP internals reference.
>> Where is it to be found?
>>
>> Thanks!
Le 22/11/2021 à 14:01, Jacques Menu a écrit :
Hello folks,
I can’t find the list of all possible values for DynamicTextSpanner.style in
the LP internals reference.
Where is it to be found?
Thanks!
JM
Hi Jacques,
Possible styles are usually documented in interfaces. In this case, it's
in
Hello folks,
I can’t find the list of all possible values for DynamicTextSpanner.style in
the LP internals reference.
Where is it to be found?
Thanks!
JM
22 matches
Mail list logo
