Translations
#3651
Replies: 1 comment 1 reply
-
Thanks Navid for all your hard work. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have always wondered about translations. I always wonder how a project lead can be confident that no translator has accidentally or unintentionally caused a mistake.
A repository has a lead who has to verify every submission before it is merged.
A lead knows exactly what field every developer has been active in and which areas the different developers are good at.
So, the lead can ask a developer: "tell me what you think of this PR" before merging or rejecting it.
But, does a lead do the same for every word translation? I don't see how that would be practical.
I don't want to antagonize anyone here. I would like to understand how any project lead, not just ours, deals with translations.
I have made submissions for a new feature to be added. And the reason it was rejected was a single word. I believe it should be like that. I'm not questioning that.
But, how can the lead apply the same level of scrutiny if what comes out in the hands of a user in other languages is something that has no idea about? His scrutiny about the used words only apply to English.
Diabetes does not spare someone just because they don't speak English. Everyone can have diabetes. I don't want to deny anyone the use of xDrip just because they don't speak English.
But, when I was a kid, I didn't speak English. And I could use a TV even though all the knobs had English descriptions only.
Of course there is no comparison. A TV has brightness and contract and volume and few others. xDrip has so many different settings. But, I cannot stop wondering is this the right way to do this.
I don't have a solution. I am just wondering. How do other projects deal with this?
I have submitted improvements to English strings. I was asked "are you sure, because if you are not, you will be wasting the time of many volunteers who need to translate these".
I couldn't agree more that I should not change something unnecessarily because it could cause unnecessary work.
But, at the same time, I cannot help wondering isn't this putting the cart before the horse?
I am sharing my thoughts. I hope this does not cause any hard feelings. I want what is best for the project and the volunteers who maintain it.
If something is wrong in English xDrip, I hear about it.
As an example, there are so many complaints about why there are so many settings in xDrip that are named filter when in fact there is no filtering done for G6 or G7 real data as opposed to the history. And I intend to fix the definitions in English.
But, what happens if something is wrong in a different language only because of an incorrect translation? I don't see how I would hear about that. How am I supposed to ensure that there are no errors in the definition for different functions in other languages?
Beta Was this translation helpful? Give feedback.
All reactions