search

w3c / publ-cg

EPUB 3 Community Group Repository
Other
44 stars 16 forks source link

embedding fonts best practices #41

Open RachelComerford opened 6 years ago

RachelComerford commented 6 years ago

From BISG survey

JayPanoz commented 6 years ago

I’m assuming there will be:

  1. legal issues (font licenses);
  2. technical issues e.g.
    • subsetting + obfuscating*;
    • importance of font-stack;
    • performance – if you embed an entire CJK font while you need a few characters, some devices will become borderline unusable.
  3. practical issues e.g.
    • css styles so that it doesn’t completely break the user setting and prevent readers who need it most to change the font;
    • “the monospace exception” as some UAs don’t ship with a monospace font;
    • rendering maybe (?) since there can be a lot of specific issues – platforms don’t render fonts the same, some fonts can become unreadable on some platforms because hinting issues for instance, etc.

* both are required in almost all paid font licenses.

So, definitely more complex than one could expect at first sight.

Do we happen to have foundries and/or font services in the CG? That could help greatly.