There are a variety of reasons that you may need to translate a string differently in different contexts, or places, in a VPME Multilingual application. For example:
· A string in the Master Language that fits the space available on a form and on a report may be too long for, say, the report when translated into another language. In this case, you would need a translation for the string that fits on the form and an abbreviated translation that fits on the report.
· A string in the Master Language may fit appropriately in different contexts (for example, different forms), but in another language the different contexts may require different translations.
The keys to creating and using alternative translations for the same string are (a) the “Use ID” associated with the string in the CUSEID field of the String and String Translations records and (b) the Use ID passed to the VPME Multilingual string translation engine when the string is translated. In other words, creating and using alternative translations for a string is a two step process:
1. Create Use ID: You create multiple String and String Translations records for the string using the Use ID field to differentiate between the alternative translations.
2. Pass Use ID: Where the string is translated, you make sure that the VPME Multilingual string translation engine is passed the Use Id value that will return the translation needed.
Let’s talk about this in more detail.
Creating Alternative Translations
To create alternative translations for the same string, you must create String records and String Translations records with the same String ID but different Use ID’s.
For example, let’s say you have two forms with “Employees” as their Master Language captions. However, say, in Spanish the string “Employees” should have different translations for the two forms because the context of the forms makes a difference in Spanish. Therefore, you would:
· Create one String record with the String ID “Employees” and a blank Use ID field. Then, create a Spanish String Translations record with the translation you will use when the VPME Multilingual string translations engine is passed the String ID “Employees” with a blank Use ID.
· Create a second String record with the String ID “Employees” and a Use ID field containing, say, “S”. Then, create a Spanish String Translations record with the translation you will use when the VPME Multilingual string translations engine is passed the String ID “Employees” and a Use ID of “S”.