My organization has projects that act sort of like git branches for versions: there is a main project and there are projects for older versions. Translations are heavily done in the main project, while the other projects receive translation memory fill-up due to great similarity in the source strings.
From time to time, a new version is released and I have to branch the main into a versioned branch, and by the I main I copy all translation resources from that main project into a new version project. Translations still being worked on in main project.
Currently, I have to manually create a versioned project, download the resources for each language from the main project into PO files, and then upload those PO files into the newly created version.
I’ve been trying to implement an automation via Python SDK but It still has to download from main project to then upload to the new versioned project.
Is it possible for my to automatize this somehow?
Is it possible to clone the project, and bu that I mean not having to download to later upload again the translation files?
I am Antonis from the Transifex Customer Success team.
As I understand your current workflow, you create different projects for different versions, if not, please correct me. Can you keep a single project and create new resources, or does this not match your workflow? This would allow you to use TM fill-up to copy any matching translations instead of doing this manually.
If you are on the premium plan and above, you could also create a Translation Memory group that could connect all your project’s Translation Memory so you could keep your current workflow.
Please let me know if any of the above was helpful, and if you have any further questions, I will be happy to assist you.
Each version (i.e. each Transifex project) contains more than 500 resources with a total of 24K source strings. Putting them all together would make harder to query strings, to filter what resource from which version I’m looking for.
The projects already have TM fill-up on and, unless I’m reading it wrong, the translations in project are replicated to previous version if there wasn’t a string change between versions. At least, whenever I translate a new string that was also backported to previous version, I see an entry in Suggestion from that previous version.
Hi @Mylon is it possible that the “old” translation memory propagation has been switched off? It previously worked across projects in Python documentation organization, and apparently (not sure for how long though) it now doesn’t work.
@m-aciek Currently we have Translation Memory Fill-up enabled for all projects. However, I just learned that sharing translation memory between projects of a organization requires creating a “translation memory group” which is requires a Premium subscription.
That means we have several projects available that are not making use of translations done in the newest project. Great disappointment.