KOReader: a document reader for PDF, DJVU, EPUB, FB2, HTML, ... (GPLv3)

[soulafein]

Originally Posted by chrox

Embeded fonts ought to be used by default, with embeded style sheet on. If they are not, probably it's a bug in koreader. But there is also some possibility that the epub file has wrong css definitions. So without the document we just cannot tell.

In Calibre, in MoonReader (Android) epub works with embeded fonts but in Koreader doesn't. I will sent You PM with sample epub

[MaxStirner]

Since -20140210 or 0213 dictionary does not work again

[chrox]

Originally Posted by MaxStirner

Since -20140210 or 0213 dictionary does not work again

Fixed in build 939.

[obyrm]

Since 935 the dictionary function does not work for kindle Now it works with build 939

I also noticed that the build file sizes always differed until the build 935. Now both kindle and kobo editions are same file size

[knc1]

Originally Posted by obyrm

Since 935 the dictionary function does not work for kindle
- - - -

Answered in the post immediately before yours.

[chrox]

Originally Posted by obyrm

Since 935 the dictionary function does not work for kindle

I also noticed that the build file sizes always differed until the build 935. Now both kindle and kobo editions are same file size

It should be fixed in build 939.

It's because them are both compiled with the "gcc-arm-linux" toolchain now. See https://github.com/koreader/koreader...bdf3e35fb8086e

[soulafein]

Originally Posted by chrox

Embeded fonts ought to be used by default, with embeded style sheet on. If they are not, probably it's a bug in koreader. But there is also some possibility that the epub file has wrong css definitions. So without the document we just cannot tell.

Hi chrox. Did you check the sample epub from ebookstore that I send You? What about its font?
Another question:
1. It would be nice if mini progress bar was divided into chapters :-)
2. It would be nice if Koreader had indicator which font is used :-)
BTW Koreader rocks!

[chrox]

Originally Posted by soulafein

Hi chrox. Did you check the sample epub from ebookstore that I send You? What about its font?
Another question:
1. It would be nice if mini progress bar was divided into chapters :-)
2. It would be nice if Koreader had indicator which font is used :-)
BTW Koreader rocks!

It's confirmed a bug in koreader when handling "font-family" property of the css. I simply edited the

body
{
	font-family: AmerigoPL;
	line-height: 1.2;
	margin: 0 15px;
}

into

body
{
	font-family: AmerigoPL, serif;
	line-height: 1.2;
	margin: 0 15px;
}

. And the problem seems solved. An screenshot on the final rendering in koreader compared with E-book Viewer from Calibre.

[soulafein]

Originally Posted by chrox

It's confirmed a bug in koreader when handling "font-family" property of the css. I simply edited the

body
{
	font-family: AmerigoPL;
	line-height: 1.2;
	margin: 0 15px;
}

into

body
{
	font-family: AmerigoPL, serif;
	line-height: 1.2;
	margin: 0 15px;
}

. And the problem seems solved. An screenshot on the final rendering in koreader compared with E-book Viewer from Calibre.

Attachment 119197

Now it works like a charm ! Thank you Simple and effective

[chrox]

Originally Posted by soulafein

Now it works like a charm ! Thank you Simple and effective

Now the "no default generic-family" bug is fixed in koreader, and with the next nightly build you can read this document without any modification of the css. See https://github.com/koreader/crengine...3fa3ffa6e535ea

[pkbo]

chrox, will your fix work properly if I will specify font-family: AmerigoPL, sans-serif ? I guess no, because you've set 'n' to 1, the following code will never be executed:

if (n==-1 && nn!=-1)
{
    n = nn;
}

right?

[zamana]

Hi!

I know that Kindle can open MOBI files natively, but is there a way to force mobi files to be opened by KOReader?

Thanks.
Regards.

[chrox]

Originally Posted by pkbo

chrox, will your fix work properly if I will specify font-family: AmerigoPL, sans-serif ? I guess no, because you've set 'n' to 1, the following code will never be executed:

if (n==-1 && nn!=-1)
{
    n = nn;
}

right?

Oops, may be it's better to patch it like this:

if (nn!=-1)
{
    n = nn;
    // remove family name from font list
    list.erase( i, 1 );
}

though I haven't tested it yet.

[chrox]

Originally Posted by zamana

Hi!

I know that Kindle can open MOBI files natively, but is there a way to force mobi files to be opened by KOReader?

Thanks.
Regards.

You can use the KUAL unified aplication launcher, in which koreader is launched as a file manager that will show all supported formats including MOBI.

[pkbo]

Originally Posted by chrox

may be it's better to patch it like this:

It will select the last font family (not the first one, which I think was intention in the initial code) I'm not sure if it is a problem or not, otherwise it looks ok.