Contributors mailing list archives
Re: Moving transation platform to Weblateby
we wished to start using weblate for our PR some added
functionality on hr_skill module.
It will surely be a while before this is eventually merged, although our customer will already be using it.
So now I am not sure what to do, just use the regular way of using PO translations and pray a conflict wont happen?
The platform really looks great by the way, thanks for the work.
For new modules that re not yet in weblate, you can add .po files manually, that will not create conflicts.
For modules that are already in weblate, my recommendation of not touching .po files manually is the safest (although there are ways around if really needed, of course).
On Thu, Jun 28, 2018 at 11:32 AM David Beal <firstname.lastname@example.org> wrote:
always translate using Weblate, and never push changes to .po files manually
A question about the workflow. When your module is in PR and you need a translation, you can't use weblate because no merge.
How to proceed in this case ?
2018-06-18 12:47 GMT+02:00 Jairo Llopis <email@example.com>:
Awesome! Thanks! 👏👏👏👏👏