Topic: [APPROVED] [BUR] Distinguishing between hard_translations by the artist and hard_translations by an editor

Posted under Tag Alias and Implication Suggestions

The bulk update request #1397 is active.

remove implication hard_translated (1762) -> edit (0)
remove alias translation_edit (788) -> hard_translated (1762)
remove alias translated_edit (0) -> hard_translated (1762)

Reason: Current usage for hard_translated tends to include translations provided by the artist, which then get the post incorrectly tagged with edit. post #2938984 is a good example of this, as both the Japanese and English versions are available at the same source.
For this reason, I'd like to propose the following tag relationships:

hard_translated implies translated.
translation_edit implies hard_translated and edit.

From these three tags, hard_translated, translated, and translation_edit, we can combine them as follows:
translation_edit includes all unofficial hard translations.
hard_translated -translation_edit includes all official hard translations.
translated -translation_edit excludes unofficial hard translations, but includes note translations and hard translations by the artist.
translated -hard_translated excludes all hard translations entirely.

The following BUR needs to be applied after this one is approved:
category translation_edit -> meta alias translated_edit -> translation_edit imply translation_edit -> hard_translated imply translation_edit -> edit

EDIT: The bulk update request #1397 (forum #317762) has been approved by @gattonero2001.

Updated by auto moderator

if I recall correctly, we only accept (hard) translations to English correct?
if an image is hard translated, and we are limiting the translations allowed to only English, wouldn't posts with hard_translated contain english_text? aka, hard_translated implies english_text

cutefox123 said:
if I recall correctly, we only accept (hard) translations to English correct?
if an image is hard translated, and we are limiting the translations allowed to only English, wouldn't posts with hard_translated contain english_text? aka, hard_translated implies english_text

This matches my understanding of the policy.
If we can accept english_text being mistagged on spanish/etc. translations, since they're dead on arrival anyway, then hard_translated → english_text makes sense.

cutefox123 said:
The bulk update request #3767 is active.

create implication hard_translated (1762) -> english_text (826957)

Reason: we only accept translations to English

If we want to be super pedantic, I could imagine a translation that lacks any text. Let's say the original Japanese text is "2022年12月27日". You could translate that as "December 27th 2022", but you could also just translate it as "12/27/22" and the latter lacks any English text. How likely is that to be the only text in a picture? Perhaps rather unlikely.

EDIT: Oh, I suppose it's also conceivable that the original "Japanese" text was (for example) German text transliterated into Japanese , and the "translation" is just it changed back to German written the normal way. This is another unlikely but possible edge case.

Updated

crocogator said:
If we want to be super pedantic, I could imagine a translation that lacks any text. Let's say the original Japanese text is "2022年12月27日". You could translate that as "December 27th 2022", but you could also just translate it as "12/27/22" and the latter lacks any text. How likely is that to be the only text in a picture? Perhaps rather unlikely.

well currently, translated (which hard_translated implies) already implies text, I mean, you could technically say that numbers are text...

I'll just give it an upvote. I think the odds of either of the exceptions I mentioned actually happening and screwing up the implication are rather unlikely.

crocogator said:
EDIT: Oh, I suppose it's also conceivable that the original "Japanese" text was (for example) German text transliterated into Japanese , and the "translation" is just it changed back to German written the normal way. This is another unlikely but possible edge case.

But then, a proper hard translation would likely also gain an English translation of the German text, no matter who provides it. The implication might not be technically correct in some cases, but practically the tagging would or should be indistinguishable either way.

crocogator said:
EDIT: Oh, I suppose it's also conceivable that the original "Japanese" text was (for example) German text transliterated into Japanese , and the "translation" is just it changed back to German written the normal way. This is another unlikely but possible edge case.

e6 only accepts the original and an English translation, according to the uploading guidelines. If the original was German, then translated/transliterated to Japanese, then translated back to German, only the original German version would be acceptable of those three.

watsit said:
e6 only accepts the original and an English translation, according to the uploading guidelines. If the original was German, then translated/transliterated to Japanese, then translated back to German, only the original German version would be acceptable of those three.

I think the example was supposed to be that the original was Japanese, the hypothetical character was just saying something in German that was transliterated for the hypothetical artist's Japanese audience, and the single translation was just changing it to the actual German dialogue, i.e. only two versions existing in the example.

Hmmm, to add onto crocogator's original point, could there be a scenario where the page only has sound effects in the original language (like ドキ), which then gets hard translated (into doki or ba-thump (or heartbeat sound effect of your choosing)). Would that qualify as not english text but also accepted as hard translation?

This is of course speaking as a hypothetical, and I don't oppose the implication

  • 1