alias kanji, furigana, hiragana, katakana -> japanese text

Posted under Tags

BUR #16778 has been rejected.

undeprecate japanese_text
create alias furigana -> japanese_text
create alias hiragana -> japanese_text
create alias katakana -> japanese_text
create alias kanji -> japanese_text

These don't help translators, readers, or searchers, and just make searching/tagging/translating harder. They also pad tags (a lot of posts with Japanese text need 2 or 3 of the above, though they're horribly undertagged).

One reason to keep Japanese text searchable would be if you're looking for some art with cool runes you can't read. Examples: post #5977592, post #6269547, post #6265773, post #2111839, post #6096355, post #6283792.
This is often huge kanji, but sometimes actual Japanese symbols too. These posts should be searchable in some capacity, but the distinction between kanji/kana is not particularly important.

Would text focus or big text (doesn't yet exist) be enough to cover everything people want to search? Most of it would be Japanese text anyway.


  • Leave the tag bloat and undertagging of these, but make these imply japanese text instead for ease of searching, etc.
    • Removes none of the existing functionality, but also makes it easier to use.
  • Deprecate them all
  • Alias furigana (almost always hiragana), hiragana, and katakana to simply kana

We also have archaic japanese text for older Japanese.

[...] having something called “kanji” is inviting smart people to tag literally any image with kanji


That's a lot more important when it's not a meta tag. It's a separate topic that comes up a lot, but when it comes to translations, keeping the number of "requests" down helps ensure that the posts people actually want translated get translated, especially with translations being much harder to do (and less "necessary" than tags). Of course, the *_request format is easy and consistent instead of calling it something like untranslated or no commentary.

Edit: As discussed in topic #22939, commentary:untranslated should theoretically replace commentary request eventually, but that wouldn't work for posts with missing notes/translations, at least not without Japanese text being confidently autodetected.


I would be more for getting rid of these tags entirely, or at least renaming them to something more useful. seriously, what is the point of katakana? its wiki wants it to be used only for non loan words or sound effects, yet those make up a lot of the tag. same thing with hiragana and kanji, these would apply to pretty much all Japanese language translated/translation request posts, to the extent that tagging them seems redundant. people not adding translation request like you say is of course another issue that these “duh” tags don’t solve.

the only valid case I could see is for kanji “art” like the examples brought up, where the characters are given special focus or played with in some way as its wiki currently states. this could easily apply to hiragana/katakana too, however the name should be something less painfully basic and unhelpful.

furigana however I can understand, because unlike hiragana or katakana this is a relatively uncommon choice some artists include in their works.

Attempting to see whether or not these tags had previously seen discussion in the first place yields nothing, at least nothing using the option to search linked tags on the forum. And looking at the tag history of each reveals a lot of meandering, and gives a feeling of "we had an idea for this, but we never really realized it - but we're still going to work on it and keep 'em around," leading us to this situation where they've just slipped through as undertagged messes.

That isn't to say that there isn't anything we could draw from them, though, but in their current form and especially with their current names, I'd just say nuke and deprecate 'em in accordance with the current status quo. Now, in terms of what we can draw from them, we can look at the kanji tag for example. The current rule-set of kanji is incredibly broad for one tag, but it provides a decent avenue for improvement. Take the "featuring [it] as a design element [or] focal point of the image..." rules and separate that out into its own tag for kana and kanji, and a second tag based on the "jokes about the visual appearance of [it]" rule. Each would provide an actual use to taggers (posts focusing on one or multiple kana/kanji that isn't text focus, and posts which play with kana/kanji as a possible pun subtag), though I don't know what you'd exactly call either tag.

But if we're dealing with furigana, we also have to deal with nonstandard furigana. But we could alternatively just rename both furigana and nonstandard furigana to ruby text and nonstandard ruby text, based on the reason Bob brought up, and broaden it beyond just Japanese because it is uncommon in general.

As text focus has too many images that are predominantly text, like tiny paragraphs, I think the new tag should be called big text. A lot of big text posts would still have text focus, however.
Big text is applicable to all the examples in the OP, and pretty much all artistic text I would ever want to search. It doesn't seem particularly open to misinterpretation or excessive use, and most examples would be JP or English.


BUR #16793 has been approved by @nonamethanks.

deprecate kanji
deprecate katakana
deprecate hiragana

My proposals:

  • create kanji joke and other specific concepts that are currently lumped together (and thus unsearchable individually) under kanji
  • deprecate kanji, katakana, and hiragana, because they're useless padding tags - most posts with text on danbooru have either kanji and hiragana or katakana

I don't know about furigana, it's not that common so it might be useful, but then again a shitton of comics have it. I'm neutral on it.

The katakana tag doesn't seem useful the way it's currently used. I did a search for katakana translation request and many of the posts have a mix of hiragana, katakana, and kanji. However, I do think it could be very useful if it were reworked to apply only when the Japanese text in an image is mostly katakana (and if the tag is renamed to "katakana only" or something similar).

I can read hiragana and katakana and know a bit of grammar, but don't know much actual Japanese and often have to rely on handwritten kanji recognition for vocabulary. There are many posts I have no business trying to translate, but it's very easy if the post contains mostly loanwords, character names, or copyright titles. Having a tag that focuses on posts with easily identifiable katakana words like these can give less skilled translators like me something to do and allow the more skilled translators to focus on other posts.

BUR #21764 has been rejected.

undeprecate japanese_text

As far as I know there is currently no way of tagging an artwork as having japanese text.
Yeah, most of the text on this website is japanese text, but there is no way to search for posts containing it unless you remove some of the bigger *_text tags. And if you want to search for the opposite, good luck?
(Even then, it doesn't count for mixed-language_text)

1 2