When “difficult” becomes “impossible” in translation

One word got ahead of the speaker

The public theater invitation on an exam day uses this Japanese reply:

ぜひ行きたいんですが、その日は試験で。

KYOTOEIC translation

I'd really like to go, but I have an exam that day…

In this invented scene, the speaker wants to go to the theater but has an exam that day. Nothing in the reply says they plan to skip it. The unfinished sentence leaves no basis for making that decision on their behalf.

The earlier English answer option said “Interested, but unable to attend that day.” Japanese used “参加しにくい,” and Korean used “참가가 어렵다”: both describe difficulty attending. English made the obstacle sound more absolute. The public variant now says “finding it difficult to attend that day.” Even when options point toward the same answer, the certainty they express should match.

Less absolute can still be useful

The person extending the invitation could ask when the exam finishes before buying a ticket. “Difficult” keeps the scheduling obstacle in view while leaving the speaker room to say whether they can attend.

The reverse matters too. If the original gives a specific deadline or alternative, making it vaguer loses information. Replacing “Sunday” with “sometime” might sound conversational, but it takes away something the other person can plan around. During review, we compare who can do what and when, as well as the tone.

In the reservation question asking for a name, the English “May I ask your name?” and Korean “성함을 여쭤봐도 될까요?” differ in length. Both still request the guest's name. A smooth sentence that instead requests the receptionist's name or permission to cancel the reservation would change the task.

What the revision counts count

On October 13, 2026, we compared the second and third saved versions of the 300-question bank again. Korean had changed values in 97 dialogue fields and 298 explanations; Japanese in 16 dialogue fields and 179 explanations; English in 44 dialogue fields and 204 explanations. The question fields and correct-answer keys were unchanged in all three languages.

The larger Korean count does not show that Korean had the worst translation. A spacing adjustment counts as one changed field, and a substantial rewrite also counts as one. These are file differences, not error rates or native-speaker ratings. The public answer-option correction discussed above was a separate task, outside this comparison of 300 questions.

Correcting a translation while preserving its history

The public variant received a new ID, and the earlier wording remains in its saved version. Quietly replacing an old sentence would make it harder to establish what a player actually read. Corrections and preservation therefore go together.

If you spot a translation error, include the scene's link, the language and the wording in question. Alongside “this sounds awkward,” an explanation such as “this could mean the receptionist's name, but the question asks for the guest's” gives us a specific point to compare with the original.