Quote:
Originally Posted by AlPe
My [S]two[/S] three cents.
A) Forget about (commercial) embedded font. There are plenty of freely embeddable fonts out there (e.g., under Open Font License or LaTeX Project Public License).
|
i totally agree with you on this one. i would only ever embed fonts with open licences when working on my own projects, but i've spoken to a number of designers who've laid something out a particular way and want it rendered 1:1 (which i try to explain isn't going to happen anyway. another topic).
Quote:
Originally Posted by AlPe
B) Consider NOT to use embedded fonts altogether: many Reading Systems do not offer the user with the option of NOT using the Publisher's default font, and the user gets annoyed.
|
i thought so too, but am starting to think that a lot of popular devices do actually offer embedded font support, although default to device-fonts. i was actually trying to find a comprehensive (or close to comprehensive) list of devices and the level of embedded font support, like not just if the reader supports the @font-face declaration, but actually makes it available for readers to choose them.
Quote:
Originally Posted by AlPe
C) Personally, I use embedded (open) fonts only for titles or when certain special glyphs are needed. (And, BTW, my glyphIgo tool might be useful to minimize them.) |
yeah i noticed your util on the forum a while ago - thanks by the way - but haven't played around with it much. i've used font-squirrel to subset a font for one or 2 special characters in the past, but might try yours out in the future to subset title fonts.