MobileRead Forums - View Single Post

kirill · 04-29-2011, 11:39 PM

I had similar problem with Cyrillic fonts on kobo, and they are present on the system! I can open text file with utf8 Cyrillic text and everything is fine, but e-pubs need to be modified to display non-Latin text.

The culprit of this problem is custom .kobo/adobe/pxf/userStyle.css file that nickel/adobe plugin use to overwrite font selection for the whole document body:

Code:

body {
 font: serif;
}

When programs like calibre embed fonts into an e-pub they assume that it is enough to add css style for the body tag, but that change gets lost because of the custom css on Kobo. My solution was to add custom styles for every element present in the document. In my case I add this to the style file:

Code:

p,div,h1,h2,h3,h4,h5,h6
{
font-family: "MyEmbeddedFontName";
}

I have tried to modify .kobo/adobe/pxf/userStyle.css on Kobo, but without success as it gets overwritten on startup.

This is a rather annoying problem, I would say a design bug in the nickel.

04-29-2011, 11:39 PM	#4
kirill Junior Member Posts: 2 Karma: 10 Join Date: Apr 2011 Device: Koboe (1gen)	I had similar problem with Cyrillic fonts on kobo, and they are present on the system! I can open text file with utf8 Cyrillic text and everything is fine, but e-pubs need to be modified to display non-Latin text. The culprit of this problem is custom .kobo/adobe/pxf/userStyle.css file that nickel/adobe plugin use to overwrite font selection for the whole document body: Code: body { font: serif; } When programs like calibre embed fonts into an e-pub they assume that it is enough to add css style for the body tag, but that change gets lost because of the custom css on Kobo. My solution was to add custom styles for every element present in the document. In my case I add this to the style file: Code: p,div,h1,h2,h3,h4,h5,h6 { font-family: "MyEmbeddedFontName"; } I have tried to modify .kobo/adobe/pxf/userStyle.css on Kobo, but without success as it gets overwritten on startup. This is a rather annoying problem, I would say a design bug in the nickel.