Quote:
Originally Posted by kartu
denverh
1) Correct
2) Correct
3) To my knowledge, there is no risk to brick reader with such script with CFWs that I know (mine, boroda's or amutin's) since the script does not get executed, if reader is connected to USB during startup. That allows you to recover from errors.
|
I was wondering if plugging the reader in during startup might not be the way to unbrick it, if things went wrong. This is good to know.
Quote:
Originally Posted by kartu
denverh
Now regarding your custom CSS. Shortest way to create such CSS is to take FontsAsInLRF.css and replace the paths to the font files.
You need to mention "font-weight:" when defining font-face only if there are different files for different font weights. I'm not sure if URL must be in quotes or is it optional.
And one important point: if you are using 2.0.11b, there is a bug with the path to CSS files. (will be fixed soon in 2.0.12b) As a workaround you put save your CSS file as /epub/userStyle.css in internal memory.
|
I am using PRS+ 2.0.11b, on a 650. I tried modifying FontsAsInLRF.css as follows, and putting it in .../epub/userStyle.css:
@font-face
{
font-family: sans-serif;
src:url(res:///Data/fonts/WREXHAM_.TTF);
}
@font-face
{
font-family: serif;
src:url(res:///Data/fonts/WREXHAM_.TTF);
}
@font-face
{
font-family: monospace;
src:url(res:///Data/fonts/WREXHAM_.TTF);
}
I picked Wrexham because it will be immediately obvious that the font changed. Anyway, all the books I checked still look the same as before. I also made sure that userStyle.css was picked in the "User EPUB Style" menu. So I'm still having trouble getting this particular option to work. Any suggestions?
Thanks,
Denver
Ah ha! The workaround location for userStyle.css is /epub, not the epub directory in /database/system/PRSPlus.