Question for techies re:Hacked AdobeViewer

[jackie_w]

I wonder if someone with Linux knowledge could answer this question?

I believe the Hacked AdobeViewer.app, which allows us to customise fonts for EPUBs, does so with a minor string edit where

res:///adobe/pxf/userStyle.css

is changed to

res:///mnt/ext1/userStyle1.css

i.e file userStyle1.css in the root dir of main memory.

Please correct me if I've got this wrong, but in the new firmware v15.3 it looks as though

res:///adobe/pxf/userStyle.css

has become

res:///userStyle.css

With such a short path/filename, is it ever going to be possible to hack it to one which is user accessible? It's my understanding that you have to keep the number of characters constant.

I really hope I'm wrong

[tselling]

I tried it previously and could not find a way to hack AdobeViewer.app in version 15.3b to use a userstyle.css. The good news is you can use the hacked 15.2 version of AdobeViewer.app with 15.3b firmware.... you can also keep the original one in 15.3b as well should you have a file that doesn't work with the 15.2 version. Just name the hacked 15.2 version AdobeViewer152.app and modifying the extensions.cfg file to include all the versions of the viewers you want in the order of preference you want.

[jackie_w]

Thank you for a speedy response, tselling, and for a suggested workaround.

I'm so disappointed with this decision. Is it a deliberate attempt to close off AdobeViewer? What can be the possible harm in users choosing their own fonts? In fact I wonder why the developers haven't built in the hack as standard. Does no-one at Adobe (and PocketBook???) read the ereader forums. Many Sony-reader users also use a similar hack.

I guess another workaround is to add the contents of userStyle1.css into the css file inside each EPUB either manually or via Calibre. Not difficult to do but not as convenient, and not possible for DRM'd books.

[LoneTech]

It's quite possible they actually already look in a more useful location, such as your profile directory. The string is also long enough to fit /mnt/ext1, although the filename is then only 4 characters - may have to make those .css if it actually looks for information in them (which, incidentally, is not permitted on FAT). There are probably other options too, like putting a symlink in /tmp. I can't tell any of these for sure as I still don't have a pocketbook.

[wallcraft]

Originally Posted by LoneTech

It's quite possible they actually already look in a more useful location, such as your profile directory.

The difference is that previously res: pointed to the root of the filesystem tree ("/"), but now it is pointing somewhere else. There may be a string for that location, which might be /adobe/pxf (say). I agree that it might possibly be a user accessible location, but if so why doesn't PocketBook say so.

[jackie_w]

Thanks for replying, guys. I guess we'll just have to wait and see when/if a final v15.3 turns up.