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

  • Thank you for the quick reply. I will get back to you if we have more questions.

  • 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.

  • Hi,

    We agree the agile development is taking more and more space in the industry and the localization process needs to adapt quickly also.

    We are evaluating an integration with different code repositories. As the .Net parser is very popular and this is usually used togheter with Microsoft technologies we were looking at TFS in the first place.

    Can you give us more details

    - on the workflow you are using

    - which steps you find useful to automate between the repository and Passolo

    - how is your development environment set-up i.e. Git with Microsoft Visual Studio?

    Thank you

    Florina

  • Hi David, we strongly believe that 2 years from now, Continuous Delivery and multi-branching will be the norm for most software companies like us. Other companies provide TMS systems that allow working in such environment.

  • Hi,

    As David said, this is not in the scope of TMS but.... we do look increasingly at the particular needs of software translations and I would like to thank you for raising this here as it helps us shape what will get done in this area.

    The Passolo Ideas area is a good place for such Agile software localization needs, even if the solution itself might not mean a Passolo application evolution but something else (stay tuned).