[JSWolf]

Originally Posted by petrjahoda

OK, can you please make a summary of those fixes you need, because that first post is a mess, things we discussed, some are repeating over and over again, so I am lost in what you want to solve now.
Can you please make a simple list?

Yes, I'll go through the list and simplify it. I'll do so this weekend. If I can get the 1.3 version this weekend, I'll use that to see what I think still needs to be fixed.

Also why are those things not a good idea to be in the roadmap?

If you include an ePub editor, that would take up a lot of space. We already have two very good ePub editors (Sigil & calibre) that work well on MacOS. An iPhone is way too small for an ePub editor to work well enough. And it was asked to be on MacOS so it's not for a phone or tablet. Whoever asked can use Sigil and/or calibre.

This is an ePub reader. ePub is not PDF and there are other very good programs available for iOS/iPadOS to handle PDF. Adding PDF support is just adding bloat.

An ePub reader is not going to work on an Apple watch. The watch face is way too small. UI have an Apple watch and I'd never ever want a reading app written for it. Again, a feature that's of no use.

There is already a plugin for Hardcover.app for calibre. So if you have calibre integration, the plugin can get the reading info from there to talk to Hardcover. The problem is that if you add in support for one servfice like Hardocover.app, then you'll have to app in support for all of them (Goodreads. Hardcover.app, Storygraph, LibraryThing, etc.) Als, you would have to keep making changes everything any of those sites change the site. Again, that would add serious bloat.

Many people do not want AI added to their apps. I think more don't want it then do want it. When it was announced that calibre was getting AI added to it, there was an uproar over it until it was announced that the AI did not have to be used or the code even loaded in memory if it's not being used. AI will cause a lot of people to boycott justRead,app. Do you really want that? Plus it's again more bloat.

This app should be a neutral app. If you add Bookstore integration, you'd end up having to add many bookstores. And again, more bloat.

These features are not useful enough and would have a small amount of users for little to no gain. The app does not need to blow up like a balloon with features that are best outside the app. Sure there are features others want that I won't use, but I do see the usefulness of them. These are features I see nothing useful about them.

And as for the line height: please, please, please, really please: if you have publishers style, the line height is set by publisher. If you want to change things in the publishers style, then it does not make sense to have a Publishers Style at all, right? So then you can simply turn it off and set it like you want.

You have the line height incorrect. When the eBook does not specify a line height, then the reading software should be using the font's metadata that specifies the line height. You are doing it with a fixed line height. That does not respect the line height metadata in the font. You have to respect the font's metadata for line height or you ruin publisher style by having a line height that's incorrect. The eBook I am using to test things does not have a line height and the font has a specified small line height in the font's metadata. So you should be reading the metadata and setting the line height based on the metadata.