Topic: [APPROVED] Pokémon Ruby Beta BUR

The bulk update request #10939 is active.

Reason: I randomly came across art of the Pokémon Ruby/Sapphire betas and saw that its tags didn't have proper implications the same way the Pokemon Gold Beta received. I figured someone should fix that.

This BUR only contains the Gen 3 beta Pokémon that have posts here, I went through the beta_pokemon_(species) posts to add/create tags for the ones that went untagged. I might add more BURs in this thread if more species ever pop up. I've also aliased some alternate names for the species that changed names across dev stages, keeping the names they had last before deletion.

Note: Warabbit, Beta Treecko and Fiyoko already imply beta_pokemon_(species).

PART 1/2

EDIT: The bulk update request #10939 (forum #447096) has been approved by @spe.

The bulk update request #10940 is active.

Reason: PART 2/2

EDIT: The bulk update request #10940 (forum #447097) has been approved by @spe.

Do we need tags for the individual beta pokemon games? We don't have tags for the individual release pokemon games, I think the beta game tags can also be aliased away.

watsit said:
Do we need tags for the individual beta pokemon games? We don't have tags for the individual release pokemon games, I think the beta game tags can also be aliased away.

Eh, unlike the main games, the content of the betas are very much self-contained and exclusive to that specific beta. This is a case more akin to series where the cast changes depending on the entry, like Zelda for example, fusing all the titles' tags wouldn't be doing a service because a lot of individual characters can be pinned to a specific title. Same thing would happen with beta Pokémon designs.
In normal Pokémon, the cast usually carries over to successive games, which makes it pretty uncommon to see a post that can be pinpointed to a specific game (not even counting versions into the mix), so it's probably for the best to lump it all together. Even then, we have tags for spin-offs that stand out from the main series.

The bulk update request #13309 is active.

create implication kujatta (8) -> beta_pokemon_(species) (1034)
create implication kujatta (8) -> pokemon_ruby_and_sapphire_beta (303)
create implication ninfu (1) -> beta_pokemon_(species) (1034)
create implication ninfu (1) -> pokemon_ruby_and_sapphire_beta (303)

Reason:

yand said:
I might add more BURs in this thread if more species ever pop up.

PART 3/2
_{and stealth bumpEDIT: The bulk update request #13309 (forum #481252) has been approved by @spe.}

The bulk update request #10939 (forum #447096) has been approved by @spe.

The bulk update request #10940 (forum #447097) has been approved by @spe.

The bulk update request #13309 (forum #481252) has been approved by @spe.

The bulk update request #13377 has been rejected.

remove implication zuruuzu (5) -> beta_pokemon_(species) (1034)
remove implication zuruuzu (5) -> pokemon_ruby_and_sapphire_beta (303)
create alias zuruuzu (5) -> zuruzu (0)
create implication zuruzu (0) -> beta_pokemon_(species) (1034)
create implication zuruzu (0) -> pokemon_ruby_and_sapphire_beta (303)

Reason: This was indirectly brought to my attention by Wandering Spaniel: the spelling "zuruuzu" that was in usage here is actually incorrect. The name in the leak is ズルーズ, which transliterates to "Zurūzu", so the tag should be formatted as "zuruzu".

Source

EDIT: The bulk update request #13377 (forum #482313) has been rejected by @yand.

yand said:
The name in the leak is ズルーズ, which transliterates to "Zurūzu", so the tag should be formatted as "zuruzu".

That's "zuruuzu" (or "zuluuzu"), the ー indicating an extension to or elongating of the previous vowel. This can be romanized as either a dash above the letter indicating a long vowel sound, or duplicating the vowel letter, "zurūzu" or "zuruuzu". Since we don't use non-ASCII characters in tags, the uu would be the correct alternative to ū.

In either case, you can't alias away a tag in the same BUR as removing implications from it, since the BUR isn't guaranteed to run in sequence.

watsit said:
That's "zuruuzu" (or "zuluuzu"), the ー indicating an extension to or elongating of the previous vowel. This can be romanized as either a dash above the letter indicating a long vowel sound, or duplicating the vowel letter, "zurūzu" or "zuruuzu". Since we don't use non-ASCII characters in tags, the uu would be the correct alternative to ū.

In either case, you can't alias away a tag in the same BUR as removing implications from it, since the BUR isn't guaranteed to run in sequence.

NGL I only created this followup because I saw that someone from staff edited posts from zuruuzu to zuruzu right before the BUR was passed, and rationalized that it was because the "write as is, but ditch the accents" rule ("pokemon") took precedent, though I can see why it wouldn't apply to what's already an approximation.
I'll take your word for it, cancel the BUR, and manually flip the tags back for the time being.

Thanks for pointing out the last part though, I'll keep it in mind going forward.

The bulk update request #13377 (forum #482313) has been rejected by @yand.

yand said:
NGL I only created this followup because I saw that someone from staff edited posts from zuruuzu to zuruzu right before the BUR was passed, and rationalized that it was because the "write as is, but ditch the accents" rule ("pokemon") took precedent, though I can see why it wouldn't apply to what's already an approximation.
I'll take your word for it, cancel the BUR, and manually flip the tags back for the time being.

Thanks for pointing out the last part though, I'll keep it in mind going forward.

Oh shit, that's my bad. I was going by the "pokemon" precedent yeah, and trying to standardize some of the beta mons' spellings, didn't put it together that zuru(u)zu was included in this BUR