View Single Post
Old 10-25-2012, 10:29 PM   #60
EbokJunkie
Zealot
EbokJunkie can differentiate black from dark navy blueEbokJunkie can differentiate black from dark navy blueEbokJunkie can differentiate black from dark navy blueEbokJunkie can differentiate black from dark navy blueEbokJunkie can differentiate black from dark navy blueEbokJunkie can differentiate black from dark navy blueEbokJunkie can differentiate black from dark navy blueEbokJunkie can differentiate black from dark navy blueEbokJunkie can differentiate black from dark navy blueEbokJunkie can differentiate black from dark navy blueEbokJunkie can differentiate black from dark navy blue
 
Posts: 144
Karma: 13245
Join Date: Feb 2009
Location: SoCal
Device: Kindle 3, Kindle PW, Pocketbook 301+, Pocketbook Touch, Sony 950, 350
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?
EbokJunkie is offline   Reply With Quote