View Single Post
Old 10-05-2010, 02:19 PM   #11
charleski
Wizard
charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.charleski ought to be getting tired of karma fortunes by now.
 
Posts: 1,196
Karma: 1281258
Join Date: Sep 2009
Device: PRS-505
Quote:
Originally Posted by jharker View Post
Actually, it's perfectly possible to embed fonts in iBooks.
Quote:
Originally Posted by frabjous View Post
This surprises me. When the iPad was first released, I made an ePub with an embedded SVG font to see if it would work (since I knew mobile Safari supported SVG fonts), and had someone test it, and it didn't work.

See here (post #15)

Did I do something wrong there?
He's using the <cite> hack.

Apple's approach is idiotic and stubborn, but it's quite clear: they don't want book designers to have any control over the fonts, they don't even want them to be able to specify which inbuilt font is used. Some of the loopholes that existed have been closed off, and the <cite> loophole will probably be 'fixed' in a future version.

It would be unwise to rely on a hack for something that's essential to your book. The only robust option that won't break in a future version would be to render the characters or symbols that you need as individual pieces of svg and embed those inline with the text.
charleski is offline   Reply With Quote