So what about hashtag translations

I don't think this has been "solved" yet. We made untranslatable commentary, deprecated hashtag-only commentary and gave the nearest can a good and hard kick hoping that we would never go that far down the road. Now everyone is still just doing whatever.

Personally I'm very much against translating hashtags in-place. I do not want to click on #Arknights and be redirected to https://x.com/hashtag/アークナイツ, that's just bad design and also straight-up misleading when it comes to what is expected from hashtags and links. I also think translating these with [tn][/tn] is pointless because they are trivial (worst-case just click on them to see where they go), and can lead to cases where you get the same translation 3 times, which is just clutter.

Translating non-trivial hashtags can sometimes be useful, an easy example being #アークナイツ版深夜の真剣お絵かき60分一本勝負, or those Tumblr hashtags which contain half a paragraph of text. For the aforementioned reason, I still think these should be translated with a translation note, and not in-line. This also gives room to format it nicely (like adding spaces) without it looking weird.

So basically what I'm proposing:

• Never change the display text on hashtags
• Keep translations to "non-trivial" (vague term, I know) hashtags, and use [tn][/tn] for these translations.

For what defines trivial hashtags, I think just character, copyright, artist etc. names, as well as ship names.

i agree with using tn, it's the best solution imo

If danbooru ever adds support for ruby characters in markdown that would be my vote.

Ylimegirl said in forum #434026:

If danbooru ever adds support for ruby characters in markdown that would be my vote.

I don't think this would be ideal as it'd convey the wrong semantic meaning, since we're not doing pronunciation guides but translations.

The [tn][/tn] option gives me strong "Translator note: Keikaku means plan" vibes so I really dislike it.

Unbreakable said in forum #434040:

The [tn][/tn] option gives me strong "Translator note: Keikaku means plan" vibes so I really dislike it.

For trivial hashtags I agree, which is why I'd rather just not have anything done at all. But for "sentence-y" hastags they seem like an okay solution to me. What else do you propose?

Unbreakable said in forum #434040:

The [tn][/tn] option gives me strong "Translator note: Keikaku means plan" vibes so I really dislike it.

You said that last time too (forum #340419) but aren't offering any other solution to this conundrum.

I don't think we need to consider edge cases like 3 arknights hashtags for all hashtag translations. It's completely harmless to translate them in place since you can just click original for the original commentary like any other translated commentary and I really don't think the average user even clicks on hashtags in commentaries in the first place except reading them. Also leaving them untranslated doesn't make sense since if it wasn't a hashtag they'd be translated anyways regardless of how simple it was.

Unbreakable said in forum #434040:

The [tn][/tn] option gives me strong "Translator note: Keikaku means plan" vibes so I really dislike it.

stop rejecting our heritage. embrace the keikaku

Could a feature be implemented to automatically "translate" the "trivial" hashtags, similar to what Translate Pixiv Tags does?

I think doing the EXACT same thing as TPT would be bad, since the Wiki has usual hashtags for certain properties, and there's some weird cases like #ウマ娘ブルアカダービー. But it would probably save a lot of time in the long run if some of the most popular hashtags could just be automated. It's repetitive and tedious, and typing out [tn]#BlueArchive[/tn] is also just really annoying because of all the special characters.

ANON_TOKYO said in forum #434044:

For trivial hashtags I agree, which is why I'd rather just not have anything done at all. But for "sentence-y" hastags they seem like an okay solution to me. What else do you propose?

Ylimegirl said in forum #434045:

You said that last time too (forum #340419) but aren't offering any other solution to this conundrum.

My opinion is to just translate them as normal commentary, or if you really want to let people know in some way add the language in qualifier right after (like (JP) or (KR)). It's not like it's impossible to check where a link takes you before you click it (if there are even people clicking them).

wavedash said in forum #434089:

Could a feature be implemented to automatically "translate" the "trivial" hashtags, similar to what Translate Pixiv Tags does?

I think doing the EXACT same thing as TPT would be bad, since the Wiki has usual hashtags for certain properties, and there's some weird cases like #ウマ娘ブルアカダービー. But it would probably save a lot of time in the long run if some of the most popular hashtags could just be automated. It's repetitive and tedious, and typing out [tn]#BlueArchive[/tn] is also just really annoying because of all the special characters.

I think some site-support for translating hashtags similar to TPT would be could and an even better solution. Problem is that gets quite complicated quite quickly since currently the site is in no way aware what hashtags are. So all commentary would have to be re-parsed in a way that would reliably find hashtags. Not impossible, but definitely a pain.

Alixiron said in forum #434082:

I don't think we need to consider edge cases like 3 arknights hashtags for all hashtag translations.

...

Also leaving them untranslated doesn't make sense since if it wasn't a hashtag they'd be translated anyways regardless of how simple it was.

This combination appears thousands of times (commentary:#明日方舟 commentary:#アークナイツ commentary:#Arknights), not even counting other languages, and that's just for Arknights. In general, using hashtags in more than language is pretty common, so I don't know why you act like it's an edgecase.

And they are hashtags, that's the entire point. If they were something different they'd be handled differently, yes, but that's quite obvious.

Alixiron said in forum #434082:

... It's completely harmless to translate them in place since you can just click original for the original commentary like any other translated commentary and I really don't think the average user even clicks on hashtags in commentaries in the first place except reading them. ...

Unbreakable said in forum #434139:

My opinion is to just translate them as normal commentary, or if you really want to let people know in some way add the language in qualifier right after (like (JP) or (KR)). It's not like it's impossible to check where a link takes you before you click it (if there are even people clicking them).

Just because it's possible doesn't mean it should have to be done. Translations are the ones we're meant to look at, having to click original just to know where the link is going is stupid.

https://x.com/hashtag/Arknights should never lead to somewhere that is non-obvious by default. Since translations are shown by default, it's misleading to point the link somewhere else. Similarly with JP or KR suffixes, this just changes the link again, plus it's also just ugly.

Just going on the record that I'm not in favor of not translating hashtags (double negative, hah!), and for the same reason I've always said: not everybody on this site understands Japanese (or any non-English language for that matter). It would be a huge loss IMO to take this valuable information away from the majority of users.

As far as what I would vote for... Ruby DText would be preferable (who cares about semantics). Next preference would be qualify as needed ((JP), (CN)). Last would be [TN]. Fourth would be DText that allows the title attribute to be set, which would popup the translated text when hovered over.

ANON_TOKYO said in forum #434198:

This combination appears thousands of times (commentary:#明日方舟 commentary:#アークナイツ commentary:#Arknights), not even counting other languages, and that's just for Arknights. In general, using hashtags in more than language is pretty common, so I don't know why you act like it's an edgecase.

And they are hashtags, that's the entire point. If they were something different they'd be handled differently, yes, but that's quite obvious.

I think for this specific Arknights example, if they weren't hashtags - just literally "明日方舟 アークナイツ Arknights" - wouldn't you leave it as is and tag with multilingual commentary? You could just do the same thing with duplicate hashtags when there's already an English equivalent in the original commentary.

I think Ruby text would be the ideal solution.

why can't you just use tn tags as if they were ruby text? danbooru already supports tn tags

+1 on the multilingual commentary solution for the Arknights example.

I don't entirely agree with ship or duo tags always being treated as trivial though, there's times where they can provide more context or aren't even obvious as a ship tag unless you know a lot about the two.

I greatly dislike the idea of leaving some hashtags untranslated because they're "trivial". If you can't read Japanese, then they're all just as unreadable, so they should all be translated. We shouldn't be telling users who can't speak the language "no, no, you don't need to worry about those ones, trust me".

I think hashtags should only be translated if they convey something valuable (think Tumblr's walls of hashtags or ship names, for example). Hashtags just going "#Arknights #明日方舟 #アークナイツ" are just plain redundant, when just the first alone tells you everything you need to know.

Also, I feel like even if you can't speak Japanese, for instance, you do learn how the series name is written there over time usually, so I'd much prefer posts not be translated "#Arknights" ad nauseum. How does that help anyone?

I do think Ruby is a good compromise if we can't come to an agreement. While it is mostly a furigana thing, I've seen enough Touhou to know the average user does not care about that tidbit, and if it gets us to a solution, all the better for it.

Knowledge_Seeker said in forum #434554:

I think hashtags should only be translated if they convey something valuable (think Tumblr's walls of hashtags or ship names, for example). Hashtags just going "#Arknights #明日方舟 #アークナイツ" are just plain redundant, when just the first alone tells you everything you need to know.

And how am I supposed to know they're redundant? I don't speak either of those languages.

Also, I feel like even if you can't speak Japanese, for instance, you do learn how the series name is written there over time usually, so I'd much prefer posts not be translated "#Arknights" ad nauseum. How does that help anyone?

It helps users who can't speak Japanese. Translations are for the benefit of all users, not just those who are intimately familiar with the copyright.