Localized folder locations in Vista
Posted: Mon May 21, 2007 4:39 am
We ship our setup in three languages: English, French, German
When testing on a German Windows Vista installation we observed that the folder location in the tree view and the one in the edit control do not match. This might confuse users or lead them to manually correct a location when this is not necessary.
To reproduce this issue with InstallAware 6.6 follow these steps:
- Get Folder Location System->ProgramFiles Directory into PROGRAMFILES
- Set Variable TARGETDIR to $PROGRAMFILES$\\$TITLE$
- Use a PTShellTree on your form, cf. e.g. destination.dfm
- Use a non-English installation of Windows Vista to run the built setup
- When asked to choose a location the folder names in the tree view are localized (e.g. C:\\Programme on a German Vista installation), while the edit control shows the non-localized location (e.g. C:\\Program Files).
- Both the localized and the non-localized folder names are accepted by setup and lead to correct installation in the desired location
However, the setup experience could be improved if both displayed locations matched. We do not intend to build a custom dialog or write a plug-in to circumvent this problem somehow.
Is it reasonable to expect this issue to be fixed in a future 6.x release?
When testing on a German Windows Vista installation we observed that the folder location in the tree view and the one in the edit control do not match. This might confuse users or lead them to manually correct a location when this is not necessary.
To reproduce this issue with InstallAware 6.6 follow these steps:
- Get Folder Location System->ProgramFiles Directory into PROGRAMFILES
- Set Variable TARGETDIR to $PROGRAMFILES$\\$TITLE$
- Use a PTShellTree on your form, cf. e.g. destination.dfm
- Use a non-English installation of Windows Vista to run the built setup
- When asked to choose a location the folder names in the tree view are localized (e.g. C:\\Programme on a German Vista installation), while the edit control shows the non-localized location (e.g. C:\\Program Files).
- Both the localized and the non-localized folder names are accepted by setup and lead to correct installation in the desired location
However, the setup experience could be improved if both displayed locations matched. We do not intend to build a custom dialog or write a plug-in to circumvent this problem somehow.
Is it reasonable to expect this issue to be fixed in a future 6.x release?