KOReader Forum

[jonnyl]

I pronounce it co-reader. I guess you could also say "K.O. Reader." But that doesn't roll off the tongue as easily.

[Frenzie]

To me it's koreader (or co-reader if you find that clearer).

At first it was written KoReader, which pronunciation-wise seems clearer to me, but then it was changed to KOReader because apparently KoReader suggested a pronunciation like Korea to some. Which is a "problem" if you say kuh-ree-uh but not if you say koh-ree-uh.

I find kuh-READer a bit implausible as a reading for koreader myself, but perhaps as a native speaker of Dutch I have a stronger initial stress bias than English speakers. Or maybe it's non-native English speakers of non-Germanic origin who actually have the stress issue.

For historical context:
https://github.com/koreader/koreader/pull/25
https://github.com/koreader/kindlepdfviewer/issues/782

[Strrav]

Hello
Is there a new Koreader version working with the new kobo Firmware 4.40.23081 ?
Thanks

I reply too myself : yes ! It works

[jonnyl]

Are there any reports of it not working? Honest question, because I'm not aware of any Kobo firmware updates ever breaking KOReader compatibility (but I could be wrong and anyone please correct me if I am).

[mergen3107]

I got the impression that people still confuse it when FW updates itself.
KFMon (which is default launcher for KOReader) breaks after any update, so you need to reinstall it.

NickelMenu, which survives updates, is somehow not the default.

So people think that a specific FW broke KOReader, but that’s not true

[Frenzie]

Originally Posted by jonnyl

Are there any reports of it not working? Honest question, because I'm not aware of any Kobo firmware updates ever breaking KOReader compatibility (but I could be wrong and anyone please correct me if I am).

It can and has happened. Granted, it depends a bit on how you define "KOReader". Something like 3.18 (?) broke part of the startup script (not KSM but the script called by KSM, shipped as part of KOReader) that prepares the environment before starting KOReader proper.

If you mainly use KOReader/Plato/coolreader I'd disable automatic firmware updates. Not for the chance of them actually breaking since the kernel interfaces remain the same, but for the annoyance of having to restore KFMon.

[mergen3107]

@Frenzie
Do you know why NickelMenu option to run KOReader isn’t the default?
Does have any drawbacks compared to KFMon?

[Frenzie]

If you're saying that would generally survive firmware updates I'd say that's a very good question.

[DNSB]

NickelMenu will survive a firmware update. Since I use NM for quite a few tasks, I simply use NM to launch KOReader and Plato.

Heck, the OCP package installer default launch for KOReader using KFMon uses NM to do the launch without having to locate the .png file. Ditto for Plato.

menu_item : main : KOReader : kfmon     : koreader.png
menu_item : main : Plato    : kfmon     : plato.png