Korean Translation Best Practices

Copying @EdogawaKun's comment and starting an issue.

Original comment:

This was something that I was about to ask you. I'm not sure if you've seen my comment on the matter, but in Korean there are few suffixes where a different syllable is put depending on the last syllable of the previous word.

In terms of your example, that's the translation that goes around the issue, so it should work. However, there were other strings that I found particularly problematic.

One of those was Find movies where %@ worked with: string.

In Korean, that would roughly translate to %@과 함께 작업한 영화를 찾아보세요 if we respect the placeholder. However, 과 is not always used.

For example:

In Korean, Sam Neill is written as 샘 닐. In this case, 과 is used. (i.e. 샘 닐*과* 함께 작업한 영화를 찾아보세요.) However, Steven Spielberg is written as 스티븐 스필버그. In this case. 와 is used. (i.e. 스티븐 스필버그*와* 함께 작업한 영화를 찾아보세요.) In the old days of translation, we compromised by putting both of the suffixes in the translation. (i.e. 샘 닐*와(과)* 함께 작업한 영화를 찾아보세요.) However, these days, this method is now seen as a very old way of translation, and makes the translation look dated. I've heard there are now algorithmic ways of solving this, but since I cannot suggest that because of few translation issues on one language, after few hours of thoughts, I compromised by taking out the placeholder entirely. I thought that given the context in the menu, having no placeholder should not be an issue with the overall UX, either.

As you've found on No results found..., there may be a way to go around this. One way that I'm thinking is somehow putting the placeholder at the rear end of the translation, so that we need no suffixes. I'll still have to make the sentence (maybe not even a direct translation) in a way so that could be a possibility, but in the meantime, I wanted to hear your opinion on this. (as you may have guessed I was stumped by this for a while 😂)

cliss / callsheet-localizations

Korean Translation Best Practices #127