Robin Bannister writes:
> The non-mapping cases
>\markup \box \concat { "X" "Y" "Z" }
> and
>#(markup #:box #:concat ("X" "Y" "Z"))
> give one box without complaints
>
>
> The mapping case
>\markup \concat \box { "X" "Y" "Z" }
> gives 3 boxes without complaint, but
>#(markup #:con
Am 15.07.19 um 08:12 schrieb Robin Bannister:
It is normal 'automagic' for
\box { "X" "Y" "Z"}
to be mapped into
{ \box "X" \box "Y" \box "Z" }
giving you 3 boxes in a markup list
to which \concat can be applied.
Seems like that magic happens only for LilyPond syntax markups.
The ma
Robin Bannister wrote:
One explanation is that
- concat wants to be given (markup-list?)
- general-align wants to be given (markup?)
So the two should be swapped:
#(markup #:general-align Y UP #:concat ("16" #:teeny "ma"))
This of course implies that your #{ #} version shouldn't
Malte Meyn wrote:
#{ \markup \concat \general-align #Y #UP { "16" \teeny "ma" } #}
works but
(markup #:concat #:general-align Y UP ("16" #:teeny "ma"))
doesn’t and I don’t know why …
One explanation is that
- concat wants to be given (markup-list?)
- general-align wants to
Am 14.07.19 um 16:21 schrieb Robin Bannister:
Malte Meyn wrote:
How can this made be top- or bottom-aligned (or aligned depending
according to the 'direction property)?
Inside a #(define-markup-command (command-name layout props arg1 arg2 …)
you can collect 'direction as follows:
(let*
Am 14.07.19 um 13:15 schrieb Andrew Bernard:
Provide the mechanism, sure, but don't prescribe a single appearance. I
don't even think there is a default that would suit everybody, that's
the point.
Of course I wouldn’t change LilyPond’s default. The markups I showed
would be only an example
Malte Meyn wrote:
How can this made be top- or bottom-aligned (or aligned depending
according to the 'direction property)?
Inside a #(define-markup-command (command-name layout props arg1 arg2 …)
you can collect 'direction as follows:
(let* ((dir-prop (chain-assoc-get 'direction props 1)))
Hi Malte,
Well this is interesting. What you have shown is perfectly normal in
many editions. Some editions line up the dash with the top of the va
abbrev., and some on the baseline, and some in the middle. It's a matter
of personal taste. Trying to force one way of typesetting is not in the
Hi list,
I’m currently working on a patch that would make the default ottavation
texts/markups (currently "8va"/"15ma" and "8vb"/"15mb") changeable by
the user without having to \set Staff.ottavation after each \ottava, see
the following code and attached picture:
%%%