Hi,
I wonder what is the logic behind the shared strings? It brings nothing but troubles.
1. If you have more than one product, editing the shared strings makes no sense because it will be automatically visible in every product you have. Stupid.
2. If you have 2 products and only 1 of them is going to be localized, the other one will be localized as well... In my case the customer should never see the other languages... even in the installer.
3. It seems that IA copies the shared strings to the files called shared.translations.language during the "Single file" build. Why not to use ONLY this files from now on? Instead they are overwritten every time the build is started.
Generally I think it is a biggest flaw of IA. Why is it so weird?
Best regards,
adi
What is the reason for shared strings?
-
MichaelNesmith
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Re: What is the reason for shared strings?
Shared strings are for generic installer messages that actually never should need to change from project to project. Thus, shared strings.
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: What is the reason for shared strings?
Hello,
Great... after updating to InstallAware 9 R2 the shared strings are restored to default...
Couldn't the installer at least keep the old ones? Or warn that they will be lost?
Best regards,
adi
Great... after updating to InstallAware 9 R2 the shared strings are restored to default...
Couldn't the installer at least keep the old ones? Or warn that they will be lost?
Best regards,
adi

