|#601 by [deleted]|
2019-06-19 at 22:52
|Yeah, sorry for getting carried away.|
|#602 by ramaladni|
2019-06-20 at 01:47
|Uhh, right. I guess I'd rather not reply and move the issue along.|
I think that if this feature is added, the team pages should be deleted. So, for example, you'd no longer have Arunaru, the "producer" but Arunaru as a "staff" member. Unless the plan would be to keep both?
At the same time, you'd have to specify releases if there is more than one translation available, and it might get a bit messy. Well, no more than when console ports are involved, I guess.
On that note, it'd be cool if release information could be hidden depending on the language. It'd help clean up certain pages like fault milestone one. Though I'm not sure how easy it'd be to implement.Last modified on 2019-06-20 at 01:47
|#603 by being|
2019-06-20 at 04:06
|Translator (+Editor?) pages should definitely be a part of the database. The translation plays a huge, huge part of your experience with the VN in English. I don't think arguing about good or bad translators, or preferences in translation choices really has anything to do with it. It is simply a valuable thing to include in the database. There are some problems, though. Most notably those fan translation projects that use multiple translators, often starting with one who quits and then gets followed up by another who continues the translation. Some projects has apparently a varied set of translators... It gets really messy, and hard to verify who has even worked on it. Still, despite some potential problems with accuracy in some unusual cases, I think it can only be a positive feature. If someone actually wants to blacklist certain translators then that is their choice. People can easiliy blacklist writers they don't like, too. You can put a positive spin on this, by saying that the user has made a choice that gives them a more positive life experience, rather than reading it negatively by assuming they are going to harass the translator. This is obviously also true for using the feature to wishlist other works by a translator that user like. It's a positive thing for the users, not a negative thing. No matter how I look at it I think it is a good feature and one that I would really like to see.|
|#604 by [deleted]|
2019-06-20 at 04:32
|@602 The current method for adding new translations and other major updates by adding a whole new release entry and leaving the old ones instead of appending to the original release is a huge mess. It's been brought up multiple times before. I don't know what's a practical way to change it within the limitations of the database.|
I think regarding producer entries vs. staff entries for translators, it should be something like:
(I say "translators" in all of my points below for simplicity, but please mentally replace that with "translators and editors.")
- For individual translators who released unofficial patches, they should be listed as both staff and a producer (publisher for the release). This matches how original games released by an individual creator are currently treated (they get a producer entry for the release but are also credited as staff for their specific roles).
- For translation groups who released unofficial patches, the group gets a producer entry listed as publisher on the releases and the individuals, if credited, get staff entries.
- For individual translators who worked on official translations, nothing changes about the publisher credit, but the translators are added as staff entries.
- For translation groups who worked on official translations but aren't part of the company, e.g. SUN-TEAM on r61354, my initial thought was there should be a staff entry for the group, as well as staff entries for individuals if they are credited, and the producer should be removed from the release unless it's credited as a producer on Steam, etc., but now that I think it through that seems unnecessarily complicated... So that's a potential sticking point.Last modified on 2019-06-20 at 04:33
|#605 by eacil|
2019-06-20 at 07:44
|There is a way to sanitize the multi-updated multi-language steam releases. Instead of linking every language to the superseded releases, you keep only the language that was added. Like that, you have two releases for each language: one for when the language was added and one for the up-to-date release. Of course, you have to enforce the addition of a note|
Added [language] support to rXXX.to not confuse the user into believing there were stand alone releases for [language].
Superseded by rXXX.
I doubt those intermediate releases have any other purpose than offering data about new language support dates.Last modified on 2019-06-20 at 07:44
|#606 by hin12|
2019-06-21 at 06:41
|Why are the NES and SNES (FC and SFC) shown as "Famicom" and "Super Nintendo"? Should probably be changed to "Famicom" and "Super Famicom".|
|#607 by dk382|
2019-06-21 at 06:57
|@602 That's more or less what I meant by "more UI customization options." I can see how staff lists could get out of hand when listing even just the key staff involved with official and fan translations of all languages, but this could be helped a lot by having better filtering options, in my opinion.|
|#608 by 707|
2019-07-05 at 07:47
|Can we add original title sub-field for song title (whether on the vocal field or make a new field)? Some VNs are way too unknown that I think the songs cannot be searched for with just a romanisation alone.Last modified on 2019-07-05 at 07:52|
|#609 by raccooncitizen|
2019-07-05 at 10:37
Not sure if this was mentioned before, but is it possible to add a way to filter staff's work? Filtering a writer or a voice actor by removing what you read or put in your wishlist/blacklist (like any other tag).
You must be logged in to reply to this thread.