From the othert thread in the Apple section

[JSWolf]

I just installed justRead.app and I find a number of issues. I don't think this should have been released just yet. Also, I cannot see a discount on the lifetime price. Also, if we only get a week for the special pricing, then it's not going to work because of the number of issues that need to be fixed before it can be properly tested.

• No hyphenation
• No line height adjustment so I cannot decrease the line height the line height is too large
• Vertical and horizontal margins are incorrectly reversed
• The top/bottom margins are wrong. The bottom margin is OK, but the top margin goes to the top of the screen and the bar on the screen obscures some text. The default T/B margins should have the text before the bar and at the bottom of the screen. So I have extra space at the bottom of the screen because I have to have a top margin to make the text below the bar. I have room for at least two lines (well it would be two lines if the line height was not so large)
• Does not respect the metadata in the font for rendering the lien height by default
• The line height is too large. It should be (by default) using the font's line height metadata
• Aa is where the font size should be found
• Alice in Wonderland is said to have an error at the beginning of the book so it's not rendering something correctly

There is a bug in line height. When I make the line height smaller then in publisher mode, not all lines are the same line height. I have to go to 110% to get the line height the same for the main text.

Click image for larger version Name: IMG_1359.PNG Views: 13 Size: 543.7 KB ID: 221643

Another line height bug is that between 0 and 80%, the line height does not change. I want to make the line height smaller then show in the screen grab, but that's not working.

Another thing that could be changed is Publisher Style. Let us have the overrides with no need for Publisher style. We'll just either have the overrides on or off and if off, the publisher CSS takes control.

And one other thing, if line height is off, let the metadata for the font decide the line height.

Whehn adjusting the brightness, please don't use haptic feedback.

As for the vertical margins, please make then individually adjustable so we can adjust for the top and bottom margins separately. This will solve the problem with the status bar. Also, by default, the top margin should not be so high that text is under the status bar.

• Hyphenation should be on/off irrespective of publisher mode.
• When in publisher mode, the line height is too large because it's not respecting the metadata of the font being used. I'm using ChareInk6SP on my iPhone 15 Pro Max. But you can test this with ChareInk7SP as it has the extract same metadata. ChareInk7SP can be had from the first post at https://www.mobileread.com/forums/sh...d.php?t=184056
• The margins are incorrect. Vertical is up/down and horizontal is left/right.
• When I first installed the app and first opened a book, the margins were very much incorrect. The top margin went all the way to the top of the screen and under the dynamic island so so text was obscured by the dynamic island. The bottom text went right to the progress bar and that was good. But when I had to change the top margin to move the text below the dynamic island, it also raised the bottom margin away from the progress bar and left space that could have included more line(s). This is why the top/bottom margins need to be separated so we can adjust for the dynamic island without changing the bottom margin.

Vertical is up/down. Horizontal is left/right. Top/bottom is top/bottom. It's the top & bottom margins that need to be made separately. Vertical and horizontal will be fine as is when they are corrected.

https://www.vocabulary.com/dictionary/vertical

Vertical describes something that rises straight up from a horizontal line or plane. A telephone pole or a tree can usually be described as vertical in relation to the ground.

https://www.vocabulary.com/dictionary/horizontal

The opposite of vertical, something horizontal is arranged sideways, like a person lying down.

[petrjahoda]

Hi JSWolf, thank you for your post, even I think we discussed it a lot.
Let's tackle it one by one.

Are you really not seeing that lifetime option?

[JSWolf]

Originally Posted by petrjahoda

Hi JSWolf, thank you for your post, even I think we discussed it a lot.
Let's tackle it one by one.

Are you really not seeing that lifetime option?

I just cut/pasted from the other thread. I Didn't edit anything out. That's the problem with starting in one thread and moving to another without all the relevant posts being moved. Anyway, I do see the lifetime option.

What I would like to know before going lifetime is if all of the issue a raised will eventually be fixed.

I've seen the roadmap and some things are not a good idea to be there.

• MacOS ePub Editor
• PDF Support
• Apple Watch Integration
• Hardcover.app Integration
• AI Features
• Bookstore Integration

As for the fixes, can some of the actual errors be fixed before any new feature is added or any feature (that works) tweaked?

This means the first thing (that I know of) would be the line height issues.

Thanks.

[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?

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

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.

[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.

[petrjahoda]

Hi and thank for the response.

1. What do you mean by "if you include epub editor that would take up a lot of space". Where does a macos app take space? justread.app is reading app for ios, editor will be editor for macos. Two different apps.
I never wrote about having an editor in the ios app, or where did you find about this idea?


2. Hardcover: also I did not write anywhere what exactly here I have in mind, so it was surprise for me reading that it makes no sense :-)


3. The same for AI. Here is one example I will include it: when I... for any reason ... do not read a book for a month and then return to it, nowadays I need to reread the last chapter to get into it. And I want AI to make me a summary of that last chapter in this case. Is that really that bad? You think people will boycott justread.app because of this? Even if you can disable it?


4. Bookstore... what do you mean... bookstore? There is no Bookstore in the roadmap.


And about that line height: so please disable the publisher style if you do not want it and set the line height like you want. I do not understand here why is it not possible to do this?

[JSWolf]

Originally Posted by petrjahoda

Hi and thank for the response.

1. What do you mean by "if you include epub editor that would take up a lot of space". Where does a macos app take space? justread.app is reading app for ios, editor will be editor for macos. Two different apps.
I never wrote about having an editor in the ios app, or where did you find about this idea?

In the roadmap. If it's not part of the app, then it should not be in the roadmap. Also, do you think there needs to be another editor besides Sigil and calibre?

[quote]2. Hardcover: also I did not write anywhere what exactly here I have in mind, so it was surprise for me reading that it makes no sense :-)[/qote]

Even if it's just updating the reading position it makes no sense.

3. The same for AI. Here is one example I will include it: when I... for any reason ... do not read a book for a month and then return to it, nowadays I need to reread the last chapter to get into it. And I want AI to make me a summary of that last chapter in this case. Is that really that bad? You think people will boycott justread.app because of this? Even if you can disable it?

It's not just a matter of disabling the AI, it's a matter of if it's disabled, will the code not ever load in memory? And yes, it is that bad. Use the iPhone or iPad's browser to use AI do what you want. The proble is too many people want want app to do everything when that's not really a good idea. AI is best used in a browser.

4. Bookstore... what do you mean... bookstore? There is no Bookstore in the roadmap.

It's under suggested.

[petrjahoda]

Also are you read the descriptions for those items in the roadmap?
Because from your answer I think you are not.

For example about Apple Watch, ...

the description says: Track your heart rate while reading via Apple Watch and Apple Health. Discover how much reading calms you down with detailed heart rate metrics during reading sessions.

and you are writing: 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.

That got me an idea that you are not reading the description for those items in roadmap?

[petrjahoda]

Looks like we are living in different universes :-)
Bookstore is nowhere in roadmap, where do you see it please?

And about that Hardcover integration, you are writing ... Even if it's just updating the reading position it makes no sense.
What updating position are you talking about? I do not understand you here.

[JSWolf]

And about that line height: so please disable the publisher style if you do not want it and set the line height like you want. I do not understand here why is it not possible to do this?

I should not have to disable publisher to get a correct line height. When publisher is set and there is no line height in CSS, the line height should be the same as with Publisher off and line height set to 100%.

And under 100% (with Publisher off), the line height is broken. Some lines are closer together then others. They should all be the same width apart.

And with Publisher on, I should have hyphens if I want them.

[JSWolf]

Originally Posted by petrjahoda

Looks like we are living in different universes :-)
Bookstore is nowhere in roadmap, where do you see it please?

And about that Hardcover integration, you are writing ... Even if it's just updating the reading position it makes no sense.
What updating position are you talking about? I do not understand you here.

I didn't notice that bookstore was under suggested. I just read everything as in the roadmap since it was the roadmap section I was looking at. Same with Hardcover.app.

[petrjahoda]

Originally Posted by JSWolf

And under 100% (with Publisher off), the line height is broken. Some lines are closer together then others. They should all be the same width apart.

Please check also the spacing between paragraphs. You can have spacing for lines and spacing for paragraphs.

[petrjahoda]

Originally Posted by JSWolf

I didn't notice that bookstore was under suggested. I just read everything as in the roadmap since it was the roadmap section I was looking at. Same with Hardcover.app.

Maybe it is Friday and my brain is not operating fully :-) but I do not understand you there.
There is no BookStore in Roadmap. You wrote there is. And now you are writing you didn't notice that bookstore was under suggested?
I am lost here :-)

Also please, 'suggested' in the roadmap are suggestions from users.
Maybe you mistaken BookStore with BookLore, which I even dont know what it is (will look into it deeply], as this is an idea from a user.

[The Old Man]

I’ll jump in, probably to my regret. JSWOLF seems to be asking for a lot o features that, to me, are not needed in an ebook reader. My concern is the basics. How well it displays a book, fonts, size, spacing, book loading, cloud integration, page turning. I’m sure you get the idea.As an example - how do you delete a book from the library?

[petrjahoda]

Hi The Old Man... for now you delete it where it is saved. In that folder.
But no problem adding this feature right into the app. Deleting a book from the app is simple. My question here is: it will also delete the file, because that is where the book is. Do you really want something like this?

As the app has no books 'in it' it shows the books from a folder.