Donmai

alias anchor -> anchor_(device)

Posted under Tags

BUR #4807 has been rejected.

create alias anchor -> anchor_(device)

The anchor tag is supposed to be for actual anchors, like in post #4382869, as opposed to anchor symbol, which includes everything else in the shape of an anchor that is not a real anchor, but this distinction in practice doesn't exist because people don't pay attention to tag names.
In an ideal world we could just leave the main tag unqualified, but this is a world with countless ship-themed gacha games where every character has an anchor drawn somewhere in their design.

(second part of the BUR will be to remove the alias and make anchor a disambiguation page)

Wait, since when is anchor symbol for physical anchor ornaments? Accord to the wiki (also back in topic #14490) it's used for a single anchor symbol on a piece of clothing as opposed to a repeating pattern, also symbol doesn't bring to mind physical objects to me.

But yes, there should be different tags for actual anchor and for ornament versions.

Unbreakable said:

Wait, since when is anchor symbol for physical anchor ornaments? Accord to the wiki (also back in topic #14490) it's used for a single anchor symbol on a piece of clothing as opposed to a repeating pattern, also symbol doesn't bring to mind physical objects to me.

An "insigna" is a badge, it's not just a drawing, so the wiki has to be rewritten if "anchor symbol" has to just be a drawn pattern.
Gonna be honest, I had completely forgotten about that topic, but it doesn't make much sense to me that we would distinguish a tag for the anchor symbol from a tag for anchor-shaped ornaments. We don't do that for heart and other shapes for example.

In any case I've removed the implications from the BUR, to prevent stopping it.

BUR #4808 has been rejected.

create alias anchor_symbol -> anchor_print

anchor symbol is identical to anchor print in usage. And regardless, we don't have single/multi pattern distinction for any other tag. I don't think I've ever seen a multi-anchor pattern, given that the vast majority of ship gacha use single anchors. If someone really wants to be able to search for that, something like multi-anchor pattern or something should be created instead. As it stands these two tags exist for the same concept.

(this alias should also be removed just like the opening request's once it goes through)

BUR #4809 has been rejected.

create implication anchor_hair_ornament -> anchor_(symbol)
create implication anchor_print -> anchor_(symbol)
create implication anchor_choker -> anchor_(symbol)
create implication anchor_necklace -> anchor_(symbol)
create implication anchor_necklace -> necklace
create implication anchor_earrings -> anchor_(symbol)

And finally, to follow examples like diamond (symbol) and star (symbol).

Disagree with #4808. This could lead to a large number of posts with anchor earrings, necklaces, hair ornaments, pins and so forth being tagged as anchor_print. Anchor_print should be restricted to patterns on textiles.

It bears mentioning that ship girls are drawn as giantess more often than your average character. Consequently, it's not improbable that there's a few pictures out there where, e.g. anchor_earrings literally are anchor_(device)

Arcana55 said:

Disagree with #4808. This could lead to a large number of posts with anchor earrings, necklaces, hair ornaments, pins and so forth being tagged as anchor_print. Anchor_print should be restricted to patterns on textiles.

How? One is anchor_symbol, the other is anchor_(symbol). I specifically set this distinction so the BUR has no chance of accidentally going wrong.

Arcana55 said:

It bears mentioning that ship girls are drawn as giantess more often than your average character. Consequently, it's not improbable that there's a few pictures out there where, e.g. anchor_earrings literally are anchor_(device)

Then it can be tagged with both tags.

indexador2 said:

I find the (symbol) qualifier to make less sense in anchor necklaces and earrings than diamond or star ones do. After all, star_(symbol) doesn't look like a star and diamond_(symbol) doesn't look like a diamond, but anchor_necklace is identical to an anchor in every way except size, and even then it could probably be used as an anchor for a small boat.

On the contrary, diamond (symbol) is specifically for a symbol of a diamond that is not a diamond (๐Ÿ’Ž). You're thinking of diamond (shape).
There's often mistags due to the similar names, but in this case there's no anchor_(shape) so there should be no issue like this.

I'm in agreement with Arcana55 and oppose implicating the physical object anchors to symbol when visually they're identical to the physical device. They're also not a flat representation of the object (as defined by the wiki for anchor_symbol), they're depicted as physical objects and should be treated as such.

I would like to suggest though that the various ornamental ones should have a parent tag like anchor_jewelry or anchor_ornament.

edit: Instead of aliasing anchor to the device, it would probably be better to use anchor as a catchall for all physical anchors and have anchor_(device) as a child tag for the actual device. This removes unnecessary headache of worrying that small or jewelry anchors are being put into the same tag alongside ones that can be used as the actual device.

Updated

Agree with #4808
anchor_symbol and anchor_pattern have a very very similar wiki description.
if anchor_symbol and anchor_print are supposedly two tag with different purpose, then i think its better to change the wiki to be more descriptive. the similarity between two wiki made the taggers confused and ultimately mixing them up.
for example if we search anchor_symbol -anchor_print we can get stuff like post #4444762 and post #4451100 and if we search -anchor_symbol anchor_print we get post #4006488
So it's either aliasing them or change the wiki to be more distinctive.

For #4809
i think it's better to make anchor_symbol and anchor_(symbol) something more distinct because some taggers will bound to mix between the two

here is my suggestion to solve them both:
Removing anchor_symbol by mixing them into anchor_print (extra bonus is that it will be consistent to the *_print tag)
You can do #4809 so that people won't confuse anchor_(symbol) as anchor_symbol because anchor_symbol will not be exist anymore

Updated

1