[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: „Anonymous” properties, deafening engravers and font features

From: Valentin Petzel
Subject: Re: „Anonymous” properties, deafening engravers and font features
Date: Sat, 20 Nov 2021 14:22:16 +0100

Hello Lukas, hello Jean,

Using details works very well, thank you for that. I’ve appended an example I 
just did for Paolo Prete for overriding properties of different articulation 
types (although it is not limited to that) using this details property.

@Jean: I just don’t want to bother you developers with a feature request if by 
stupidity I request for something that does already exists, like the details 
property Lukas mentioned.

One use case is: We can have scores with multiple time signatures by moving 
some engravers from Score to Staff (or whatever). Now if we have a piece where 
we have a section with mixed time signatures, we might want to kind of switch 
between a Score engraver and a Staff engraver within the music. Of course as 
you said this would just need switching engraver on and off withing music. 
Maybe one could have an engraver property one can set to block the engraver 
from outputting stuff?

About the font-feature thing you’re probably right, I just thought that there 
is no reason to override anything if we do not change anything. Removing font 
features can be useful if we have activated some feature (e.g. by saying 
\override something.font-features #'(smcp)) but then we have one particular 
case where we do not want that feature.


Description: Text Data

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]