I have been translating into Korean for several months. I get ideas from some users and some are modified. However, some users are messing with my translations. As a result, the translation is inconsistent. Also, some words and sentences are translated with different meanings.
I want to limit the translation rights of some users.
For several months I have been contributing to remmy Korean translation. I don’t want to see my efforts ruined.
I object to other people editing my translations without my permission. Translations need to be rechecked, reviewed, and corrected from scratch. waste too much time
I believe that you can block already translated strings so that they cannot be replaced by another translation (I have seen this in other projects using Weblate).
However, your idea of limiting translation suggestions could really hinder the accessibility of the project, and in my opinion, one of the strengths of Lemmy is that it is available in many languages, thanks to the fact that it has always been accessible. As soon as I saw that nobody had translated Lemmy into Basque, I decided to help the developers. And I am aware that some of the translations I did could be improved, because the context is ambiguous and sometimes there are several ways to interpret a text string. But if the translations had been “locked”, I would not have contributed to the project. And I think many users will think the same if that is done.
I don’t know what you think about what I say, but I would like to hear your opinion about it. I think the best solution is to create a group dedicated to translators in Matrix as @nutomic@lemmy.ml said and create a consensus on how text strings should be translated or oriented.
Okay I created a Matrix chat for translators, please join. Someone can also create a Lemmy community, then I will announce both of them on weblate.
Where’s the link?
Sorry, fixed.
Done. Thanks.
I agree with your opinion. I just hope that the English pronunciation does not translate into Korean pronunciation.
Here are the possible translation workflows in Weblate. Right now we are using “direct translation”, so what you want is basically switch to “peer review” mode. Thing is that it affects all languages in a project, so it would be good to get input from more translators before changing that.
Yeah that’s my feeling too, I don’t know that we’d want to switch to the peer reviewed model unless people with translation experience think its a good idea.
deleted by creator
Several people have been asked to correct incorrect words or sentences. I would like to express my gratitude. But spoiling the translation is intolerable. I am not excluding others. We are trying to reverse the broken translation due to one person.
We could also ban the user who does that, but i’m not sure its the best solution.
deleted by creator
Is it a single user going through and changing all the translations? That’s annoying haha
Same here. I am also a native Spanish speaker, but I can help with translations written in English without any problem.
Sometimes the translations we make are erroneous because we are guided by the logic of our language and ignore the logic of the English language. But in those cases, it is as easy as suggesting instead of directly translating the text string. Or as you say, ask someone else to review it to make sure you don’t make mistakes.
@nutomic@lemmy.ml is there a way to add translation approvers with weblate?
Can you give some examples? I haven’t used Weblate, but is there a way to comment on the tokens so you can leave notes for other translators? I think limiting translation rights is a slippery slope. I have worked on projects where that has happened, and the result was much worse than inconsistency =\
Let’s take an example. If you pronounce squid game in English, it is squid game.
However, if the Korean pronunciation of the squid game is used as it is, it becomes a O-Jing-Uh Game.
Had the O-Jing-Uh Game been used, it would not have received the world’s attention. You probably didn’t know what it meant.
Other translators who run into problems translate even more bizarrely.
Ban is written as ban and translated into Korean should be translated to mean to block or deport. (restricted privileges)
When translating ban, we translate it as ban (밴됨). ban = 밴됨 Few Koreans know the meaning of this word. it’s english Writing the pronunciation into Korean is not a translation.
example
- ban = bean dum (Korean pronunciation)
- down vote = da-un boat (Korean pronunciation)
- up vote = up boat (Korean pronunciation) … …
I am not a person who can speak English. Has the meaning been conveyed?
영어 잘 하시는데요… ㅎㅎ 뜻이 전달됐어요! (저도 한국말 할 줄 압니다^^). In the case of ban(밴됨), I can see how that would make things confusing. On other projects I have worked on, sometimes those kinds of transliterations are preferred. For example, 로캘/로케일 vs. 현지/현장. I am not sure if Weblate has a way to indicate “standard” translations of common tokens, or if can facilitate discussions. Maybe there should be a Lemmy translators community to serve as an agora for this kind of thing :)
I agree a Lemmy translators community (or Matrix chat) would be a good idea. That would also make it easier for us devs to stay in contact with translators.
Yes! That would help us coordinate better as translators :)
I noticed it was saying 밴됨 and I was like “well I guess that word makes sense…?”. Glad to know it’s an awkward word and it’s not just me _