Jacob makes good points, but I used the information that in the previous
links.  When using the WixStdBA, since as you found "the bootstrapper is
correctly switching to the localized 1046\thm.wxl and 1046\license.rtf" you
can take advantage of that fact by:
1) define a Variable element which is overidable  (I give several examples
because I use the first as an InstallCondition for separate localized
packages, and the second as a MsiProperty for a MSI which has external
transfroms as Payloads.)

    <Variable Name='UsingThisLCID' Value='1033' Type='string'
bal:Overridable='yes' />
    <Variable Name='MyAppNeedsThisTransform' Value='1033.mst' Type='string'
bal:Overridable='yes'     &lt;Variable Name='MyEmbeddedTransform'
Value=':1033.mst' Type='string' bal:Overridable='yes' />

2) In your Bundle's wxl files (when using WixStdBA) have code like this:
<?xml version="1.0" encoding="utf-8"?>
<WixLocalization Culture="fr-FR"
                 Codepage="1252"
                 Language="1036"
                 xmlns="http://schemas.microsoft.com/wix/2006/localization";>
  <String Id="UsingThisLCID">1036</String>
  <String Id="MyAppNeedsThisTransform">1033.mst</String>
  <String Id="MyEmbeddedTransform">:1033.mst</String>
</WixLocalization>

3) For different localized MSI packages use a MsiPackage like this:
  <Fragment>
    <PackageGroup Id='MyApp_fr_FR'>
      <MsiPackage Id='MyApp_fr_FR'
                  Vital='yes'
                  Compressed='no'
                  DownloadUrl='myUrl{2}'
                  SourceFile='fr-FR\MyApp.msi'
                  Name='MyApp\MyApp_fr-FR.msi'
                  InstallCondition=' UsingThisLCID=1036 '                >
        <MsiProperty Name='INSTALLFOLDER' Value='[InstallFolder]' />
      </MsiPackage>
    </PackageGroup>
  </Fragment>

The key point here is InstallCondition, but another issue that I had when
creating a Bundle driven MSI in multiple languages, was the layout under the
bundle's folder different msi packages in specific languages have the same
name.  My solution was to use the MsiPackage/@Name attribute to rename the
msi package,  I prefer to put all of the above MsiPackage fragments in a
wixlib and include a fragment like this, so that I only have to include one
PackageGroupRef in my Bundle's chain (as I use the msi in several bundles):
    <PackageGroup Id='MyApp'>
      <PackageGroupRef Id='MyApp_de_DE'/>
      <PackageGroupRef Id='MyApp_en_US'/>
      <PackageGroupRef Id='MyApp_es_ES'/>
    </PackageGroup>

For my MSI package which has external transforms, I do this (in a small
nutshell <Smile/>): 
        <MsiProperty Name='TRANSFORMS' Value='[MyAppNeedsThisTransform]' />
And include the transform files as Payloads with the MsiPackage.

I hesitated to provide the Embedded example since you are using Burn.  I
spent a lot of time using embedded transforms only to discover some problems
that could not be resolved, when 'on-demand' installs take place.  In  this
thread
<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-td7596896.html#a7596923>
  
Rob indicated at using embedded transforms in the manner I was doing it is
not supported.  So I switched to the above method of building separate
localized msis and using InstallCondition to control which MSI should be
installed.  I used to use WixStdBA in this manner, but I now have a mba and
code in the mba which detects the threads current culture and selects which
localized msi to include in the plan (pretty much the same idea as about but
without the wxl files). 






--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-burn-bootstrapper-access-lang-as-a-property-or-variab-le-tp7599256p7599259.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to