Legacy system replacement

Hi there,

 

In my company, we need to translate a large set of terms for several different languages. Our applications are developed in several technologies (C#, Java, Html, etc.) and we need to translate all the textual elements.

Right now, we have a process on build to extract all the application terms, so that they can then be used in our translation support software (Trados). After translation, the translated files are sent back to the applications.

We have an automatic translate system for all the applications for all the languages we need to support. The process run on build and is totally developed in house. This process need a lot of maintenance and is very susceptive to bugs. Because that I’m trying to prove that SDL can replace our entire flow. For example, we want to use the API extraction methods for the different sources (*.js, *.properties, DB, ect.).

 

Is this replacement possible to be done with SDL? Can anyone give me a hand on that?

 

Regards,

Sérgio Neves

Parents
  • Based on what you described is hard to imagine that you would find an off-the-shelf product that would be able to replace your custom workflow. In terms of software localization SDL has a solution named Passolo that could help you a lot in what you are looking to achieve so I suggest to have a look. 

    In terms of using the API you can definitely use the Studio File Type API to build filters that would be able to proper parse your custom files like *.js or *.properties but this would still require a custom solution built in house (building those custom filters). Maybe I didn't understand correctly your question in the first place but this looks like replacing a custom solution with another ...? 

    Romulus Crisan | Translation Productivity Development Manager | SDL | (twitter) @cromica_82 | (blog) http://www.romuluscrisan.com/

Reply
  • Based on what you described is hard to imagine that you would find an off-the-shelf product that would be able to replace your custom workflow. In terms of software localization SDL has a solution named Passolo that could help you a lot in what you are looking to achieve so I suggest to have a look. 

    In terms of using the API you can definitely use the Studio File Type API to build filters that would be able to proper parse your custom files like *.js or *.properties but this would still require a custom solution built in house (building those custom filters). Maybe I didn't understand correctly your question in the first place but this looks like replacing a custom solution with another ...? 

    Romulus Crisan | Translation Productivity Development Manager | SDL | (twitter) @cromica_82 | (blog) http://www.romuluscrisan.com/

Children