There's a few tags that have multiple suffixes or have text that continues past the suffix.

There's a few different variations of what's happening among those tags (with examples):

• name_(source)_(character) - corin_(luvbites)_(character)
• firstname_(nickname)_surname - amaryllis_(amy)_sharmila
• name_(gender)_(source)- surfer_(male)_(bluey)
• or _(source)_(gender) - corrin_(fire_emblem)_(male)
• name_(species/form)_(source) - granite_(horse)_(granitethewolf)
• or _(source)_(species/form) - pepper_(crushpepper)_(skunk_form)

Should these be aliased away to fit in a with a single suffix scheme like most other tags?

dirtyderg said:
There's a few tags that have multiple suffixes or have text that continues past the suffix.

There's a few different variations of what's happening among those tags (with examples):

• name_(source)_(character) - corin_(luvbites)_(character)
• firstname_(nickname)_surname - amaryllis_(amy)_sharmila
• name_(gender)_(source)- surfer_(male)_(bluey)
• or _(source)_(gender) - corrin_(fire_emblem)_(male)
• name_(species/form)_(source) - granite_(horse)_(granitethewolf)
• or _(source)_(species/form) - pepper_(crushpepper)_(skunk_form)

Should these be aliased away to fit in a with a single suffix scheme like most other tags?

Looks like granitethewolf has two completely different characters named granite, so I'd say no for that one.

granite_the_wolf and granite_(horse)_(granitethewolf)

*_(source)_(character) should be reserved for instances where the character shares a name with a non-character in the same source. It'd be pretty rare, but I'm not sure how else to solve the issue of like virginia_(irl)_(character) and virginia_(irl)_(location) (I made this up these are not real tags).

*_(source)_(gender) and the reverse should just be gender_name_(source). These are usually background characters who only have 'names' like Male Shopper or for player characters that can be genderswapped.

Species/form probably shouldn't exist tho.

regsmutt said:
*_(source)_(character) should be reserved for instances where the character shares a name with a non-character in the same source. It'd be pretty rare, but I'm not sure how else to solve the issue of like virginia_(irl)_(character) and virginia_(irl)_(location) (I made this up these are not real tags).

*_(source)_(gender) and the reverse should just be gender_name_(source). These are usually background characters who only have 'names' like Male Shopper or for player characters that can be genderswapped.

Species/form probably shouldn't exist tho.

Unless two different characters from the same source have the same name, and there isn't another more reliable way to distinguish them.

kyiiel said:
Looks like granitethewolf has two completely different characters named granite, so I'd say no for that one.
granite_the_wolf and granite_(horse)_(granitethewolf)

I mean, I'd say granite_the_horse_(granitethewolf) would be a good alternative. Keep the distinction while keeping things to one suffix tag.
Same with other tags, like if (made up tags) randomartist has two characters named Alex, one could be alex_the_dog_(randomartist) and the other alex_the_sheep_(randomartist). Seems a bit easier on the eyes imo. (if that makes sense lol)

regsmutt said:
*_(source)_(character) should be reserved for instances where the character shares a name with a non-character in the same source. It'd be pretty rare, but I'm not sure how else to solve the issue of like virginia_(irl)_(character) and virginia_(irl)_(location) (I made this up these are not real tags).

True, though I'd say there's always a way to get around using a double suffix. Like with your examples, they could just be virginia_(irl) and virginia_(state).

regsmutt said:
*_(source)_(gender) and the reverse should just be gender_name_(source). These are usually background characters who only have 'names' like Male Shopper or for player characters that can be genderswapped.

Species/form probably shouldn't exist tho.

Agree and agree

dirtyderg said:
I mean, I'd say granite_the_horse_(granitethewolf) would be a good alternative. Keep the distinction while keeping things to one suffix tag.
Same with other tags, like if (made up tags) randomartist has two characters named Alex, one could be alex_the_dog_(randomartist) and the other alex_the_sheep_(randomartist). Seems a bit easier on the eyes imo. (if that makes sense lol)

That's definitely better.

All of these do not meet the naming standards for character tags and should be aliased away.
We avoid doing double suffixes (i.e., *_(*)_*) and would almost never include the species or gender in the tag (due to instances of alternate_species and crossgender).

By order of preference and availability, the character tags should be:

• Unique short name (i.e., name).
• E.g., draquarus.
• Unique full name (i.e., forename_surname).
• E.g., marty_mcfly.
• Common name with suffix (i.e., name_(character_owner/copyright)).
• E.g., marty_(back_to_the_future).
• Unique name with species* (i.e., name_the_species).
• E.g., draquarus_the_dragon and draquarus_the_wolf.
• Common name with species and suffix* (i.e., name_the_species_(character_owner)).
• E.g., alvin_the_chipmunk_(chipmunkfan123).
• Fan-made name for unnamed character.
• E.g., nubless.
• Nameless character (i.e., unnamed_character/species/etc._(character_owner)).
• E.g., unnamed_surfer_(bluey) or male_surfer_(bluey).
• Unnamed character
• Unknown character

^{* Not encouraged and only used in very rare/exceptional circumstances, such as character owner having two characters of the same name or using an already established name.}

thegreatwolfgang said:
All of these do not meet the naming standards for character tags and should be aliased away.
We avoid doing double suffixes (i.e., *_(*)_*) and would almost never include the species or gender in the tag (due to instances of alternate_species and crossgender).

Should I just go ahead and make a BUR to alias these all away?

Hm.. Didn't notice this one. What about characters owned by multiple parties? Like ryan_(muskie)_(auzzie) Maybe ryan_(auzzie/muskie), keeping it alphabetical?

Also, characters that are supposedly the same but with reworked designs. jumba_(kazecat) vs jumba_(kazecat)_(original_design)

dirtyderg said:
Should I just go ahead and make a BUR to alias these all away?

If you intend to tackle the entire list of non-compliant character tags, you will need to double-check the sources to ensure that they are the same characters or have any other names and follows the standards I mentioned above.

dirtyderg said:
There's a few different variations of what's happening among those tags (with examples):

• 1) name_(source)_(character) - corin_(luvbites)_(character)
• 2) firstname_(nickname)_surname - amaryllis_(amy)_sharmila
• 3) name_(gender)_(source)- surfer_(male)_(bluey)
• 4) or _(source)_(gender) - corrin_(fire_emblem)_(male)
• 5) name_(species/form)_(source) - granite_(horse)_(granitethewolf)
• 6) or _(source)_(species/form) - pepper_(crushpepper)_(skunk_form)

• 1) Looks like an unnecessary character suffix. Suggest renaming to corin_(luvbites).
• 2) Looks like a unique full name and an unnecessary nickname suffix. Suggest renaming to amaryllis_sharmila or amaryllis_(sakuradlyall).
• 3) Looks like an unnamed but popular background character. Suggest renaming to male_surfer_(bluey) (since there is also another popular background character called surfer_(female)_(bluey), which also needs to be renamed accordingly).
• 4) Looks like an unnecessary gender suffix. Suggest aliasing to corrin_(fire_emblem).
• 5) Looks like one of those exceptional circumstances I mentioned. Suggest renaming to granite_the_horse (since its counterpart is already named granite_the_wolf).
• 6) Looks like an unnecessary species/form suffix. Suggest aliasing to pepper_(crushpepper) (and using alternate_species skunk to differentiate them) or renaming to pepper_the_skunk_(crushpepper).

thegreatwolfgang said:

• 4) Looks like an unnecessary gender suffix. Suggest aliasing to corrin_(fire_emblem).

For that one, I'm looking more at
alias corrin_(fire_emblem)_(male) -> male_corrin_(fire_emblem)
alias corrin_(fire_emblem)_(female) -> female_corrin_(fire_emblem)
As they are the player character in that particular game, with gender customization options. While they're technically the same character, I don't think crossgender would apply here since the gender is defined by the player.
Maybe with an implication to corrin_(file_emblem)

dirtyderg said:
7) Hm.. Didn't notice this one. What about characters owned by multiple parties? Like ryan_(muskie)_(auzzie) Maybe ryan_(auzzie/muskie), keeping it alphabetical?
8) Also, characters that are supposedly the same but with reworked designs. jumba_(kazecat) vs jumba_(kazecat)_(original_design)

• 7) No, we would never do that. I don't think I have seen a character who is co-owned by multiple owners, in that case you'd look for better alternatives to avoid naming both in the tag.
• From what I can see, https://inkbunny.net/Auzzie & https://inkbunny.net/MuskiePup are the same person and the unused muskie_(auzzie) tag points to that as well.
• Suggest renaming to ryan_(auzzie) since that seems to be the new name for the character and the character owner.
• 8) Unnecessary separation. Suggest aliasing to jumba_(kazecat).
• I have seen reworked designs before with characters, but they tend to still keep their old character tags with no new tags being made for their previous iterations.

dirtyderg said:
For that one, I'm looking more at
alias corrin_(fire_emblem)_(male) -> male_corrin_(fire_emblem)
alias corrin_(fire_emblem)_(female) -> female_corrin_(fire_emblem)
As they are the player character in that particular game, with gender customization options. While they're technically the same character, I don't think crossgender would apply here since the gender is defined by the player.
Maybe with an implication to corrin_(file_emblem)

From what I can see from the Fandom wiki page, gender is the the player's choice, so crossgender does not apply here since it could canonically be either.
Since the character designs don't even differ that much, it does not justify a separated male & female tag. You would instead use corrin_(fire_emblem) male and corrin_(fire_emblem) female to differentiate them.

I do not know the official standing on this, but since commander_shepard and female_shepard are a thing and there doesn't seem to be a discussion to consolidate it, I will allow it.

The bulk update request #10004 is pending approval.

Reason: Removing nicknames from within tags

Notes:

• alias george_(yuri)_kuznetsov -> george_kuznetsov : Artist seems to use the name George more than Yuri
• alias menachem_mendel_(menchy)_rappaport -> malcolm_krall : new name taken from ref sheet in post #4862722, I can't find another instance where the name in the tag is used

The bulk update request #10005 is pending approval.

Reason: Clearing out the _(male) and _(female) suffixes

Notes:

• alias toka_(male)_(xtoka_samax) -> toka_tail_(xtoka_samax) - post #2972324 seems to give the male Toka a second name ("He is also Toka (Tail)") though I'm unsure if this is a surname or what exactly it indicates.

Followup BUR will handle any crossgender tags for characters like liam_(genderbend)_(candygurl)

The bulk update request #10006 is pending approval.

Reason: Removing secondary suffixes containing species from character tags

The bulk update request #10007 is pending approval.

Reason: Removing secondary suffixes for alternate appearances such as in-game skins, alternate forms/species

Additionally handles the modeler tag for untied verbeger's gryphon model, since the 'black version' falls under this category

Followup BUR will handle any alternate species tags for characters like pepper_(crushpepper)_(skunk_form)

The bulk update request #10008 is pending approval.

create alias ryan_(muskie)_(auzzie) (62) -> ryan_(auzzie) (0)
create alias corin_(luvbites)_(character) (10) -> corin_(luvbites) (0)
create alias escort_(luvbites)_(character) (6) -> escort_(luvbites) (0)
create alias danny_(lepidusdelsol)_(character) (9) -> danny_(lepidusdelsol) (0)
create alias ao_(sojin_advance)_(character) (3) -> ao_(sojin_advance) (0)
create alias frosty_(fp-mk38)_(character) (2) -> frosty_(fp-mk38) (0)
create alias ghost_(shiloh)_(fawnpawss) (2) -> ghost_(fawnpawss) (0)
create alias diodki666_(artist)_(artist) (1) -> diodki666 (1)
create alias saurian_(warhammer)_text (4) -> saurian_text_(warhammer) (0)
change category saurian_text_(warhammer) (0) -> meta

Reason: Removes unnecessary _(character) suffix from character tags that already contain the artist.

Additionally:

• Handles the 'dual owner' tag for Auzzie's Ryan, as Auzzie seems to be an alternate/updated handle for Muskie
• Removes double _(artist) suffix from diodki666's artist tag
• Moves copyright suffix for warhammer's saurian language to the end, and makes it a meta tag.

The bulk update request #10009 is pending approval.

create alias wuschel_(male)_(wuschelwolf) (7) -> crossgender (69284)
create alias liam_(genderbend)_(candygurl) (4) -> crossgender (69284)
create alias fujimaru_ritsuka_(male) (6) -> crossgender (69284)
create alias hibiki_nyatani_(pokemon_form)_(ikitsunyan) (2) -> alternate_species (37040)
create alias laika_(pokemon_form)_(ikitsunyan) (1) -> alternate_species (37040)
create alias pepper_(crushpepper)_(skunk_form) (13) -> alternate_species (37040)
create alias soups_(rabbit_form)_(superiorfox) (2) -> alternate_species (37040)
create alias jack_(kangaroo_form)_(nightsky) (1) -> alternate_species (37040)
create alias gryphon_(black_version)_(untied_verbeger) (3) -> gryphon (24705)
create alias gryphon_(untied_verbeger) (74) -> gryphon (24705)

Reason: Followup for BURs within topic #54285

The bulk update request #10010 is pending approval.

remove implication carmen_(animal_crossing)_(mouse) (4) -> animal_crossing (54845)
remove implication lulu_(anteater)_(animal_crossing) (1) -> animal_crossing (54845)
create implication carmen_the_mouse_(animal_crossing) (0) -> animal_crossing (54845)
create implication lulu_the_anteater_(animal_crossing) (0) -> animal_crossing (54845)

Reason: Fixes BTRs for BURs in topic #54285

thegreatwolfgang said:

• 5) Looks like one of those exceptional circumstances I mentioned. Suggest renaming to granite_the_horse (since its counterpart is already named granite_the_wolf).

I'm iffy about this, I only associate [name]_the_species] as a naming convention equivalent as full names in some media, rather as a disambiguation trick. Though this is probably a failing on my part

anicebee said:
I'm iffy about this, I only associate [name]_the_species] as a naming convention equivalent as full names in some media, rather as a disambiguation trick. Though this is probably a failing on my part

While it is true that we allow it to be used on some popular characters in media (such as sonic_the_hedgehog and courage_the_cowardly_dog_(character)), that is because they are officially named and popularly called as such.
However, we generally dissuade the use of name_the_species or specifically name_(species), since name_(character_owner) is the preferred choice and it does not run into complications related to alternate_species.

There are also some additional exceptions where name_(character owner) would not look nice and name_the_species is used instead.
For example, if the character owner is called "John the Tiger", you would not tag their character as john_(character) (since it is too common) or john_(john_the_tiger) (since it is redundant/too long).
You would instead stick with john_the_tiger since it rolls off the tongue better.

EDIT: I have looked it up and apparently name_the_species is considered to be one of the "proper formats" for character tags, see howto:tag characters.