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

[Markismus]

I personally think that adding "..and new issues (both bugs and enhancements and questions)" to knc1's post is far more interesting than the question whether he personally should be seen as a fan boy or a developer.

[guerrilla]

I asked that because if he's a fanboy I will simply ignore his (unpleasant) posts in this thread, if he's a developer I will avoid to post feature requests and suggestions as they're not welcome.

[knc1]

Originally Posted by guerrilla

I asked that because if he's a fanboy I will simply ignore his (unpleasant) posts in this thread, if he's a developer I will avoid to post feature requests and suggestions as they're not welcome.

Please re-read your own post.

Despite what may have been intended, it was none of those, it was written as a plain and simple criticism.
Not an effective way to communicate your wishes.

[guerrilla]

Originally Posted by knc1

Please re-read your own post.

Despite what may have been intended, it was none of those, it was written as a plain and simple criticism.
Not an effective way to communicate your wishes.

In fact my post was not a feature request and wasn't even addressed to the developers. It was addressed to other users, asking if a feature that I was under the impression that had to be there was working for them.

Please note that in response to your post I simply clarified what I was meaning and that I criticized your attitude only when you used the same tone in response to a polite (and this time unmistakable) feature request from another user.

[hawhill]

Please don't reiterate heated arguments. This thread is long enough already. Feature requests are always nice, though I like to remind everyone that they easily slip away, especially when also using this thread to vent hurt feelings. If you want to keep a feature under developers' scrutiny, feel free to open an issue in github. Of course, discussion among users here is also very welcome.

[guerrilla]

I will obviously comply to your request hawmill but allow me a very last post to say that when you talk about "venting hurt feelings" I feel like you're somewhat diminishing my point.
It's probably my fault, as I took knc1's bait about my previous post. I should have been more straight in stating that it's not his answer to my post at matter here, but his reply to phoenix512's post, which has nothing that can be read as simple criticism.

[gaurmiaur]

Could anyone provide popular manual how to install Koreader to KOBO Touch?

[knc1]

Originally Posted by gaurmiaur

Could anyone provide popular manual how to install Koreader to KOBO Touch?

There is a KOBO forum here, you might get quicker response there.

[guerrilla]

On Kindle PW, koreader tends to freeze more often than not when using certain fonts (e.g. Charis SIL). Unfortunately crash.log is empty.
Is there any precaution I can take to prevent this? Besides not using that font of course, 'cause I really like Charis SIL

[hawhill]

It really shouldn't crash at all. What does "crash" mean? Freeze? Abort/restart? When doing what? Reading documents - of what kind? Epub?

[guerrilla]

I didn't write crash, I wrote freeze
When I select the new font from the menu it just freezes and I have to restart via the hardware button. I noticed this with epubs. The issue happens when selecting that particular font on most documents (and when you restart koreader the document is shown with the previous font, so you could go on forever).
I can't really find a pattern, that's why I was asking. Certain fonts are affected (Charis SIL), most fonts are not (Times New Roman, Georgia, Bookman Old Style, Elegant Garamond, Amasis, Gill Sans, etc.)

[hawhill]

Oh sorry, I didn't read carefully enough. OK, since Charis SIL is an open font, I think I'll give it a try. That might take a few days, however, until I find spare time to do so.

[guerrilla]

It seems that I was having that problem with a couple epubs that are so poorly formatted (no css file, all the styling is done with a style attribute in every damn tag) that there's no even use inquiring further with them.
I've just tried half a dozen ebooks and I can set Charis without any problem now.

So don't waste your time testing the font, it's probably better if I send you an actual ebook to test if I happen to have that issue again.

[guerrilla]

Ok, I realize I'm a major pain in the a##, but I have another question, please don't kill me

I'm reading an ebook (epub) where chapters have no title, they just begin with a paragraph which has a generous top margin. Koreader ignores this top margin, unless I set render style to "clear all external styles", in which case page breaks between chapters are ignored.
The p tag is already wrapped inside a div tag.
Is there any trick to make koreader render the top margin and pag breaks, maybe putting some magic string inside epub.css?
I guess that this is a feature meant to save screen space, but in this case the margin helps me tell that I'm reading a new chapter when the last paragraph of the previous chapter happens to end at the very bottom of the page.

[hawhill]

I guess the way would be fiddling with epub.css, indeed. We just took what came with CoolReader Engine, I think. It's a bit messy and there simply isn't a solution that fits all cases, unfortunately.

That said, CREngine does not properly understand all CSS properties either. It works surprisingly well, though.