Topic: [APPROVED] Tag alias: star_marking -> star_(marking)

Posted under Tag Alias and Implication Suggestions

The tag alias #57226 star_marking -> star_(marking) has been approved.

Reason: Identical tags. Although star_marking has more posts associated with it than star_(marking), the tag star_(marking) follows the current tag naming convention for markings more accurately, as well as having more aliases associated with it.

For example, heart_(marking) and gloves_(marking) follow the general convention, but star_marking does not.

EDIT: The tag alias star_marking -> star_(marking) (forum #332148) has been approved by @slyroon.

Updated by auto moderator

bitWolfy

Former Staff

thegreatwolfgang said:
You may need to unalias from star_marking first then re-alias both to star_(marking), or else the current alias suggestion would fail.

That's not actually true for normal alias requests.
See the alias page, under "transitives": "Alias ☆ -> star_marking will become ☆ -> star_(marking)".

It's only a problem for BURs, for some reason. Those will fail if they encounter transitives.

faucet said:
I think just unaliasing it should be good, -> star_(marking) isn't a good alias imo. It could refer to a star shape that isn't a marking, and people shouldn't be using unicode tags instead of typing star anyway.

Yeah, this reminds me of the whole issue with <3 and heart_symbol/heart_(marking) as well. There is no real way of getting rid of ☆ other than disambiguation.

bitwolfy said:
That's not actually true for normal alias requests.
See the alias page, under "transitives": "Alias ☆ -> star_marking will become ☆ -> star_(marking)".

It's only a problem for BURs, for some reason. Those will fail if they encounter transitives.

Huh, curious. Didn't know it was an issue exclusive to BURs.

bitwolfy said:
That's not actually true for normal alias requests.
See the alias page, under "transitives": "Alias ☆ -> star_marking will become ☆ -> star_(marking)".

It's only a problem for BURs, for some reason. Those will fail if they encounter transitives.

Considering I plan on making a BUR soon, would the problem resolve if I added the original aliased tags to the BUR? How would one circumvent this issue?

magenta-magic said:
Considering I plan on making a BUR soon, would the problem resolve if I added the original aliased tags to the BUR? How would one circumvent this issue?

No, you will need to un-alias everything from the first tag a BUR first, then make another BUR to re-alias everything to the second tag.

These two cannot be on the same BUR at once since the system does not do it sequentially (i.e., down the list).

bump, just tried to request this

thegreatwolfgang said:
No, you will need to un-alias everything from the first tag a BUR first, then make another BUR to re-alias everything to the second tag.

These two cannot be on the same BUR at once since the system does not do it sequentially (i.e., down the list).

when it's a single tag, an admin can fix it manually before approving the alias, but it's good to announce that the request has transitives in the description

I think that it'd be better to inverse this, honestly. I feel like using *_(marking) rather than just *_marking for shape markings like this is a bit weird.

like, stuff that you wouldn't say in natural speech should have "marking" in parentheses, so stripes_(marking) makes sense, since, in a sentence you wouldn't need to say the "marking" part, ex.: "that tiger has stripes" makes sense on it's own "that tiger has stripe markings" is unnecessary. for cases where "marking" would be necessary for a sentence to make sense without context then it shouldn't be in parentheses, ex. "that tiger has stars" dosn't make sense but "that tiger has star markings" does.

is this going to be approved? came here with the same reason with alien fluff lmao

  • 1