Quote:
Originally Posted by JSWolf
Can I use a font with a longer name that I have in fonts? I would give it a try using ChareInk if I could.
|
Just try replacing
Georgia with
ChareInk in the Replace string. If kobopatch.bat doesn't fail with some kind of 'too long' error message, it will be fine.
One of the great things about kobopatch/nickel patches is that we don't have to do the exact length string matching anymore. It has some tricks to reclaim cosmetic visual whitespace from the CSS without affecting the Kobo's ability to action the CSS.
If you do get a 'too long' error you can add an extra bit to the patch to delete some of the CSS which won't be used on your Kobo, e.g. the Japanese-locale-specific stuff. For example, adding this line would free up some space for this patch if the new font-family name is too long.
Code:
# free some space
- {Find: "#caption[localeName=\"ja\"] {\n font-family: Sans-SerifJP, sans-serif;\n font-style: normal;\n}", Replace: "\n"}
It should be indented with the same number of spaces as in the font-family Find/Replace line.
ETA:
I should add this important general info about customising font-family in the Kobo GUI. It will be particularly relevant to you because you read mainly standard epubs.
After a full reboot the Kobo only has immediate access to a limited number of its built-in fonts, Georgia, Avenir and possibly one or more of the CJK fonts. The rest of its built-in fonts and all your custom fonts are only loaded "as necessary". I don't know the exact rules, only what I've observed.
After a full reboot I've always found that the following will force the Kobo to access all fonts. You won't have these problems if you only put the Kobo to sleep.
- Open any kepub. It's as easy as that for users who only read kepubs.
- If you open a standard epub and you don't see the custom font you were expecting (in the GUI not the book's text)
- Press the [Aa] font menu button. You don't need to do anything else, just close it again.
- If you still don't see the font, force the Kobo to re-render by paging across a chapter file boundary, then page back again. Or, closing the book and opening a different one might work, too.