Translation generally

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Translation generally

LordOfBikes
Administrator
Hi,

after nearly completing the German translation I have some questions.

What is the right or best way to commit the new ts file.
What does a commit on the translation server do?
Will it commit directly into the main github repo?
Or shall I commit it in my github fork and create a pull request?

When testing the new German translation file I still found some text that isn't in the ts file yet. So a lupdate is necessary to refresh the ts files.
After running lupdate, shall I commit and push all language files to my fork or only the German version?
How will the new ts files be updated on the translation server? May there be conflicts on other language ts files when portions are translated but not committed yet?

Regards,

Armin
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Translation generally

dxli
Administrator
Hi,

Usually, Ries would only commit the translation changes for each release.

I think it's okay to keep translation updated in the master branch.

Thanks,

Dongxu

LordOfBikes wrote
Hi,

after nearly completing the German translation I have some questions.

What is the right or best way to commit the new ts file.
What does a commit on the translation server do?
Will it commit directly into the main github repo?
Or shall I commit it in my github fork and create a pull request?

When testing the new German translation file I still found some text that isn't in the ts file yet. So a lupdate is necessary to refresh the ts files.
After running lupdate, shall I commit and push all language files to my fork or only the German version?
How will the new ts files be updated on the translation server? May there be conflicts on other language ts files when portions are translated but not committed yet?

Regards,

Armin
Loading...