Variable content in language files

[mikKummerfeld]

Hello Guys,

when are you going to fix the problem, that very often, the content of variables will be written into the language.text.

E.g
I have a variable which is $versionx$ (content: 1.0.0.31). I increase the variable on every build and this variable of course must not be translated.

But when I open the language manager I find the following:

Original: 1.0.0.31
Translated: 1.0.0.18

sssss.png (3.98 KiB) Viewed 5121 times

This is very very bad, because when I am at 1.0.0.31, the compiled setup.exe still shows 1.0.0.18 in GUI.

Problem occures in IA Trans Manager and TransManager Pro

Heiko

[FrancescoT]

Dear Heiko,

I really believe that you are not using InstallAware correctly.

When an IA project uses translations, every time you update the string project resources (... as your Version variable and as well any other variable and Dialogs resource), you shoud export strings project to translator (... with the provided IA localization wizard).
Doing this and selecting to export the updated strings only (if not already exported), you will have all the strings updated.

Regards.

[mikKummerfeld]

I do that this way. I export always after inserting some labels, etc and then translating and insert to project.
This is a bug...

1. Changing labels, radiobuttons, titels etc in the dialogs
2. Export using your wizard (first option) with preserve to D:\projects\projectname\translation
3. Open TransManager and translate new texts or existing ones
4. Import using you wizard (third option) and overwrite existing resources

[FrancescoT]

Dear Heiko,

Now I see what you mean ... and I found the same.

Let me verify it with the dev team.

Regards.

[mikKummerfeld]

Ok thank you. For me with hundreds of variables like this, is very annoying...
I have now about 17 different setup projects...

[FrancescoT]

Dear Heiko,

it works in that way because export to translator process, if it is used preserving existing translations, keeps the first assigned language value.

When you export for the first time project string resources, the value assigned for a variable or a resource, are assigned as well to the language resource.
Due of this, exporting again project string resources preserving existing translations, the Wizard translator just does what it supposed to do and keeps the previous translation. To verify what I'm saying, use the "mTranslator.exe" IA tool to inspect translation resource files contents.

I use as you "Translation Manager Pro" with my personal project and honestly, I overwrite always existing translations and then I use the translate command to immediatelly restore translation.

I suppose that "Translation Manager Pro" probably uses a different approach when displaying string translations and it represents as empty, those that contains the same original string ... but in reality it not true.

I hope this clarify any doubt.

Regards