So Phill, did you have a chance to try any of these suggestions and/or WiX
3.8 to see if you can get the Burn wrapper .exe to launch correctly in the
language of the OS?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi
[mailto:phogl...@rimage.com]
Sent: 12 August 2013 21:58
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] multi-language bundle - A BIG THANKS
I assume that your (Neil's) description of the WiX language detection behavior
applies to 3.8, because I have not observed that behavior
I assume that your (Neil's) description of the WiX language detection
behavior applies to 3.8, because I have not observed that behavior with WiX
3.7. For me with 3.7 I always have to use -lang LCID to see any of my
supported bundle translated strings. So far I have only tested using
Windows 8 Pr
Thanks for the idea. I will try that.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-tp7208949p7587954.html
Sent from the wix-users mailing list archive at Nabble.com.
---
multi-language bundle - A BIG THANKS
Yes, we support seven languages. If I pass UserLanguageID or SystemLanguageID
in my var "LCID" and then pass it as a property to the MSI package in the form
of TRANSFORMS=LCID.mst all is well for the supported languages, however an
unsupported lang
Yes, we support seven languages. If I pass UserLanguageID or
SystemLanguageID in my var "LCID" and then pass it as a property to the MSI
package in the form of TRANSFORMS=LCID.mst all is well for the supported
languages, however an unsupported language results in an error because the
transform doe
Okay thanks, If 3.8 does correctly detect OS language and launch Burn wrapper
in detected language then that should solve part of that issue.
As for your 2nd issue, are you talking about conditioning your MsiPackage so
that it will only use your supportted language .mst's that you need to pass
to
I am trying to solve that same issue, so I do not have a solution yet. I was
in the process of importing the 'extended bootstrapper' and writing a
BAFunction.dll to try and get the language of the UI to be the same as the
OS UserLanguageID and also address an issue where I need to restrict which
L
Phill/Alnoor
I had to make a few more adjustments to my code to match what you have, but
it will still only launch in English when running on a French OS. If I use
the command line option -lang 1036 then the Burn wrapper will correctly show
UI and License in French.
So how do I get it to show the
Well I got it working. As posted earlier I added a modified
HyperlinkTheme.xml to my 1031 subfolder, and originally I added this Payload
statement:
"
"
The bundle project builds but when run it does not display any dialog and
the log file shows error creating the main window (as reported in the
Cool, thanks. If worst comes to worst, I'll just fire up Process Monitor
again and watch the file system activity to see what files the bootstrapper
is looking for (and not finding.)
Somehow, that feels more fun than wading through source code.
Alnoor
--
View this message in context:
http://w
It looks like the answer to loading a localized xml file is here:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Localized-bundle-Picking-up-the-right-files-td7265208.html
I have not tried it yet, but he is correct that I did not have the png file
in each localized folder.
--
Vie
My experiments so far do not work. I added:
"
"
And made various changes to only that xml file, but so far it has not picked
it up. I was just starting to read through the source code, but do not have
anything figured out yet. Anyway the big issue was getting the translated
strings int the dial
Hi Phil,
Glad to help, and thanks for the suggestions. It does make sense to localize
the theme itself, though I have not done so yet. Did you try it?
Alnoor
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-b
This is VERY COOL.
I am working on my first WiX bundle and was just getting to the point where
I need to get it working in JEFIGS +Ch Simplified. I quickly implemented
the steps you posted with the one exception that I created a Payload entry
for a 1033 sub folder, which it uses by default rather
15 matches
Mail list logo
