Version 4.5 sent to AppStore (KOReader sync, small updates)

[petrjahoda]

■ New features
- Sync with KOReader & Kobo. Your reading position follows you between justread and any e-reader running KOReader, a Kobo included, in both directions. Connect the official KOReader sync server, your own, or a Grimmory library in Settings > KOReader, and the page you stopped on is waiting on the other device. Opening a book asks before it jumps, or jumps by itself if you prefer. The Help Center walks through every route step by step, from installing KOReader to picking a server.
- Add-books menu. The + button in the Library opens a menu: Import from Files, Get Free Books, and Calibre Books whenever your server can be reached.

■ Improvements
- Read Aloud keeps the spoken word in the middle of the screen in scroll mode, instead of snapping every sentence to the top: youtube
- Page counts are computed the way Calibre does it, so a book is the same length here as in the Pages column of your Calibre library. Every book is recounted once after the update.
- Hiding the goal card on Home also hides the streak-at-risk banner and the finish confetti.
- Filters now stay on the device that set them, so a filter on the iPhone no longer shrinks the library on the iPad.

■ Fixes
- A damaged EPUB or comic file no longer crashes the app when it is opened or when its cover is read.
- A neural Read Aloud voice that fails part way through preparing a book no longer freezes the app.
- The reader's close and rotate buttons follow the book's colors on iOS 18, so a dark book on a light-mode device no longer hides them.

■ Localization
- All the new text is natively translated across all 18 supported languages.

[culytera]

- Is there a way to delete multiple books at once through Select? I only see the options to set them as Read, Unread, or to add them to a Collection.

- The page number on the bottom left never seems to reach the actual last page, I was expecting a 5/5 when I reach the bottom of the epub but it still shows 4/5.

- Odd behavior regarding progress calculation:

1. Get to the bottom of the epub, close the file, book should be marked as finished (expected behavior)
2. Mark that same book as unfinished, open it again, scroll up a bit and close the file
3. Book will still get marked as finished and progress is set to 100% even though I didn't close the book at the bottom of the last page
4. If I mark it as unfinished it'll show its true progress percentage of 79%.
5. If I reopen the book then close it without scrolling, it gets marked as finished and progress is shown as 100%.

I've also noticed this behavior when I go to the second to the last chapter of an epub and close the reader. The book gets marked as finished despite my progress being at 92% when I mark it as unfinished.

The only time I expect a book to get marked as finished is when I actually scroll down to the bottom of the book.

[petrjahoda]

Hi Culytera
1. deletion, good idea, going to the to-do list
2. Page + mark as finished, will look into it, thank you for the detailed description

Just a question: in your examples, are you still talking about book that has 5 pages? Even with those 79% example?

[culytera]

Originally Posted by petrjahoda

Just a question: in your examples, are you still talking about book that has 5 pages? Even with those 79% example?

Ah yes, that's for the 5 pages book. With a book that has 61 pages for example, the mark as finished issue gets triggered at 92%. A book with 131 pages gets marked as finished when progress is at 86%.

[petrjahoda]

Originally Posted by culytera

Ah yes, that's for the 5 pages book. With a book that has 61 pages for example, the mark as finished issue gets triggered at 92%. A book with 131 pages gets marked as finished when progress is at 86%.

This is going up the list because I am not seeing anything like this in my reading.

If anyone else is reading this: do you please experience the same?

[petrjahoda]

This is really strange, I have tested it right now with multiple books I did not read yet, 160 pages, 102 pages, 91 pages and the book gets finished whenever I get to the end (99% as that was the request in some previous posts here, to mark it not at 100%, but sooner).
Can you please send me those two files, 61 pages and 131 pages?

[petrjahoda]

As I am thinking about, the problem can be in paging.
Say I have a book with 5 calculated pages (as Calibre is doing)
When I select a BIIIG size for font, those 5 calculated pages can spread to maybe 20 pages you are swiping on device, showing 1/5 if you are on start.
Or you can select a smaaaaal size for font and those 5 calculated pages will be shown on a half of one device screen, showing 1/5 and get marked as finished.

The same goes for scrolling.

But I will look into it, you described it perfectly, but the files will help :-).

[petrjahoda]

And it is also different for iphones and ipads.
Say a 5 page book can be say 5 pages on iphone, but only half a page on ipad.

[petrjahoda]

Just out of curiosity I peeked into, how Calibre is doing it.
And Calibre can show me, for example ... page 72.6/85 (85%) and next page is 73.9/85 (87%).
Which is kinda weird for me and I understand, that it is calculated by percentage from total pages. I do not know if this is right or wrong. To me it feels kinda strange.

I already updated that 'finishing' algorithm, but I am keeping that paging as it is now, because pages with decimal numbers feel strange to me.

[culytera]

I can send this test epub that Fanficfare generates. I added additional paragraphs in the last chapter so there's more room for the progress. When at 69% progress (at the very top of the last chapter), closing the book marks it as finished.

My reading device is an iPhone XS Max if that helps.

[petrjahoda]

Thank you very much.
EDIT: tested with your file and after yesterdays change it gets closed only when reaching final page (and nowhere else to go).

[culytera]

Originally Posted by petrjahoda

Thank you very much.
EDIT: tested with your file and after yesterdays change it gets closed only when reaching final page (and nowhere else to go).

That's great to hear! Looking forward to the update whenever that comes.

I have another question, what date metadata does justread use for sorting with Recently Changed? I had to create custom columns in Calibre for progress, start date, and finished date so all books' last_modified metadata got updated. This seems to have affected the grouping under Recently Changed sort so now most books are under "This Week".

I use a plugin called Last Modified to have more control with the modified date of books in Calibre, but obviously this isn't used by justread. Is it somehow possible to use this custom column through justread's Calibre Mapping feature?

EDIT: Though I realize not all metadata gets imported.

[petrjahoda]

Hi, justread uses modified from the file itself (see screenshot from your file).

[culytera]

Originally Posted by petrjahoda

Hi, justread uses modified from the file itself (see screenshot from your file).

Ah that makes sense, I was wondering why changing the last_modified default column through Job Spy didn't affect the order in justread.