I don't get that argument at all. Some characters didn't have their names localized, so it would be inconsistent if we used the dub names? The point is recognizability, if all of the names we use are what appear in the official dubs, then people both inside and outside the YGO fandom are more likely to recognize them, and it would be consistent because changed or not their still all the official names.
The original japanese names are official in the translation of the Yu-Gi-Oh mangas.
The english localization of some character names were mostly exclusive to 4Kids dub and now to some newer games.
If we were to convert all tags to english names (but leaving the ones whose names are unchanged), it would likely leave inconsistencies. For example, at the same time we have Joey Wheeler and Mutou Yuugi, as Yugi's name is unchanged in both versions but written differently, and this would create a inconsistency on how YGO characters are being named. If we change both tags to Joey Wheeler and Yugi Muto, it would look less weird, however, it would create another problem of the character's name to being tagged by how it is written. It will be like the exact same discussion of topic #20172.
From howto:wiki's character wiki guidelines:
- Use correct naming conventions. Characters are tagged in the way they are written in their native languages, thus Kinomoto Sakura, not Sakura Kinomoto. This "original order" policy carries over from tagging into wiki writing as well as translation notes.
Therefore Mutou Yuugi is the correct one by danbooru guidelines. In the end, the best option is to leave all characters with their original names, while the characters that have different names in the english localization of the YGO anime have these alternate names aliased for searchability, in other words, the way things are right now, which I don't see any issues.
This was discussed in topic #17413 as well, where there was the agreement that Yu-Gi-Oh! copyright tags should be aliased to official, worldwide romanization. And evazion's statement in that topic: forum #173506.