Originally Posted by wallcraft
It can presumably screw up the fallback if there is something wrong with the font. The reason for doing it is that the fallback (the default serif font) isn't very good. By redefining serif you always get Liberation when no font is specified in the body of the ebook. This should not be necessary if the ePub was designed from the start to use an embedded font, but if it is added later it can be hard to get Liberation to to applied uniformly to all the CSS.
Hi there, the comma separated list does give a list of what fonts to use if the 'system' cannot find a particular font. For instance:
In the style.css file you might have:
font-family: "Liberation", Arial, sans-serif;
The above means - if you can't find font family "Liberation" then use Arial. If you cannot find Arial then use any font that is sans-serif.
I believe the use of quotes in such declarations is to handle font family names which have spaces in - e.g.: "Liberation Sans".
Note that the fall back strategy is important for those who are testing their ePub document with embed fonts. If your Windows or Linux system has these fonts installed already, then some ePub readers will use those fonts - SIGIL for instance. In contrast, So you assume that the embed fonts are working. However, when you transfer the ePub document to your eReader, the embed font does not work.
From my experience, Calibre uses the embed font.