Comment on Tag Wrangling Guideline Update: Translated Character Names in Relationship Tags

  1. quicksilver_ink (Guest) Wed 02 Mar 2016 01:56AM UTC

    While I can see that as a rule it's elegant and makes sense... in practice this style of relationship tagging is extremely difficult to parse, especially in a long list of ship tags, and especially if both characters have first and last / first and family names. When it's (Japanese name A/ Japanese name B) | (English name A/English name B), I can tell much more easily which ship it is, regardless of which set of names I'm using. I only need to be able to read one set of names.

    In order to interpret Japanese Name A | English Name A / Japanese Name B | English Name B, I have to either know both sets of names and be proficient in switching between them (since the part of the tag that's easiest to read is English Name A / Japanese Name B), or I have to read all the way through both sets of names to be sure it's the ship I want. It's also much easier for my eye to wander too far if another ship is listed after this one, because then we have

    Japanese Name A | English Name A / Japanese Name B | English Name B Japanese Name A | English Name A / Japanese Name C | English Name C Japanese Name D | English Name D / Japanese Name E | English Name E

    Look at that godsawful mess! The / and | bars now are even harder to distinguish, all the names run together, and at some point I am going to think English Name C and Japanese Name D is one of the ships being tagged. Add in situations where the names in both languages are similar (or worse, both sets of names are in English like like Green | Blue Blue | Green in Pokemon)...

    Comment Actions