Set primary/secondary/tertiary/etc languages

[acs87]

I can read in multiple languages and so in my filter chapter languages settings, I set those languages. I do this because of x reason, the chapters aren’t available in English. Maybe cause they stopped translating, group doesn’t allow reuploads to MangaDex or whatever reason. So instead of missing out on some chapters, I add more languages to read them in those languages when they aren’t available in English. But now, I’m getting updates for chapters that I’ve already read in English and are just being translated to other languages. So I propose having ranked language. If I were to set Language A to primary and Language B to secondary, it would show me updates in Language B ONLY IF I haven’t read them in Language A. If there’s a new chapter in Language B but I already read it in Language A, it doesn’t notify me or appear in my follows page. If you want some more clarification, please reply.

 

[Oeconomist]

@acs87—

If this feature could be provided without cost, then it would be unequivocally good.

But it would require a bit of effort on the part of the programmer(s), and would use more computing resources for each instance of someone moving from one chapter to the next, even though most of those users will only be able to read one language.

It seems to me that a better way to serve someone like you would probably be to have the option of an alternative way of moving through a series. Under this alternative, upon completion of a chapter, one might be given a set of choices, which would be each of the translations that were subsequent and nearest in number for their language. (For example, after reading chapter 34 in Urdu by GroupM, you might be offered chapter 35 in Urdu by GroupM, chapter 35 in Urdu by DeathToGroupM, chapter 37 in French by gilets_jaunes, and chapter 93 in English by BloodyPoms) It wouldn't be a smooth as what you propose, but it should make fewer demands on the server.

 

[acs87]

@Oeconomist I believe you may have misunderstood me. What you’re talking about is a separate issue. Let me clarify the issue I had. To check up on any new updates on the mangas I’m currently reading I go to my follows page. There, I see any chapter recently uploaded to the series I’m following, but only the languages I chose in the filters. So if there’s a new update in CHINESE for a chapter I’ve already read in ENGLISH, it appears there anyways cause it’s a new upload. What I’m suggesting is to hide any updates of the same chapter that’s already been read. Say I read chapter 1-22 of a series in ENGLISH and I’m waiting for the next one. Then someone uploads an ITALIAN translation, chapters 1-10. Those won’t show up in my latest updates page cause they are chapters that I already read in ENGLISH. A way to go about this would be to group the translations of one same chapter into one master entry (or something). If the master entry is marked as read, all further uploads if that chapter will remain hidden. About computing resources, I don’t think this will take much computing resources and most probably will be less than the computing resources used in sorting. So I wouldn’t be to worried. We can always donate anyway.

Now I want to talk about the issue you bring up. I have come a cross a few series who’s ENGLISH translation end, but more is available in another language. When you reach the last chapter in the current language, it returns you to the series page. Currently, there a beta option in the reader called recommendations. It shows you a list of recommendations of what to read next. I think this could be taken advantage of and show you some sort of message like “The next chapter is available in RUSSIAN. Continue reading in RUSSIAN?” and show you the next chapter or something. I think that would address your issue.

ps: in terms of programming, I don’t think either of these would be hard to implement.

 

[Oeconomist]

@acs87—

I apologize for misunderstanding your suggestion.

None-the-less, I think that the issue of execution resources still needs to be considered. That cost will persist, regardless of the demands on the programmers.