Hacked AdobeViewer.app with userstyle1.css

[rkomar]

Originally Posted by EbokJunkie

Hey guys,

Old thread but the idea is still great.

I tried to use this on new Pocketbook Touch with unhacked (original) AdobeViewer.
Touch has blank UserStyle.css in /system/fonts/adobe.
File looks as just a placeholder, any attempt to fill it with content winds up with automatic overwriting it by the same blank file (just body{}).
So I made this file read-only, filled it with Tselling's suggested content, and copied fonts to system/fonts.
Interesting that AdobeViewer in Touch is affected by changes made to css file (I set very large left margin and this worked).
However, font stays unaffected.
Maybe someone has Touch and can figure out why this happens?
Could be that path to fonts changed or Linux mount changed name for Touch?

I believe that fonts embedded in the ebook have precedence in AdobeViewer, no matter what is in UserStyle.css or which version of the program. I've read elsewhere in this forum that if you want to control the fonts used, you have to strip out the ones embedded in the ebook. Maybe that is why you can't change the fonts.

[jackie_w]

@EbokJunkie,

I don't know about the newer PB models but this userStyle1.css gives me my chosen font (Charis) on my PB360 (original) with the hacked ADE version of fw15.2, even if there is a different embedded font.

@font-face {font-family: serif; font-weight: normal; font-style: normal; src: url(res:///mnt/ext1/system/fonts/CharisSIL-Regular.ttf)}
@font-face {font-family: serif; font-weight: normal; font-style: italic; src: url(res:///mnt/ext1/system/fonts/CharisSIL-Italic.ttf)}
@font-face {font-family: serif; font-weight: bold; font-style: normal; src: url(res:///mnt/ext1/system/fonts/CharisSIL-Bold.ttf)}
@font-face {font-family: serif; font-weight: bold; font-style: italic; src: url(res:///mnt/ext1/system/fonts/CharisSIL-BoldItalic.ttf)}

body, body.book, body.text, body.calibre, body.calibre1, body.calibre2, body.calibre3, body.calibre4  {
    font-family: serif;
    line-height: 1.2;
    widows: 0; orphans: 0;
    margin-left: 5pt; margin-right: 5pt;
    font-size: 1em
    }

The red bits are important. You can leave out the line-height/widows/orphans/margins/font-size lines if you do not want to override what is already in the epub css.

[EbokJunkie]

Thank you Jackie, your idea about multiple body tags saved my day :-)
One note: on Pocketbook Touch res:/// path doesn't work.I just used path relative to css location: url(./fonts/font_file_name) and that worked for me.