Hello,
I need to localize my setup again for every new version, this nerves. In a new version only some files are changing, so I put in the new files, change the version and after changing version I have to add the other languages again. Why?
If I try to import my already worked on localizations IA tells me that the localization doesn't match the version, so I have to export strings again and then auto translate and then edit the strings again for all my languages and then import. This is much work but it would not be necessary, I think because the script doesn't change...Is there a workaround for this?
Amendment: Is it enough to rename the mtx file?
[WHY] Do I have to localize for every version?
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Re: [WHY] Do I have to localize for every version?
Obviously you're changing some more than just files, if your existing translations aren't being picked up. If you are renaming your project, yes, try renaming the MTX file.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
Re: [WHY] Do I have to localize for every version?
This seems to happen to me as well if I add any new strings to my setup. When importing previous translations translations get all messed up.
Are you planning on improving the translation management in a future version?
It would be nice to have the translation strings editable within the project and not require a separate app for managing them.
Are you planning on improving the translation management in a future version?
It would be nice to have the translation strings editable within the project and not require a separate app for managing them.

