CSS files and reading software

[rkomar]

Originally Posted by jackie_w

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

I'll take a look and see if I get any ideas. If the res root directory is in fact '/', then a soft link in /tmp/ pointing to the real userStyle.css file can probably be used to get around the short string length. Any suggestions for a simple userStyle.css file that would immediately show me that it is being used?

[jackie_w]

Originally Posted by rkomar

Any suggestions for a simple userStyle.css file that would immediately show me that it is being used?

How about a one-liner to display the epub in its default monospace font:

body {font-family: monospace}

or all italic:

body {font-style: italic}

Edit: I've also attached a tiny epub with no existing special formatting which should work with either of the above custom css files.

[paola]

Originally Posted by jackie_w

You are correct that the res:///mnt/ext1/system/fonts is specific to PocketBooks. This seemed reasonable as paola's readers both appear to be PBs.

A Sony would need to be res:///Data/....

This is the situation I have myself, Sonys and a PB, and is why hacked firmware (PRSPlus on a Sony) is a better solution for me because the magic css file is a Sony version on both Sonys and a PB version on the PB. The same epub reads equally well on all devices. Horses for courses.

I'm not sure how you'd ever get round the problem that the user-accessible internal memory root is different on each device, res:///Data on a Sony, res:///mnt/ext1 on a PB... and who knows what else on a different reader

sorry fo being such a pain, but while all is well on the PB903, when trying to read any book with Adobereader on the PB360, the font info is ignored! The device must be seeing the CSS file, since the image does scale as expected, but it cannot see the fonts. I have checked that there are no spelling mistakes, that the fonts are there, I have tried variations with "Lexia DaMa", but nothing - I guess the directory specification is res:///mnt/ext1, but for some reason it cannot see the font! and the font is there anyhow, as if I open the file with other viewers I can select the LexiaDaMa
I can survive without of course, but I'd really like to understand what is going wrong!

[jackie_w]

Originally Posted by paola

... but I'd really like to understand what is going wrong!

My offer is still open if you would like to email me an epub which is not working on your PB360.

[paola]

Originally Posted by jackie_w

My offer is still open if you would like to email me an epub which is not working on your PB360.

many thanks jackie - should be in your inbox!

[paola]

ok, with a million thanks to patient Jackie for helping me out - I suspect there many be a bug with the standard Adobeviewer application in FW 15.3, as the font information is ignored. However, the hacked Adobeviewer version does the trick (of course I had to edit the userstyle1.css file by adding the relevant @font-family code for the LexiaDaMa). So (but I have only just tried it), it looks like the Hacked Adobeviewer application works with FW15.3 too - I thought I had read somewhere this was not the case.

EDIT: but of course, with the Hacked version there is no need for the additional userstyle.css file in the root of the system - the css stylefile of the book itself suffice.