That's a good one-off solution, but it would be cool if we could create a solution in the extension itself so that everyone can leverage it without additional work.
Putting the license text in the wxl file won't be good enough in WiX 2.0 because there is no ability to override that text. So you'd have to manually modify the wxl file to localize the text (not such a good solution) - plus you'd have to watch out for issues of putting RTF text inside XML like watching out for < and >. The only solution I can think about that might work (I'm still not sure if it would) is to make the "license.rtf" string itself localizable. Even then, you'd still need to modify the wxl file - but only to change a file name, not to replace an entire block of text. That seems a lot safer assuming you continue to take drops of WiX 2.0 and some minor fixes to localized text etc continue to keep trickling in. The only issue is that I'm not sure if the binder architecture of 2.0 would support localizing the location of a license file. Some experimentation would be required. The other option is to move to WiX 3.0. Work on the core of 3.0 is very near completion, however, I'm still nervous about groups using 3.0 that are shipping anytime in 2006. It's not a matter of us churning the schema so much anymore as just a general issue of 3.0 needing some bake time to ensure the major bugs are fleshed out. Derek -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stefan Pavlik Sent: Tuesday, June 13, 2006 6:12 AM To: Albert At School Cc: Wix-Users Subject: Re: [WiX-users] Localized version of License.rtf Hi ... I had several problem (one year ago) and here is my sulution: In main wxs file I have LicenseDialog and one control is : <Control Id="AgreementText" Type="ScrollableText" X="23" Y="80" Width="368" Height="145" Sunken="yes" TabSkip="no" Text="$(loc.License)" /> Then I have script (in ruby) which will copy verbatim the RTF text of the License (in correct language) into corresponding wxl file. The wxl file itself is not very "nice" but it is processed only by scripts so I does not care. Hope it will help regards Stefan Albert At School wrote: >>> Could we please start this discussion on wix-users instead of inside >>> this > bug? It would probably be >>> more efficient to just talk about this there. > > Agreed. > > Ok, can someone tell me how to find a solid solution for Wix2.0 as for > the the problem described below? > Or is it safe enough to switch to Wix 3.0? > > AvP > > -- Stefan Pavlik | [EMAIL PROTECTED] Whitestein Technologies | www.whitestein.com Panenska 28 | SK-81103 Bratislava | Slovak Republic Tel +421(2)5930-0735 | Fax +421(2)5443-5512 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
