Using different language than english

[Peter Tarkkonen 0]

TMG has a very powerfull tool; Lauguages. This is most probably needed by those who live in different language area than those which come with TMG.

 

With this possibility it is easy to create new language and translate several phrases etc. used f.ex in Journal report.

 

However, whenever new upgrade is installed, one has to think should I use new language file or keep the old one which has allready been translated. I any case once and a while latest translate file should to be taken in use.

 

Now to minor problem which this "upgrading" generates. By this upgrade all translations will be deleted (overrun) and language has to be recreated and all translations has to be entered again.

 

I do not personally have too many translation which I have done, maybe only 100, but I have to remember them because old files do not exists anymore.

 

Is there a possibility to scroll thru exported language file or maybe print changes made. If only I could print those lines which were translated, at least I could live with it.

 

Peter

[GenerationGoneBy 0]

Peter,

I don't know. It would be nice if there was a way to keep our old ones and compare so that we could decide which to keep and which to update. In the meantime, would a file in a word processor help. You could have two columns, one for the words and another for what you changed them too. THen you could compare them once you upgrade. Since I use English two, I just exported my file out, and after the update, I import it back in, but that might not work for a language that's being translated.

[Peter Tarkkonen 0]

Peter,

I don't know. It would be nice if there was a way to keep our old ones and compare so that we could decide which to keep and which to update. In the meantime, would a file in a word processor help. You could have two columns, one for the words and another for what you changed them too. THen you could compare them once you upgrade. Since I use English two, I just exported my file out, and after the update, I import it back in, but that might not work for a language that's being translated.

 

Hi!

 

Even a Word file would work with me because I have not translated too much, only phrases needed in Journal report. Ofcause it would help if this Word file includes only those lines which really has some translation. This would keep the list much shorter.

 

If I have undertood correctly, by importing translation back, you replace existing translation file with old one. And that would mean that some words/phrases needed by new revision does not exists at all?

 

Peter

[Jim Byram 0]

Peter,

 

The standard procedure is to export your custom language before installing the program update. Then the language file can be updated when the program is updated. After the program update, you import your custom language and can then translate the added strings.

 

The reason for using this procedure is that if you had an installer option to update the language file or retain the current language file, you would not get the new strings in the language file if you chose to retain the current file. That's why the export/import procedure is required.

 

Terry has some articles on his site regarding using custom languages.

http://tmg.reigelridge.com/Language.htm

 

Jim

[Peter Tarkkonen 0]

Peter,

 

The standard procedure is to export your custom language before installing the program update. Then the language file can be updated when the program is updated. After the program update, you import your custom language and can then translate the added strings.

 

The reason for using this procedure is that if you had an installer option to update the language file or retain the current language file, you would not get the new strings in the language file if you chose to retain the current file. That's why the export/import procedure is required.

 

Terry has some articles on his site regarding using custom languages.

http://tmg.reigelridge.com/Language.htm

 

Jim

 

Jim,

just want to be sure I understand this right.

Export/import procedure only import "translated strings", not whole file?

Peter

[Jim Byram 0]

Export/import procedure only import "translated strings", not whole file?

Right. Only the language(s) that you are working with.

 

The point of allowing the update replacement of the language files is to get all of the changes coming from Wholly Genes when the program is updated and the language file is updated. The English part is updated by the programmers as the program changes. The translations for the other standard languages are constantly updated by the various translators. You want to get those changes each program update.

 

And use the export/import procedure to maintain your personal changes (for whatever language you are customizing).

[Peter Tarkkonen 0]

Export/import procedure only import "translated strings", not whole file?

Right. Only the language(s) that you are working with.

 

The point of allowing the update replacement of the language files is to get all of the changes coming from Wholly Genes when the program is updated and the language file is updated. The English part is updated by the programmers as the program changes. The translations for the other standard languages are constantly updated by the various translators. You want to get those changes each program update.

 

And use the export/import procedure to maintain your personal changes (for whatever language you are customizing).

 

Thank you!!

 

You just made my day!

 

Peter

[GenerationGoneBy 0]

Peter, I am glad Jim could explain it better. I just know it works for my ENGLISH2. I have some things translated from English to another word in English and like you, wouldn't want to have to keep up with the changes.