A New Edition
|#26 by diabloryuzaki|
2022-08-25 at 18:20
|< report >it seems like if i click japanese only in user -> display preferences -> staff -> click japanese only in box then submit, it will stop to show all edition from other language in default when i open vn main page|
|#27 by beliar|
2022-08-25 at 18:48
|< report >Hm, should image editor be an editor role or a staff? I added them as editors, but it seems other users are adding them as staff.|
|#28 by Marc402|
2022-08-25 at 18:49
|< report >d2#3.1|
Editor: Any text editor who worked during the original production or a translation. Image editors should be added as "staff".Just following the guidelines.
|#29 by beliar|
2022-08-25 at 18:52
|< report >Ah, so all image editors I added to the Amaterasu's translations should be switched to 'staff'.|
|#30 by hansfranz77|
2022-08-25 at 19:09
|< report >Ok looking at these makes it look kinda crammed now with all these staff roles. link |
Maybe more options to collapse only certain staff wouldn't be the worst idea?Last modified on 2022-08-25 at 19:17
|#31 by summer-fog|
2022-08-25 at 21:50
|< report >Thank you for your hard work.|
|#32 by kumiko1|
2022-08-26 at 03:41
|< report >I think we need some kind of official standardisation for edition names, just looking at link we're gonna end up with a lot of edit wars and wildly inconsistent names across the db otherwise.|
|#33 by HataVNI|
2022-08-26 at 04:42
|< report >I have finally been salvated. ILECA SUCK THESE NUTS|
|#34 by rastagong|
2022-08-26 at 12:08
|< report >Thanks to everyone who contributed to this expanded staff feature! |
Super minor stuff, but on the Tsukihime mirror moon translation, I filed people credited with "Additional Translation" under "Translator", but I've been wondering whether it wouldn't make more sense to file them under "Staff" like other minor roles, to distinguish them from main translators who handled most of the text. I assume they must have translated like, UI menus, or very specific features.
I agree with #30 that especially on older fan translations, there can be so many credits (but I suppose that's fine, this is a media database after all). For instance, I haven't added beta testers to the Tsukihime mirror moon TL yet, but here's what we're up against (they're not on credited on the official mirror moon page of the TL, only in the in-game end credits).
None of these are explicit requests/demands, just writing this stuff down for reference!
|#35 by delusionparadox|
2022-08-26 at 23:59
|< report >How should fan patches that feature large amounts of changes, but aren't new translations wholesale, be handled?|
For example, the Robotics;Notes fan patch has changes for one third of all lines in the game. Would we add it as "Committee of Zero's Patch"? And how would we credit the translators, who sometimes made minor changes like in traditional TLC and sometimes had to retranslate lines from scratch?
And for that matter, can minor patches also be added?Last modified on 2022-08-27 at 00:06
|#36 by Ezezin|
2022-08-27 at 00:54
|< report >Call it "Steam Improvement Patch". It's not only a retranslation, but also added/changed some other stuff. After that, add the people involved as always.|
Can you explain what kind of releases you consider "minor patches"?Last modified on 2022-08-27 at 03:02
|#37 by zakamutt|
2022-08-27 at 17:01
|< report >>I filed people credited with "Additional Translation" under "Translator", but I've been wondering whether it wouldn't make more sense to file them under "Staff" like other minor roles|
In a currently released project (demonbane remake tl) I was credited like that. I translated like 8k moji for a specific script, which isn't much, but still a 'real' translation job. This is going to be complicated. Personally I would err on the side of crediting as translator here; they are literally credited for translation in the original after all. This is an opinion based on being on the actual fan tl scene and wanting to document in a style recognizable to fan tl groups though, if you want to invent a new style for vndb I suppose it's hard to argue against it other than say it doesn't match the reality fan tl lives in.
|#38 by beliar|
2022-08-27 at 17:54
|< report >I think I agree that those who did additional translation work should be filed under "Translator".|
|#39 by rastagong|
2022-08-27 at 20:42
|< report >Thank you for your answers! I have no fan TL experience so it's good to hear to about actual people's experience in that area.|
Yeah, sounds for the best to leave such cases under the "translator" role then (esp. since there are limited roles for now, might as well use the translator role to its full extent when it does apply instead of overcrowding the "staff" role). I'll leave the entry as is.
|#40 by marvn|
2022-08-29 at 20:18
|< report >Can non-original editions be set to be collapsed by default somehow?|
|#41 by beliar|
2022-08-29 at 20:31
|< report >In your profile. Deselect everything in the 'staff' menu and only leave the checkbox on "Always expand original edition".|
|#42 by marvn|
2022-08-29 at 20:32
|< report >Thanks!|
|#43 by Draconyan|
2022-09-02 at 15:20
|< report >Now that we can add minor roles I've been thinking: what does the "CG" staff role mean? Does it refers to Event CGs, which makes me think they should be put under "Artist", or are they something else and they should be put under "Staff"?|
I think it's been addressed in a topic somewhere but I can't find it.
|#44 by beliar|
2022-09-02 at 16:56
|< report >It is assumed that CG means 'cg artist', and so it should go under 'artist'.|
|#45 by Ileca|
2022-09-07 at 21:22
|< report >If someone is bored, the individual I was talking about in the other thread is Marcel Weyers. A good chunk of this catalogue needs to be converted into staff.|
|#46 by Ileca|
2022-11-05 at 22:57
|< report >|
But it's so much more fun to put a feature live without telling anyone, and then checking the forums to see how fast people will find/complain about it!If that can reassure you, you are not alone: the dev of EH did the same thing by removing pagination. It's not like he can put it back, because he changed the whole backend with one based on... ID! Meaning you don't have something like ?next_page=2 anymore but instead have ?next=2369591 which is meaningless. You can only jump by dates now. I let you imagine the implications. The bad bad bad implications (such as the inability to guess the volume of galleries between two dates). HE HAS 52 PAGES/1027 COMPLAINTS MADE IN FOUR DAYS ABOUT HIS UPDATE. I immediately thought about the way things are done here and thought to myself, well, that could be way worse, we could be EH lol.
|#47 by Yorhel|
2022-11-06 at 07:26
|< report >Ouch, I feel for him. Pagination on dynamic listings is the bane of backend development - it's where all the server resources end up being spent on and it's totally impossible to optimize (in the general case, at least). The only reason VNDB is safe from this particular issue is that our database is just relatively small.|
|#48 by Ileca|
2022-11-06 at 07:49
|< report >Yes, that's the reason why he did that. According to him, the db is so huge that it would break in one or two years if he keeps the pagination. That's what happen when you allow pixiv and twitter to be uploaded to your db, changing it into a massive dump.|
I thought that you could at least keep pagination for the first 10-20 pages. In my case, while I hate this change (you lose all points of reference), it's interesting to have to change paradigm in the way you use a website.
You must be logged in to reply to this thread.