Implicating 近親相姦 → incest
Link to implication

Reason:

Translation

EDIT: The tag implication 近親相姦 -> incest_(lore) (forum #236896) has been rejected by @bitWolfy.

It hasn't been tagged yet...

Better implicate 猫 to cat, 木 to tree, 青い金玉 to blue_balls, invalidate 穴, and disambiguate アイス while we're at it...

/shitpost

(Am I missing something or is this a troll post?)

-1 only artist names, character names, symbols and emotes get translated..

Kinshinsoukan. It means incest. The question is, why would we ever implicate a tag nobody should ever be inputting, and evidently nobody has, to what they should be writing in the first place? At this point, I'm half inclined to suggest a feature of disallowing unicode tags overall and searching and aliasing every existing one out of existence. This is a stupid hassle.

notnobody said:
At this point, I'm half inclined to suggest a feature of disallowing unicode tags overall and searching and aliasing every existing one out of existence.

+1 if you do the latter first.

BlueDingo said:
+1 if you do the latter first.

Make it impossible to search for Pixiv artists you don't know the romaji name of?

^ In what sense of 'search'? Aliasing as stated shouldn't prevent use of unicode in search strings.

-1
We don't do translations in tags, with the exception of artists names.
If we do it for one language, we'd have to do it for all, and this would make the site cry as well as the administration.

Translations of what in tags? Are there even any valid non-English tags in existence on here that we would need unicode characters to write? Not like loanwords, I mean, but actual things that are best kept not only not in English but not even in the character set. Any tag not written in English, unless there's some alias for it, you might not even be able to type it in to search for it at all if you don't have the right input language on your device. Seems like an unnecessary hassle.

savageorange said:
^ In what sense of 'search'? Aliasing as stated shouldn't prevent use of unicode in search strings.

New artists won't have an alias yet, and the taggers can't add any artist tag because the Japanese letters wouldn't be allowed.

Seems like it would just skip a step in that case, right? If the going strategy is enter the romanized name when it's available, or if it isn't, enter it in the original form (assuming you can) and then ask for a translation and an alias, then just not entering it at all and waiting for a romanized name to be entered would be simpler. Or maybe have a sticky thread for it.

The tag implication is invalid. We don't implicate/alias tags other than in English, with the exception for artist names.

Also -1 to disallow unicode in tags because technically speaking the alphabets are also in unicode. If you mean limiting it then like @Furrin_Gok said, new (non-English) artist names cannot be tagged.

Deh-tiger said:
Better implicate 猫 to cat, 木 to tree, 青い金玉 to blue_balls, invalidate 穴, and disambiguate アイス while we're at it...

木 is actually wood, 树 is tree. At least in Chinese.

notnobody said:
Seems like it would just skip a step in that case, right? If the going strategy is enter the romanized name when it's available, or if it isn't, enter it in the original form (assuming you can) and then ask for a translation and an alias, then just not entering it at all and waiting for a romanized name to be entered would be simpler. Or maybe have a sticky thread for it.

You can't get the romaji for Kanji, as there are way too many words they can represent.

TheGreatWolfgang said:
If you mean limiting it then like @Furrin_Gok said, new (non-English) artist names cannot be tagged.

木 is actually wood, 树 is tree. At least in Chinese.

I did mean just limiting. The actual encoding doesn't matter. I just meant eliminating the characters the average user can't input with their keyboard without software they don't always have.

That first character is both in Japanese - moku and ki. I don't know that second one. I guess it's probably the simplified form of 樹.

Furrin_Gok said:
You can't get the romaji for Kanji, as there are way too many words they can represent.

That's not always true, but even when there're alternatives, there're a few of us on here who can do it anyway. The only way it would be true that you couldn't do it is if they were genuinely gibberish, but even then, you could find out somewhere how they pronounce it, and the original wouldn't be any more helpful to anyone who couldn't read it to begin with anyway.

notnobody said:
I did mean just limiting. The actual encoding doesn't matter. I just meant eliminating the characters the average user can't input with their keyboard without software they don't always have.

That first character is both in Japanese - moku and ki. I don't know that second one. I guess it's probably the simplified form of 樹.

That's not always true, but even when there're alternatives, there're a few of us on here who can do it anyway. The only way it would be true that you couldn't do it is if they were genuinely gibberish, but even then, you could find out somewhere how they pronounce it, and the original wouldn't be any more helpful to anyone who couldn't read it to begin with anyway.

People can copypaste the symbols (kanji or otherwise) to search for that artist. Actually blocking tge symbols would be detrimental.

I'd sort of just assumed people were usually copying and pasting those, but from where? Like, is it every time you want to see something by artist x, do you browse to their Pixiv or something, copy their name, don't just look at it right there, and then come back here to paste it in for the search? Seems just so much simpler to just have the first person to post one of their works post in a sticky forum thread or something and have the tag created and kept. Alias the copy pasted value to it in case someone does arrive that way in the future.

notnobody said:
I'd sort of just assumed people were usually copying and pasting those, but from where? Like, is it every time you want to see something by artist x, do you browse to their Pixiv or something, copy their name, don't just look at it right there, and then come back here to paste it in for the search? Seems just so much simpler to just have the first person to post one of their works post in a sticky forum thread or something and have the tag created and kept. Alias the copy pasted value to it in case someone does arrive that way in the future.

You can't suggest an alias for something you can't read. You can't post a sticky. People aren't going to search for an alternate name where it's not immediate obvious.

But if you just paste it in to the search and get the alias as a result, you're good to go. If you paste it in and get nothing, you can paste it into the thread to ask for a translation, resulting in an alias. As time goes by, should be that the only time someone pastes it in and doesn't get an aliased result is when it's brand new to the site, and that shouldn't last long for any given artist who doesn't more commonly go by a more widely readable name.

notnobody said:
But if you just paste it in to the search and get the alias as a result, you're good to go. If you paste it in and get nothing, you can paste it into the thread to ask for a translation, resulting in an alias. As time goes by, should be that the only time someone pastes it in and doesn't get an aliased result is when it's brand new to the site, and that shouldn't last long for any given artist who doesn't more commonly go by a more widely readable name.

Except you can't alias, because, hey, it's impossible to use those characters. See the problem?

Right, I was thinking about disallowing them for creation of tags, but I guess those interfaces might be inseparable. Could restrict it for admin usage only for creations maybe.

notnobody said:
Right, I was thinking about disallowing them for creation of tags, but I guess those interfaces might be inseparable. Could restrict it for admin usage only for creations maybe.

Or just let them exist in the first place so that when an alias doesn't exist, a person can copypaste it to have a tag before the alias goes down. Be rather difficult to find the images to add the tag after the fact.

The tag implication 近親相姦 -> incest_(lore) (forum #236896) has been rejected by @bitWolfy.

auto_moderator said:
The tag implication 近親相姦 -> incest_(lore) (forum #236896) has been rejected by @bitWolfy.

Jeez, 5 years of silence for a rejection, that's rough

notnobody said:
At this point, I'm half inclined to suggest a feature of disallowing unicode tags overall and searching and aliasing every existing one out of existence. This is a stupid hassle.

This turned out to be rather prescient. :p