Feature Request: Add a button inside the web to highlight/submit feedback about typos and spelling errors.
-
@myskaros said in Feature Request: Add a button inside the web to highlight/submit feedback about typos and spelling errors.:
@shiny The percent is irrelevant; different font styles and sizes change what page/percent the text is on in the app/website. Also, they just use the Find function anyway. That means you only need the volume and part, which should be easy enough to remember without needing an app function to remember it for you.
If I'm in the middle of reading something I might not know which part I am on. Having to exit and re-enter a part is an unnecessary disincentive to reporting typos
-
@shiny Take a screenshot... if you're on your phone, you have to exit the part to get to the next part anyway, that will remind you which part you were on. At a certain point, this suggestion changes from "this would be generally useful" to "I'm too lazy to put in the effort so you should do it for me."
-
Take a screenshot
Taking a screenshot means I'll need to search in that screenshot later
you have to exit the part to get to the next part anyway
No, I just close the app/put the phone away to return some time later. Or hit the next part button if there's more on this series.
put in the effort
Are you really suggesting readers are supposed to do that?
-
@_08 said in Feature Request: Add a button inside the web to highlight/submit feedback about typos and spelling errors.:
Are you really suggesting readers are supposed to do that?
I'm suggesting that this feature will add minimal benefit to both readers and JNC but add a lot of extra work to JNC.
-
Sorry to unearth a 3 week old thread but I wanted to chime in saying it doesn't even need to be that fancy. Just establish a clear subforum for reporting errors. Right now, as far as I can tell, if you want to report a problem you have to go find the discussion thread for that volume, sift through a bunch of discussion comments to make sure someone hasn't already reported the thing you were going to report, make a new post and hope the translators see it. Having discussion and error reporting all together makes both more cumbersome.
There seem to be plenty of people who want to help in reporting errors (myself included), so I think it'd be great to harness that to make the books more solid and create bigger engagement with the community.
-
I also want to chime in to say that I came to this forum just to post this exact suggestion. If an in-app solution for reporting directly through the app isn't on the radar, if you give me at least the ability to select text and copy to the clipboard the volume, part, and paragraph # (which should be the same regardless of font choices), I'll use it to report the typos and grammatical inconsistencies I find along with paying for premium access...not that there's many at all! I really am always impressed at how advanced the grammatical structure is in J-Novel Club's English translations, which I think could often pass for novels written by professional native English-speaking authors.
-
@rahul-balaggan This is chaos. I can see why some errors end up making it into the final versions when there are pages of discussion about a book with reports of errors mixed in.
I want to read stories, not pages and pages of forum posts to find out whether an error has already been discussed and reported.
A bug tracking system may work better here. Forums are for discussions and bug trackers are for tracking problems. I'm not an author but I would think this would make life easier for the translators as well. There are many systems to choose from, though I'm partial to the features offered by MantisBT. It shouldn't be too much for me to put something together as a demo which could then be transferred to J-Novel's servers.
Users and authors would be able to find and report problems for each series and volume. If any discussion is required, that discussion can be limited to the reported problem. There wouldn't be several different discussions going on within the same forum topic, and the forums can be used for discussion.
-
@wolfpack said in Feature Request: Add a button inside the web to highlight/submit feedback about typos and spelling errors.:
I want to read stories, not pages and pages of forum posts to find out whether an error has already been discussed and reported.
You do not have to read through the entire topic for any series, if you find an error and post it no one will say anything if someone else already posted before.
In fact we have some users like @Terabyte who post their entire list of errors and mention within the list that someone already posted it.
I am not saying you have to do that, and I am not saying you have to report any errors you find at all, all I am saying is that this is the way it is currently done at JNC in regards to error posting.
Sorry but J-Novel Club does not publicly comment on any potential licensing decision or acquisitions.
J-Novel Club, Future Volume Release Schedule
Manga FAQ
Premium Content List -
@rahul-balaggan I don't feel obligated to report errors so that's not the problem. I'm just proposing a cleaner method, which could also be integrated more easily into the app as well if that featured were considered.
It wouldn't be difficult to do and I'm willing to help consult and set up a system for this. I'll even do it for free/cheap. If it doesn't work out there's no loss to the J-Novel team.
-
@wolfpack if you would like to get directly involved in any aspects of JNC on a more business level you should probably email them directly to either,
Jobs@j-novel.club
or
Contact@j-novel.club
-
@wolfpack said in Feature Request: Add a button inside the web to highlight/submit feedback about typos and spelling errors.:
I'm partial to the features offered by MantisBT. It shouldn't be too much for me to put something together as a demo which could then be transferred to J-Novel's servers.
To make something work in J-Novel, you would need to make it work with existing user credentials, which is managed by NodeBB, which is node.js based system. I don't know how exactly J-Novel site is implemented, but I would assume they are implemented as NodeBB plugins, which would be the most natural way to do. MantisBT is PHP based system which would be odd ball in their environment and would be very difficult to integrate.
EDIT
So, if you want to demonstrate something, I would suggest put something together as NodeBB plugin.
-
@hiroto said in Feature Request: Add a button inside the web to highlight/submit feedback about typos and spelling errors.:
NodeBB
Good info - I'll start researching. It would definitely need to be able to integrate with the existing system.
Being PHP based doesn't mean it can't - it just becomes a matter of reviewing available features, future maintenance requirements, effort required to integrate, etc.
The first challenge is determining interest in such a system to begin with. There's a lot of growth potential for JNC.
I have reached out to the staff to see if there is any interest.
-
NodeBB
Only the forums is on NodeBB. Main site is separate and runs on LoopBack framework. Either way, I don't think there's much need to do integration unless there's a possibility from anonymous spam resulting from lack of authentification when submitting errors.
The first challenge is determining interest in such a system to begin with.
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.
-
@_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.
-
S Shiny referenced this topic on
