Not Considering

Branching

Currently, SDL TMS does not support multi branching.

When it comes to approach a localization project that follows Agile methodologies, we lack a solution that helps us monitor a Git/SVN repo to pick from branches new/edited contents.  We need to automate highly-repetitive and low added-value tasks like monitoring the branches, picking up translatable contents, and once translation is complete, putting back the localized files where they belong in the source repo.

Right now, the only solution is to check each branch manually, analyze with Passolo, and if needed, create bundles that we process through TMS. This process is time-consuming and we cannot concentrate on internationalization/globalization questions. 

PB Localization
Parents

  • Hi Florina,

    thank you for your interest in this conversation.

    We are mostly interested in how TMS or Passolo could plug in our GitHub/GitLab repos to browse for branches and allow smooth switching between them, so that we can identify what needs to be translated.

    The big idea is to avoid manual tasks: switching between branches in a tool, start Passolo, check, close Passolo, switch to another branch, isolate files to translate, send manually files through TMS, retrieve translations, etc.

    Our workflow is the following:

    - Navigate between GitHub branches to identify those needing translation

    - Use Passolo to parse language resource files and create bundles

    - Send bundles through TMS

    - Retrieve translations from TMS, import Passolo bundles back

    - Generate target language strings and push back to git

    - Rinse and repeat for all branches

    .net is one of the file formats we are using, but we also use HTMLs, XMLs, JSONs, etc.

Comment

  • Hi Florina,

    thank you for your interest in this conversation.

    We are mostly interested in how TMS or Passolo could plug in our GitHub/GitLab repos to browse for branches and allow smooth switching between them, so that we can identify what needs to be translated.

    The big idea is to avoid manual tasks: switching between branches in a tool, start Passolo, check, close Passolo, switch to another branch, isolate files to translate, send manually files through TMS, retrieve translations, etc.

    Our workflow is the following:

    - Navigate between GitHub branches to identify those needing translation

    - Use Passolo to parse language resource files and create bundles

    - Send bundles through TMS

    - Retrieve translations from TMS, import Passolo bundles back

    - Generate target language strings and push back to git

    - Rinse and repeat for all branches

    .net is one of the file formats we are using, but we also use HTMLs, XMLs, JSONs, etc.

Children
No Data