Quote:
Originally Posted by Toxaris
One way to check it is via FontForge. Load up the font and look at the info. On one tab it mentions the OS/2 version compatibility. You can also change it there and regenerate the fonts.
|
Took me a while to clue in to what it was you were saying to do!
At first, I thought you meant to go to the FontForge website (which I found) and then "load up" my font there somewhere -- couldn't find anywhere to do so.
Then I realized that it was a proggie that I had to download/install -- which I did.
Took a while to figure out how to use it (it seems like I'm stuck in my C: drive and can't check fonts on any other drive!), and then I checked the "Ruthie" font that I used in that last, "modern" version of my epub.
"Ruthie" would appear to be fine -- at least, under OS/2 it says "2" (which I presume is what it should say).
Then I checked one of the three "olde"-style fonts that I'd used in that late-Middle English text (in that first sample I'd loaded up here in my initial query), and when I load it I get a "warning" that says that I can't have an OS/2 spec set at "0", and when I look at the font info in that OS/2 section it says "Automatic".
In any case, that font (and presumably the other two "olde"-style fonts that I used there, all made by the same type designer) seem to work on the iPad (in iBooks, anyway), so
if I was going to do that version -- for iPad/iBooks only -- well, I guess I'm okay.
(I'm still debating whether to do that version, or just go with graphics for that part for every version).
Code:
I have no idea what it is used for and why there are issues with it if the version is higher. It is just one of those quirks.
I have no idea either! This ebook-creation stuff is getting endlessly more and more complicated! I seem to be downloading and installing software left and right, just to see if things "work". When I started getting into this, I never thought it would be this complicated and problematic. :/