Remember current page number when switching between groups in the reader.

[gearsky]

When reading a chapter that’s been done by two or more groups, sometimes I like to switch between the versions to check out the differences in the versions (sometimes helps me figure out which version to stick with going forward).

Unfortunately, switching between scans while in a chapter sends the user to the first page of the chapter for the scan they switch to. I think it’d be nice to be able to remain on the same page, numerically speaking, when switching. I say “numerically speaking” since of the groups have a different number of pages for the chapter due to credit pages or whatever, then it’d be unreasonable to expect the team to create a framework to figure out how to match the correct pages. Besides, even being off by one or two pages is better than having to start at the beginning each switch.

In terms of implementation, I have no idea how things go on behind the curtain, nor am I really in any sort of place to provide development advice (I’m a tester by trade, not a dev), but I do know that the urls for the chapters include the page number as part of the URL after the identifying number for the chapter (in single-page view, at least), so I know that it’s kept track of somewhere.

Note: I apologize if this has already been suggested, but I’m on mobile rn, and can’t figure out how to search this section of the forum on the mobile layout.

 

[bigtiddyoneesan]

Hey, this is pretty good. I'd like this feature as well.

+1

 

[MrIncognito]

If you need to constantly side-by-side compare, consider opening two tabs.

There's equally valid reasons to want it to not do this, like if it takes about halfway through the chapter for your sneaking suspicion that this translation might be garbage to become a certainty.

In the end, this is also a feature that will just feel bad, as you know 9 times out of 10 it's going to send people to what feels to them like a random page when they switch releases

 

[BzzBzz]

> Remember current page number when switching between groups in the reader.

Looks good in theory, but...

Some groups use no credit page at the beginning of a chapter.
Some groups use 5 credit pages at the beginning of a chapter.
Some groups use 3 credit pages in the middle of a chapter.
Some groups DO merge double pages.
Some groups DO NOT merge double pages.
Some groups remove "previously in the series" or "character introduction" pages at the beginning of a chapter.
Some groups DO NOT remove "previously in the series" or "character introduction" pages at the beginning of a chapter.

How will you sync all these groups?

Edit:
Some groups TL magazine/web chapters.
Some groups wait for tankobon release. Tank chapters may contain extra pages.

 

[bigtiddyoneesan]

Looks good in theory, but...

O shit, this is all true. Serves me right for giving out +1's all willy nilly based on impulse. I'll leave my original comment unedited to repent.

 

[Teasday]

This would be pretty easy to implement as far as technicalities go, but yeah, it would run into various problems just as easily, for frankly questionable benefit and probably more complaints than anything.

 

[sterven]

and can’t figure out how to search this section of the forum on the mobile layout.

you can't best thing to do is to use some google fu and hope you come across a relevant thread.

Oh and before I forget

I apologize if this has already been suggested

if you're unsure about it look at the planned features the general rule of thumb is that if it's not on there it hasn't been mentioned before but make sure you actually read it and not glance at it like some others do.

 

[gearsky]

@MrIncognito Opening two tabs is a lot harder when on Safari on Mobile (especially with an, admittedly unreasonably, large number of tabs open already. I have issues.). And I can tell trash translations pretty quickly. Sometimes, though, there are two groups that have translated the same manga, and have kept going for a while. There can be slight variations in the translations, or maybe in the way they handle typesetting or something. I'd like to be able to compare them to decided which one to stick with, and which one to just mark as "read" to satisfy my semi-compulsive need to have the only unread markers be on chapters I haven't reached yet.

@BzzBzz I don't expect it to sync those groups. I knew going into this request that there was absolutely no way there would be a perfect guaranteed match between versions. I even mention as much much in my post (second paragraph). But a close approximation (by which I mean: anything other than defaulting to page 1) is better than nothing, especially for longer chapters. Besides, some of those examples (namely the magazine/web chapters) are mitigated by the fact that such chapters usually get numbered differently (usually a .1 or .5), and as such wouldn't even have the two groups show up when in the reader.

@sterven I always do check, but if it's not under Planned or Rejected, that doesn't necessarily mean nobody suggested it. I figured it'd be better to be polite about it, and err on the side of caution, while still embracing the thought of "if nobody suggests it, there's a 0% (technically not, since a dev could think of it independently, but still) chance it'll be implemented".


Overall, I've read a lot of manga on this site, and I've encountered surprisingly few situations where two groups that have done the same chapters have page counts that are offset by more than 2, maybe 3 pages, which I honestly consider an acceptable margin for this.
If it would really cause that much of an inconvenience for others, then maybe make it an optional toggle?

 

[Teasday]

@gearsky Option bloat is a thing I'll have to consider, some people get very quickly intimidated by the amount of settings available. I'd prefer not to create yet another option for something this trivial to work around and rarely necessary, even though I do sympathize with the problem since I've ran into it a few times myself.

Basically, I'd need to redesign the settings dialog before I consider implementing this as an option.

 

[gearsky]

@Teasday Fair enough.

It probably shouldn't be the highest of priority of a feature anyway. I've seen the Planned list, and y'all've got quite the slog.