In our last post, we talked about how we deal with software variants in localization projects. As far as software goes, you have roughly two cases:  the software is translated and available in various languages. OR, the software is not translated and only exists in English.  A third case is that the software consists in several modules, and not all modules are translated, and the display will then be a mix between source English and target translation, depending on the functionalities that are used.

In this case, we have to define a rule regarding which of these variants will apply to projects.  This rule can be established per language, or per product, or per type of content, or can result from a mix of these three parameters. So long there is no clearly established rule, customers shall indicate which variant shall apply to the localization projects they send.

Moreover, in some localization projects, customers may find that untranslated content are documents, multimedia content, etc. Then, how to we proceed the localization?

Well, the same rule applies. Depending on our customers, there are still four variants: it can be either translated, or left in English, or put in English with a translation in parentheses – English (translated), or translated with the English source mentioned in parentheses – translated (English). Customers shall indicate which variant shall apply to your project, although the bilingual ones are quite never used, except for short links.