Quote:
Originally Posted by ShellShock
In 3.3. the location of the userStyle.css in FskDocumentViewerAdobe.dll has been changed to res:///userStyle.cs, which on my O/S equates to C:\Program Files (x86)\Sony\Reader\Data\bin (the same directory as FskDocumentViewerAdobe.dll). However, if I put userStyle.css in there it has no effect. Using Process Monitor, I can't see that the Reader Library.exe ever tries to load userStyle.css. It is almost as though this "feature" has been disabled by Adobe.
|
It is even worse than I thought. 3.3 also ignores font specifications within the .css in the epub itself, and not just the external userStyle.css. For example, if my epub .css has this:
@font-face { font-family: "Fontin"; font-weight: normal; font-style: normal; font-variant: normal; src: url(res:///Data/fonts/Fontin-Regular.ttf); }
The
res:///Data/fonts/Fontin-Regular.ttf should equate to
C:\Program Files (x86)\Sony\Reader\Data\bin\Data\fonts, but it seems to have no effect. This works in 3.2, and also works in the new devices (e.g., 350 as described here
https://www.mobileread.com/forums/showthread.php?t=98618).
Process Monitor shows that 3.3 never tries to read the external font files. So it seems the only way to change the font used is to actually embed the font within the epub.
I think this really a bug, and not just a feature that has been deliberately removed.