I draw all my ogoneks as integral parts of the base glyph. So can I omit floating ogoneks from the glyph complement, or are there apps out there that need them?
And while I've got the mic: why do some fonts have what seem like duplicate floating accents, like acute and acutecomb?
Thanks!
0
Comments
I have no problem to discourage the use of outline and shadow effects.
But just so I understand: can I omit the floating ogonek, even though Truetype knows how to make use of one?
And Jackson: what's a dead key glyph?
It is useful to realise that in a Unicode+OpenType text environment, the relationship of keystrokes to characters to glyphs is
[n] -> |n| -> /n/
Thanks for all the info, John and others.
Of course you probably don’t want to support those cases with most common fonts.
Exactly. So why anyone would suggest deleting the floating diacritics, is right next to why anyone would think we are here to save time for anyone other than the user. As precious as our time is, it's nothing compared to the time we save them.
Given that most apps and OSes will do fallback fonts if the font does not support the character, I submit that for your users on those apps, you are not even possibly doing them a favor by deliberately omitting combining diacritics, because fallback is going to be much worse than a badly-positioned or badly-joined diacritic.
If a significant portion of your users needing such characters are on apps that just shoot notdefs in such cases (e.g. Adobe creative apps), then it's a different calculus. Would you rather your users get somewhat inferior results with your typeface, or be forced to use a different typeface altogether (or do some difficult workaround)?
You can probably tell from my wording that I am in favor of more functionality when possible, these days. However, it is unfortunate that my current tool of choice (FontLab Studio) does not yet have the relevant mark attachment features, which would make me more inclined to do this. If only I could turn anchors into mark attachment points for arbitrary marks....
http://www.glyphsapp.com/tutorials/mark-to-base-positioning/
http://www.glyphsapp.com/tutorials/mark-to-mark-positioning/