The bulk update request #2511 is active.

create implication baybayin_text (40) -> text (1141795)
create implication croatian_text (15) -> text (1141795)
create implication constructed_language (477) -> text (1141795)
create implication romaji_text (84) -> text (1141795)
create implication romanian_text (8) -> text (1141795)
create implication sanskrit_text (9) -> text (1141795)
create implication swahili_text (5) -> text (1141795)
create implication theban_text (2) -> text (1141795)
create implication tibetan_text (1) -> text (1141795)
create implication waloon_text (0) -> text (1141795)
create implication xhosa_text (1) -> text (1141795)
create implication zalgo_text (21) -> text (1141795)
create implication translation_check (4703) -> text (1141795)
remove implication tantalog_text (174) -> text (1141795)
create implication species_name (1428) -> text (1141795)
change category commissioner_name (280) -> meta
create implication commissioner_name (280) -> text (1141795)
change category copyright_name (226) -> meta
create implication copyright_name (226) -> text (1141795)
create implication japanese_sign_language (4) -> sign_language (105)

Reason: Other language_* tags imply text already.
Tantalog is a fictional language, which implies constructed language (Esperanto also implies this), which should imply text.

Species/commissioner name tags means that text must be present for it to be tagged as such.
Also moving these tags to the meta category to match the other tags.
Copyright name's wiki says that it can be text or a logo, but I put it in the BUR, unless people thinks otherwise, it can go either way.

Translation check means that there is some text that is translated. Though maybe it should imply translated?

ASL implies SL, so it makes sense that JSL should also imply it. Maybe moved to the meta category?

Related forums:
topic #27846 | aliasing filipino dialects together, may conflict with this BUR.
imply character_name -> text see topic #18080
imply artist_name -> text see topic #30058

EDIT: The bulk update request #2511 (forum #335193) has been approved by @slyroon.

The bulk update request #3779 is pending approval.

change category fictional_language (399) -> meta
change category constructed_language (477) -> meta
create implication aurebesh_text (60) -> fictional_language (399)
create implication bengali_text (1) -> text (1141795)
create alias engrish_text (0) -> english_text (831510)
create implication eorzean_text (3) -> fictional_language (399)
create implication faroese_text (1) -> text (1141795)
create implication furbish_text (4) -> fictional_language (399)
create implication inkling_text (13) -> fictional_language (399)
create implication maori_text (3) -> text (1141795)
create implication orokin_text (4) -> fictional_language (399)
create alias te_reo_text (1) -> maori_text (3)

Reason: Part 2: Electric boogaloo
move the synthetic languages to meta to match natural languages.
engrish is english, but different.
imply the rest of the languages
imply the symthetic languages to imply fictional_language

not sure what do about old_english_text

Removed:
implicate runic_text -> fictional_language
implicate galactic_text -> fictional_language
implicate draconic_text -> fictional_language

no google results for "trunic text" but there are results for "tunica text"...
Not sure on what to do with character cipher, which seems to be its own... thing I guess...
could of sworn there was already a tag for toki pona...
If there is anything I should change, let me know.

The bulk update request #3780 is pending approval.

create implication toki_pona_text (5) -> constructed_language (477)
change category eorzean_text (3) -> meta
change category faroese_text (1) -> meta
change category furbish_text (4) -> meta
change category inkling_text (13) -> meta
change category maori_text (3) -> meta
change category orokin_text (4) -> meta
change category toki_pona_text (5) -> meta

Reason: see above:

it was over the limit by ONE entry

Removed:
category draconic_text -> meta
category runic_text -> meta
category galactic_text -> meta

Eh, the fictional languages give me pause. Draconic text and Galactic text in particular are rather generic terms that could describe distinctly different things; e.g. both D&D and Elder Scrolls could have a concept of "draconic text", but have nothing to do with each other. And space is a pretty common setting, so it's easy to have different interpretations of galactic text that are unrelated. Runic text also seems like something that could be completely different in different settings; outside of actual real-world runic text, you would have a distinction between magic runes or ancient runes that could be completely made up, along with runes that are made to look like real-world runes but aren't.

IMO, we should only have tags for fictional texts that come from an established setting, like Splatoon or D&D or Pokemon or something, and avoid generic names like "draconic", "galactic", "runic", etc.

to be fair, searching runic languages does bring up "elder Futhark" which is probably a better name.
the full name of the galactic language I can find is "The Standard Galactic Alphabet" so uh... not much better

I'll edit it to remove the generic ones.

cutefox123 said:
to be fair, searching runic languages does bring up "elder Futhark" which is probably a better name.
the full name of the galactic language I can find is "The Standard Galactic Alphabet" so uh... not much better

If worse comes to worse, you can use a suffix to specify what setting/series/franchise it belongs to. draconic_text_(elder_scrolls) or something would make it clear what it refers to, then draconic_text and such generic ones can be disambiguated/invalidated.

cutefox123 said:
I'll edit it to remove the generic ones.

They still seem to be in the last BUR.

watsit said:

They still seem to be in the last BUR.

Those tags do still belong in the meta category, at least until we decide what to do with them, but I'll remove them anyways.

cutefox123 said:
Those tags do still belong in the meta category, at least until we decide what to do with them, but I'll remove them anyways.

They're obviously ambiguous, so they should be in the Invalid category, if not aliased to _(disambiguation) tags that should be in the Invalid category.

cutefox123 said:
create implication constructed_language (304) -> text (774483)

What about Esperanto audio?

gattonero2001 said:
What about Esperanto audio?

I mean like, I guess, but we dont have an Esperanto audio or any language audio tag, and they dont imply constructed language, all tags that imply constricted language in some way are all texts.

[coming over from topic #39729]
Eh my main complaints with the bur is
audio from fictional languages will imply fictional language and then text, despite there being no text, and

General disagreements with how fictional_language and character_cipher should be treated. I believe fictional language be languages created from the ground up, and character cipher being a "language" which is just english (or other languages) but with the letters and digraphs replaced by symbols of the created "language". Though I wouldn't be entirely opposed for character_cipher to imply fictional language.

The bulk update request #2511 (forum #335193) has been approved by @slyroon.