It has been over a year since I tackled that issue with the help of folks
here. This thread
<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-bundle-td7208949.html#a7587949>
is on the same issue. I know we got it to automatically detect the
language, after I upgraded from wix 3.7 (which had a bug). Also you will
notice in that thread that part of my issue was that I did not understand
how the changes in the behaviour of Win 8 (in contrast to Win 7) was
affecting the issue.
Make sure that you define you WixLocalization element to specify the correct
Culture, Language, and Codepage. Then add additional String elements which
you can then use to signal your BA or use in MsiPackage conditions. This
example is from one of my localized MSI projects, so you would not need the
SummaryCodepage in a Bundle project. But you might have something like:
<String Id="msiTransfrom">1041.mst</String>
<?xml version="1.0" encoding="utf-8"?>
<WixLocalization Culture="ja-JP"
Codepage="932"
Language="1041"
xmlns="http://schemas.microsoft.com/wix/2006/localization";>
<String Id="LCID">1041</String>
<String Id="Codepage">932</String>
<String Id="SummaryCodepage">932</String>
<String Id="DownVersionErrorMsg">[ProductName]
の新しいバージョンがすでにインストールされています。</String>
</WixLocalization>
Make sure you set the culture property in VS (or on the command line of
light) for the bundle project.
You can do it in the IDE as described here
<http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/specifying_cultures_to_build.html>
, or just edit the wixproj file to include something like:
<Cultures>en-US;de-DE;es-ES;fr-FR;it-IT;ja-JP;zh-CN</Cultures>
The WixStdBA will detect what the SystemLanguage is set too (IIRC), so on
Windows 8 I always get tripped up on how to configure that, but I then get
it worked out.
Use ProcessMon
<http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx> and watch
where you BA tries to load the lcid named resources. When you do not
provide the -lcid switch you will see that it will try to find a resource
and if it cannot find the resource it will drop back to the default (which
is what is sounds like it is doing for you.) Just guessing.
I did not see anything wrong with what you posted, based on my vague memory,
but I don't know how your wxl is defined. I also defined a wxl for my
default culture (en-US) as I needed to use the string that I created in that
wxl file to control the MsiPackage conditions for the en-US package.
I switched to creating a mba long ago so now I detect the culture in my BA
based on the cuture of the thread and use that info to select which culture
specific MSI to installed. So sorry that I do not remember all the details
of using the WixStdBA.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-for-multiple-cultures-tp7598840p7598872.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
