Kbase P13699: Possible cause for lost translations with Translation Manager
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
GOAL:
Possible cause for lost translations with Translation Manager
FACT(s) (Environment):
Progress 8.x
Progress 9.x
FIX:
It is important to note that when an application changes, procedures and strings get re-loaded. If an object is deleted and a new one created with the same label, it does not automatically inherit the previous translation. The applications procedures and strings need to be reloaded so that changes can be detected. Then a pre-translation can be done to re-apply translations to new/changed objects. Then, finally, all new strings need to be translated. You cannot consolidate a kit that was created from one Translation Manager project into a different project, as it will most likely lead to corrupt translations.
Here is an example of what should happen:
In the AppBuilder, create an application with 5 buttons (labeled one, two, three, four, five)
In Translation Manager, create the new project, add the file, extract, filters, load and resources as you were doing before.
- Create the glossary and a kit and a zip file.
In Visual Translator, install the kit (using zip file) and add the translations you specified:
one -> uno
two -> dos
three -> tres
four -> cuatro
five -> cinco
- Create a return kit
Back in Translation Manager, install the return kit and consolidate. When you compile and build then it will translate correctly.
Now, in the AppBuilder, change the application as follows:
1) Delete buttons three and four
2) Rename button two to four
3) Add new buttons three and six
*** At this point in time it is important to realize that the application has changed and so we must scan the procedures for changes (the procedures tab in Translation Manager). We also need to redo the extract, filter and loading of strings (data tab).
*** It is important to re-do this within the SAME project.
This way, Translation Manager detects what is there now and what differs from before. The fact that two buttons were deleted will be detected and those translations will be thrown out. All of the sequence numbers will correctly be lined up with the appropriate strings. Also, the changes you made to the glossary will still be in this project (for example, that 'one' should be translated to 'uno'). Once the reloading of procedures and strings is finished, you can do the following:
Tools -> tranman Utilities -> pre-translate (this will assign translations to the strings that have matches in the glossary so you don't have to re-do all of those).
At this point if you rebuild and run then you will see that the buttons are translated correctly. The only one that is not translated is 'six' because there are no translations for it.
In order to translate it, you must add it via VT (creating a kit etc...) or add it to the glossary manually and do a pre-translate.
Remember all of this must be done in the same project.