[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fwd: Capitalized text
From: |
Jean Abou Samra |
Subject: |
Fwd: Capitalized text |
Date: |
Mon, 28 Jun 2021 12:04:50 +0200 |
(Sorry, sent privately by accident.)
Début du message transféré :
> Expéditeur: Jean Abou Samra <jean@abou-samra.fr>
> Date: 28 juin 2021 12:03:25 UTC+2
> Destinataire: Dan Eble <nine.fierce.ballads@gmail.com>
> Objet: Rép : Capitalized text
>
>
>
>> Le 27 juin 2021 à 21:19, Dan Eble <nine.fierce.ballads@gmail.com> a écrit :
>>
>> I am working on a grob for section labels. I want to recommend that the
>> user encode the section name in title case (Coda), but I want LilyPond to
>> render it in all caps (CODA) by default.
>
>
> Could you elaborate? Isn't setting the label through a property just as
> simple? (I don't have the technical background on your work.)
>
> I vaguely recall Coda in small caps. Is all caps Gould advice?
>
>
>> Is there already a grob property to enable this transformation? I've hacked
>> in a callback that calls string-upcase when my new grob is created, but this
>> seems like a problem that ought to have a general solution.
>>
>> If this is not currently possible, would Text_interface::interpret_string()
>> be the most appropriate place to implement it?
>
> I am not aware of it being implemented. You'd not want to call string-upcase
> on the property directly since that would only work on strings, not any
> markup. text-interface.cc already does string replacements, so uppercasing
> should fit there.
>
> HTH
>
>
>> Thanks,
>> —
>> Dan
>>
>>
- Capitalized text, Dan Eble, 2021/06/27
- Fwd: Capitalized text,
Jean Abou Samra <=