Working together on translations
-
I don’t see any information on how more than one person can work together on translations.
I have worked on danish translation.
Lately another person have made changes to the danish translation changing words to some other words that i don’t like etc.But seems like there is no information on how to work together on translations. Just how one person can change it.
So one person likes to write it one way and another person likes to write it another way. Then what do we do?
-
It seems like you could create an issue on github, and try to entice that other person to use the thread with you to discuss and compromise on changes to the Danish translation.
If that person is active on THIS community forum, you could private-chat them to do such work.
Just a couple of ideas…
Good luck.
-
The same issue would happen when translator 3 submit something.
-
I didn’t mean to use the issue on github for submitting. I meant it as a collaboration point. Then “n” people could discuss how to collaborate and move forward with an agreed-upon translation.
-
What i am looking is for instructions to be written so new and old translators can read what to do instead of multiple translators submitting translations.
In maybe project there is a Contribute page. On that page can be a Translator page or section.
So on the Translator page would be information on what to do in case you want to update the translator. Like it might say get in touch with current/last translator before doing any work.
-
My guess is that Don won’t bother with that in the GitHub area (though you would have to ask him, not us, because we’re not Don and Don doesn’t read most of what happens in the Forum). I am pretty sure he created this “Translation” section of the Forum so that such interactions would occur here, in the “Translation” section of the Forum, rather than having a “perpetual issue” open in GitHub for discussing translation changes.
Probably the best you could do would be to create a topic here called “Collaboration for Danish translation”, and then add a link to that page as an XML comment (like
<!-- please discuss any changes at https://community.notepad-plus-plus.org/topic/##### before submitting a PR to change this translation -->
). It wouldn’t be enforceable, but there would at least be a notice.addendum: also, since there is currently an open PR for the Danish translation, I would suggest commenting on that PR that you’d like to talk about the changes together.
And requiring that you get the buy in of a previous translator is likely to never be enforced, either – when someone doesn’t submit a translation for a year or more, despite multiple releases of Notepad++ in the intervening time, all of which change the GUI in ways that there are more strings to be translated, it can easily be concluded that someone has abandoned their translation efforts.