mst dialog content missing after msi compile
Hi.
I have created a MSI and a couple of language mst:s and then I get a translated install depending on the selected language when executing a wise script exe. All the mst:s are created by the "standard" process in the Windows Installer Editor, Installation Expert - language section. Exe created under Build options.
Problem is, when i edit my project (wsi) and compile, all content in the mst dialoges disappears. I do not want to create the mst:s again (or recreate them) during compilation so all languages are unchecked. I have manually edited text in the mst:s, because the wise standard translations does not always "fit like a glove" so to speak. And I also had to add new dialoges and those will not be translated, so there is another need for manual editing.
If i check the languages in the wsi file and compile i get new standard translated mst:s (with messed up positions in the dialoges etc) and my changes are of course overwritten.
Is it supposed to be like this? Because in that case there is no way to edit the msi after the creation of the language mst:s, for example an update of a file. Big problem...
Im using Wise package Studio 7.
Edit: The dialoges in the mst:s also lost the [_WiseDialogSuffix] property in the dialog title when looking at the dialog details.
I have created a MSI and a couple of language mst:s and then I get a translated install depending on the selected language when executing a wise script exe. All the mst:s are created by the "standard" process in the Windows Installer Editor, Installation Expert - language section. Exe created under Build options.
Problem is, when i edit my project (wsi) and compile, all content in the mst dialoges disappears. I do not want to create the mst:s again (or recreate them) during compilation so all languages are unchecked. I have manually edited text in the mst:s, because the wise standard translations does not always "fit like a glove" so to speak. And I also had to add new dialoges and those will not be translated, so there is another need for manual editing.
If i check the languages in the wsi file and compile i get new standard translated mst:s (with messed up positions in the dialoges etc) and my changes are of course overwritten.
Is it supposed to be like this? Because in that case there is no way to edit the msi after the creation of the language mst:s, for example an update of a file. Big problem...
Im using Wise package Studio 7.
Edit: The dialoges in the mst:s also lost the [_WiseDialogSuffix] property in the dialog title when looking at the dialog details.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
polkagris
13 years ago
It is the control table in the mst that is completely wiped, when opening the mst after the msi has been compiled .
I have no idea (yet) if this is standard behaviour or if I have messed something up.
I have no idea (yet) if this is standard behaviour or if I have messed something up.
Posted by:
anonymous_9363
13 years ago
What happens if you use the MSI as your base, instead of the WSI? Remember to switch on Wise's back-up feature or back the MSI up before editing it.
Posted by:
polkagris
13 years ago
You mean edit and compiling the msi instead of the wsi? I will try that first thing tomorrow, I'm out of office now.
But the control table info/content is still there.......somewhere. If I apply the mst on the msi with Orca.....voila....the control table isnt empty. And after generating the transform in Orca, I got a mst that shows the dialog content in wise again, with all my manual translations and manual editing.
But the control table info/content is still there.......somewhere. If I apply the mst on the msi with Orca.....voila....the control table isnt empty. And after generating the transform in Orca, I got a mst that shows the dialog content in wise again, with all my manual translations and manual editing.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.