View Single Post
Old 05-23-2011, 05:39 PM   #30
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,254
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by rkomar View Post
I've been reading up on CSS @font-face, and apparently you should be able to use something like:

Code:
src: local("Lexia DaMa")
to tell it to find the font locally rather than specifying an exact path via a url. Hooray! CSS has a reasonable way of handling this! Unfortunately, AdobeViewer.app seems to ignore the /mnt/ext1/system/fonts/ directory when searching locally, too, so this doesn't help in our case. I guess I shouldn't be surprized, because if it worked, just adding the font name to the font-family: list would probably have worked, too. So, embedding the font in the book seems to be the only system-agnostic way to use new fonts with AdobeViewer on the PB devices. I'll submit this as an AdobeViewer bug, and maybe something will happen about it.
I see you are a programmer. I'm not sure whether you ever read this old thread but it contains the simple detail of the original AdobeViewer hack, along with the difficulty of repeating it in the more recent firmware versions.

If you have any ideas of how to re-hack I, for one, would be very pleased
jackie_w is offline   Reply With Quote