In article <[EMAIL PROTECTED]>,
    "Mike Dimmick" <[EMAIL PROTECTED]>  writes:

> [...] Microsoft have used this approach before and it's the
> recommended one in the SDK. See "Localizing a Windows Installer Package" at
> http://msdn2.microsoft.com/en-us/library/aa369769.aspx.

This thread had me looking at localization support in Windows
Installer again and I can't find on this page where it talks about
transforms or recommends using a bootstrapper with transforms as the
way to localize a package.  I know InstallSUCK does it this way, but I
thought that Windows Installer allowed you to embed multiple language
transforms into the package and apply one based on the system
language?  Someone (you, perhaps?) referenced an InstallSite article
that described this process but noted that it was unsupported.

This seems the reverse of what I remember reading in the SDK
documentation, but I'm getting old now :-).
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
      <http://www.xmission.com/~legalize/book/download/index.html>

        Legalize Adulthood! <http://blogs.xmission.com/legalize/>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to