Languages and Translations

Navigation:  »No topics above this level«

Languages and Translations

Previous pageReturn to chapter overviewNext page

Q++ Languages are similar to real-life languages, but have 2 important advantages :

 

Q++ languages are general : For example, that means that you can create a "Coca-Cola" language that will let you specify the way this client wants text to be translated. For example they might want the "priority" at the top of each day to say "important" instead.

 

Q++ Languages fit in a hierarchy : In the example above, if the "Coca-Cola" diary was in English, you certainly would not want to create a "Coca-Cola" language and then type in all the English translations of all tokens, just to differentiate "important" from "priority".

 

You could have Q++ make a copy of the language, and then only modify "priority" in this copy. However if you have many customized jobs, this sort of inefficient duplication could quickly eat up disk space and slow down access to a database becoming bloated. None of the above is necessary. In the above example, you would just need to create the language "Coca-Cola". Then in the Tokens Manager, you would simply translate "priority" into "important" for that language. Nothing else.

 

 

If Q++ does not find a translation for a particular token in a language, it looks for that translation in the languages parent, and so on and so forth until it reaches the root language Q++ Defaults.

 

The Q++ Defaults Language : If Q++ does not find a translation for a particular token in a language, it looks for that translation in the languages parent, and so on and so forth until it reaches the root language Q++ Defaults. There are few built-in token translations for Q++ Defaults, but it can be very useful to ensure that your diaries follow your corporate guidelines.


Topic 104039 updated on 07-Apr-2003.
Topic URL: http://www.qppstudio.net/webhelp/index.html?thelanguageshierarchy.htm