Splitting up translation_request and commentary_request

The wiki page for translation request says that, to find requests for French translation, I should search french text + translation request. Most of what you'll find under that combination, though, are images almost entirely in (untranslated) Japanese, with maybe one line of (already translated) French text. I can't remove french text, because the image does have French text, but I also can't remove translation request, because the whole thing hasn't been translated - it just that the text needing translating... isn't French.

e.g.
post #6879283
post #6650995
post #5210444

Ditto for commentary request + french commentary; most of the stuff in the French commentary request queue really needs Japanese commentary - the one sentence of French was already taken care of ages ago and now it's just languishing in partial commentary limbo.

e.g.
post #3860127
post #5723016
post #5618737

To stop mostly Japanese (and to a lesser extent Korean) from gumming up the translation queues for other languages - the obvious solution to me is to split up translation request, check translation, commentary request and check commentary into language-specific tags, e.g. translation request (french), check translation (french), commentary request (french) and check commentary (french). Then deprecate the language-unspecific tags so that new posts wanting translation done are forced to specify which language needs work.

And I would be happy to put together that BUR, but the obvious problem I foresee this causing - and why I didn't immediately just go for a BUR - is that it implies a UI modification is needed. For example, the checkbox to add check translation when submitting a translation wouldn't mean anything anymore if translation traffic is supposed to be re-routed to check translation (french); likewise with commentary. It seems like the dialog box would need to include a list of languages tags and you could check off the ones that no longer need translation work, while leaving other languages (Japanese, usually) checked on as still needing translation work. But, I don't know how much of a technical challenge that poses.

Most of the text on posts and their commentaries here is in Japanese, so it's to be expected.

In my opinion there's no need to create 4 new tags for each language and deprecate the existing tags. You should use the Artist Commentaries page to see the full commentary when translating and the posts mentioned with French text have their Japanese text visible on the thumbnails. Though it'd take some time, you could create a favgroup to filter the posts with translated French text.

Regarding commentaries, we have mixed-language_commentary tag. So for example, the query "french_commentary -mixed-language_commentary" would (theoretically) yield posts with commentary written only in French. (I know this doesn't solve all of your problems, but FYI)

Brightlight said:

So for example, the query "french_commentary -mixed-language_commentary" would (theoretically) yield posts with commentary written only in French.

This doesn't help when I can't search for more than 2 tags at a time. I can't add -mixed-language_commentary to the query without getting rid of either check commentary or commentary request - rendering it moot because again most of the results wouldn't actually need translation.

Arcaeca said:

This doesn't help when I can't search for more than 2 tags at a time. I can't add -mixed-language_commentary to the query without getting rid of either check commentary or commentary request - rendering it moot because again most of the results wouldn't actually need translation.

You could try adding mixed-language_commentary to your blacklist. I used it to make tag gardening a bit easier while I was still a basic Member.