View Single Post
Old 05-02-2012, 01:31 PM   #205
paulfiera
Addict
paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.paulfiera could sell banana peel slippers to a Deveel.
 
paulfiera's Avatar
 
Posts: 387
Karma: 3102
Join Date: Dec 2010
Location: EU
Device: Kobo Aura ONE, Kobo Libra H20
Quote:
Originally Posted by kovidgoyal View Post
Because unlike most other css rules, @fontface rules apply globally, not via a selector. Therefore they can, in principle, be different for every HTML file.
Many thanks, Kovid.

I may be wrong, but when you have only one css applied to an epub, all these declarations apply to every html/xhtml file. Unless, of course, you have inline declarations, which will have higher specificity.

I'm aware that there can be several css files in a epub - especially in omnibus editions - and that several font declarations may apply to the different titles contained in an epub.

But...when those fonts no longer exist because they have been removed before the conversion, wouldn't it make sense to remove the declarations altogether?

Last edited by paulfiera; 05-02-2012 at 02:06 PM.
paulfiera is offline   Reply With Quote