View Single Post
Old 05-21-2013, 03:32 PM   #13
st_albert
Guru
st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'
 
Posts: 698
Karma: 150000
Join Date: Feb 2010
Device: none
@Aethyr:

This info is based on ID4, but more recent versions should have similar controls.

For starters, when you export to digital editions (epub) uncheck the box for exporting embedded fonts. (I think this is on the first panel that comes up after you hit "save" for the epub export.) ID will still include font declarations in the css file, but they will be set up as if the fonts are present on the local machine, not embedded in the epub. (For TNR, that'll usually be true anyway.)

That should eliminate the error you were seeing, I think.

Now you can either leave things as is, and provide a fallback font for the css (e.g. serif); or you can locate a TNR-look-alike that is freely sharable, and embed that using Sigil (and adapting the font declarations to suit).

And still, some reading devices will probably ignore embedded fonts anyway.

HTH
st_albert is offline   Reply With Quote