elci said:

This is such an unnecessary effort. I would laugh if it wasn't for the fact that my image folder now is a mess due to manually having to change the names to their Japanese equivalent.

You're the minority, and again, nothing is stopping you from making a BUR to revert this.

Honestly i don't mind debating with others, hell it's interesting to see others' point of view. However you aren't listening to me or anyonelse, which is why i'm now gonna say that this conversation is pointless and you shouldn't bump forum posts just because you don't like some change that happened a couple months ago.

Mysterious_Uploader said:

You're the minority, and again, nothing is stopping you from making a BUR to revert this.

Honestly i don't mind debating with others, hell it's interesting to see others' point of view. However you aren't listening to me or anyonelse, which is why i'm now gonna say that this conversation is pointless and you shouldn't bump forum posts just because you don't like some change that happened a couple months ago.

It's only pointless to you since you're the one having it your way. I would push for a BUR but I don't have the necessary free time to sit through the days of work needed for it all by myself.

You also say I'm not the one listening, yet you're the ones using my aliasing solution as if it only goes one way. Thany --> Shanna works exactly the same as Shanna --> Thany. That also breaks the main argument of not having stable Japanese names to go by, because afaik, we'd still need to decide on a singular Japanese name to make the aliasing work. Thus, the current endeavor bears little fruit.

elci said:

That also breaks the main argument of not having stable Japanese names to go by, because afaik, we'd still need to decide on a singular Japanese name to make the aliasing work. Thus, the current endeavor bears little fruit.

If we'll get official romanizations, i'll be alright with reverting all of this work. But since i doubt we'll get official romanization for minor/side characters, unless we get those too i'd say to keep english tags for consistency.

Multiple tags can be aliased to one target tag, so you're free to alias any alternative romanizations of the Japanese names to the English name in use.

Unless I'm misunderstanding the complaint.

I'm pretty unfamiliar with tagging norm, but why don't you guys just have both language names for the tags?

TNinja said:

I'm pretty unfamiliar with tagging norm, but why don't you guys just have both language names for the tags?

That would mess up any searches with tag counting metatags like fire_emblem chartags:1. Admittedly, there are many accepted tagging practices which do this (within FE, corrin_(fire_emblem) chartags:1 is one example, since properly tagged posts should have an additional character tag specifying which gender of Corrin is/are in the image.) But we try not to do it for pure vanity reasons. You'd also want to have both tags imply each other so that they're all applied to any new posts, which I'm not certain is possible.

Also, it'd resurface the same issue that motivated this tag overhaul of there being divergent romanizations of the "Japanese" names like Marx/Marks/Maakusu, except if we were tagging those as well, we couldn't resolve the issue by either ignoring it or aliasing them all to the English name.

You guys miss a game tag
Fire_emblem_musou -> fire_emblem_warriors

Erogami83 said:

You guys miss a game tag
Fire_emblem_musou -> fire_emblem_warriors

For now, spinoffs are best kept alone. Reason being we're already busy with the main series. After that, we'll see how to move.
Another problem is, FE Warriors is a crossover. Which tagging convention of what series should we use? If we make fire emblem musou -> Fire Emblem Warriors, should we also make zelda musou -> Hyrule Warriors?

This also goes for #FE.

The bulk update request #2074 is active.

create implication byleth_(fire_emblem)_(female) -> byleth_(fire_emblem)
create implication byleth_(fire_emblem)_(male) -> byleth_(fire_emblem)
create implication kana_(fire_emblem)_(female) -> kana_(fire_emblem)
create implication kana_(fire_emblem)_(male) -> kana_(fire_emblem)
create alias effie_(fire_emblem_fates) -> effie_(fire_emblem)
create alias myrrh -> myrrh_(fire_emblem)
mass update myrrh_(cosplay) -> myrrh_(fire_emblem)_(cosplay)

Reason: More tag maintenance. I also swapped Effie and Faye's wikis beforehand.

EDIT: The bulk update request #2074 (forum #158940) has been approved by @Hillside_Moose.

The tag alias effie_(fire_emblem_fates) -> effie_(fire_emblem) has conflicting wiki pages. effie_(fire_emblem) should be updated to include information from effie_(fire_emblem_fates) if necessary.

The bulk update request #2074 (forum #158940) has been approved by @Hillside_Moose.

The tag alias effie_(fire_emblem_fates) -> effie_(fire_emblem) has conflicting wiki pages. effie_(fire_emblem) should be updated to include information from effie_(fire_emblem_fates) if necessary.

Hillside_Moose said:

The bulk update request #2074 is active.

create implication byleth_(fire_emblem)_(female) -> byleth_(fire_emblem)
create implication byleth_(fire_emblem)_(male) -> byleth_(fire_emblem)
create implication kana_(fire_emblem)_(female) -> kana_(fire_emblem)
create implication kana_(fire_emblem)_(male) -> kana_(fire_emblem)
create alias effie_(fire_emblem_fates) -> effie_(fire_emblem)
create alias myrrh -> myrrh_(fire_emblem)
mass update myrrh_(cosplay) -> myrrh_(fire_emblem)_(cosplay)

Reason: More tag maintenance. I also swapped Effie and Faye's wikis beforehand.

EDIT: The bulk update request #2074 (forum #158940) has been approved by @Hillside_Moose.

Wait a second, why remove male/female implications? Byleth is going to have a lot of pictures even if they have a low post count, the game came out not even a month ago), and Kana (son/daughter of the main protagonist) already has a bunch of pictures. I think this distinction is useful, especially for the importance of these characters.

Mysterious_Uploader said:

Wait a second, why remove male/female implications? Byleth is going to have a lot of pictures even if they have a low post count, the game came out not even a month ago), and Kana (son/daughter of the main protagonist) already has a bunch of pictures. I think this distinction is useful, especially for the importance of these characters.

I think you are reading it wrong.

Unbreakable said:

I think you are reading it wrong.

Yup, i just woke up and thought implication = alias. Disregard my previous comment.

7HS said:
Also, it'd resurface the same issue that motivated this tag overhaul of there being divergent romanizations of the "Japanese" names like Marx/Marks/Maakusu, except if we were tagging those as well, we couldn't resolve the issue by either ignoring it or aliasing them all to the English name.

I still fail to see the issue in this. In fact, we went many years with this system and it was never a problem. If more unity is required then simply pick one of the names and roll with it. Marks is the current alias of your example so it clearly doesn't have anything to do with making a decision regarding which one to use.

It's still a much better solution than taking names from Heroes who aren't even consistent with their own translations, and localisations from other games who take unnecessary liberties with their translations that end up butchering the original name to the point of becoming something different entirely. Just because it's localised doesn't make it a gospel that should be seen as an untouchable monolith.

elci said:

Marks is the current alias of your example so it clearly doesn't have anything to do with making a decision regarding which one to use.

Anyone is free to suggest additional aliases to the character tags Danbooru is using from other romanizations that see use, though I imagine it is possible that they'll be asked to provide links as evidence that the romanization is actually used elsewhere on the web (and the bot might retire them in a couple of years if that ceases to be the case.)

This tag implication has been rejected because it was not approved within 60 days.

The tag implication fire_emblem:_genealogy_of_the_holy_war -> fire_emblem has been rejected by @DanbooruBot.

The bulk update request #2102 is active.

Reason: There's a FE:SS minor character called Selena (post #2016157), currently Fates Selena is in selena_(fire_emblem_fates), but it looks like someone took the tag and used it for Selena (japanese name for Severa, FE Awakening).

Added Fire Emblem suffix for all characters that didn't have it

EDIT: The bulk update request #2102 (forum #159549) has been approved by @Hillside_Moose.