I agree it's hard to catch up with the current reader.

The approach taken by the https://jnc-reader.wscr.dev/ third party reader is much better for this use case

For errors found in published ebooks it is generally recommended that corrections be sent to support@j-Novel.club

There are various reasons for that but it basically comes down to it will get seen and addressed faster.

It is also important to note that corrections found in the final QC before an ebook is published won’t always be applied to prepub parts on the website, so if the book has been published and you find an error while reading the prepub parts on the site it probably was already caught.

@_08 said in Feature Request: Add a button inside the web to highlight/submit feedback about typos and spelling errors.:

That's a good point because there's a possibility that a big text file is all staff need, making full-fledged bug tracker too excessive. Most of work would be probably needed on the client side anyway, unless you want to discourage readers from submitting errors even more.

No, the goal is to make it as painless as possible for users to submit errors. Sometimes the backend needs to be complex in order for the interface to be simple. There are unique challenges here. I'm not aware of another publishing company collaborating with their customers to help proofread their content. At the same time, I also think it's pretty cool. As J-Novel grows, the problems with the current system will get worse.

An ideal system would eliminate 'noise' while being almost entirely transparent to the J-novel team and customers. it also shouldn't be complicated to integrate seamlessly with the rest of the application.

@chocolatkey

I'll try in landscape- thanks