|
From: | Simon Albrecht |
Subject: | \caps (markup command) |
Date: | Wed, 03 Sep 2014 18:55:21 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.0 |
Hello,following James’ suggestion I now start a series of e-mails concerning the observations I made on reviewing NR A.11, the list of markup commands. First issue: Now, \caps and \smallCaps mean just the same in LilyPond. I find that unusual: normally small caps means that all letters are small capital letters (often, and also in current Lily, with the exception of capital letters staying normal-sized). Caps instead means all letters being normal-sized upper case. See <http://en.wikipedia.org/wiki/Letter_case#Case_styles> for an overview. I think that for the sake of compliance with usual terminology (and to add the possibility of non-hardcoded all-upper-case writing) the meaning of Lily’s \caps command should be changed according to this.
Yours, Simon P.S.Personally, I also find attractive the possibility provided e.g. in OpenType to convert capital letters into small caps separately, thus allowing (1) a mixture with upper case letters converted into small caps and lower case letters staying as they are, and (2) all-small-caps writing without any mixed-case distinction. I found that in the specimen for EB Garamond <https://github.com/georgd/EB-Garamond/blob/master/specimen/Specimen.pdf?raw=true>, p.7, section 2.7, and I think it is very appealing. You may well say that it is rather uncommon, but on the other hand it probably isn’t complicated to implement, so why not?
[Prev in Thread] | Current Thread | [Next in Thread] |