Hi,
I read this:
https://glyphsapp.com/tutorials/localize-your-font-german-capital-sharp-s
Interesting.
But I thought: why not just put a .case OT feature which substitutes germandbls to Germandbls?
Hi,
I read this:
https://glyphsapp.com/tutorials/localize-your-font-german-capital-sharp-s
Interesting.
But I thought: why not just put a .case OT feature which substitutes germandbls to Germandbls?
Because the case feature is meant for something else.
To elaborate on Georg’s point:
The case
feature usually deals with shapes like parenthesis, brackets, hyphens etc. by shifting them vertically or exchanging them for a version that is better fit to uppercase characters. So in general a unicode character is replaced by a character without one. In the case of germandbls to Germandbls you would be replacing U+00DF
with U+1E9E
, which is not recommended according to the specification.
Thanks for the clarifications @arialcrime, it makes more sense now.
Another thing I noticed: on InDesign when you type for example ‘Straße’ with caps lock activated on the keyboard and with the .calt feature activated, it changes the ß into ẞ as planned. But when you turn ‘Straße’ into all caps using the TT button from InDesign, it switches the ß into SS.
Any ideas how to influence also the all caps button from InDesign?
The “All Caps” button does still the default grammar rule to change ‘ß’ to ‘SS’ for all caps setting. If you like to get the ‘ẞ’, you need to type it yourself.
Only in the Latin composer.
Yes I know, thanks. I was more thinking of the user who might not use the ẞ because of this button… Well, it all depends on the user and the context.