You should use .wxl (WiX localization) files for, well, localization. It
takes a few tricks to get them working, but then it's smooth sailing.
My main WiX project directory is setup something like this Everything is
stripped down for public consumption, and I am just doing English right now,
but the picture is correct:
..\WiX\ant_wix.xml <-- I build with ant, was using it pre-WiX
..\WiX\lang
\en-us\proj_en-us.wxl
\License.rtf
\de-de\proj_de-de.wxl
\License.rtf
..\WiX\src
\proj1.wxs
\proj2.wxs
\frag1.wxs
..\WiX\wixobj
..\WiX\wixlib
..\WiX\Packages
\en
\de
The en-us .wxl file is something like this:
<?xml version='1.0'?>
<WixLocalization Culture='en-us'
xmlns='http://schemas.microsoft.com/wix/2006/localization'>
<String Id='LANG'>1033</String>
<String Id='Company'>MindCapers</String>
<String Id='ProductName'>SomeProductName in English</String>
...
</WixLocalization>
To access from within a .wxs file:
<Package Description='!(loc.ProductName)'
Comments='!(loc.ProductName) v1.0'
Manufacturer='!(loc.Company)' InstallerVersion='200'
Compressed='yes' />
To build, it's just the light command line that needs to have this added:
-cultures:en-us -loc "lang\en-us\prod_en-us.wxl"
-dWixUILicenseRtf="lang\en-us\License.rtf"
For each language of course. I also change the output directory to reflect
the localization, like so:
-out "Packages\en\prod_v1.0.msi"
As I mentioned, many steps, but worth the refactoring if you need to
localize to several languages
Julie Campbell
[EMAIL PROTECTED]
-----Original Message-----
Message: 2
Date: Wed, 21 Nov 2007 20:42:11 +0800
From: Abhradeep Thakurta <[EMAIL PROTECTED]>
Subject: [WiX-users] Problem with localization of product name
To: "[email protected]"
<[email protected]>
Message-ID:
<[EMAIL PROTECTED]
microsoft.com>
Content-Type: text/plain; charset="us-ascii"
Hi,
Can you please help me in finding out a way to localize the product name.
We have used the technique of using .wxi (where the strings are defined as
?defined ? ) file which in turn gets localized but this is not accepted by
Microsoft Loc Studio 4.6 . So can u suggest a work around ?
Thanks and Regards,
Abhradeep Guha Thakurta
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs. For
more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
