>> 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


-----Oorspronkelijk bericht-----
Van: Nobody [mailto:[EMAIL PROTECTED] Namens
SourceForge.net
Verzonden: maandag 12 juni 2006 19:48
Aan: [EMAIL PROTECTED]
Onderwerp: [ wix-Feature Requests-1503405 ] Localized version of License.rtf

Feature Requests item #1503405, was opened at 2006-06-09 02:40 Message
generated for change (Comment added) made by derekc You can respond by
visiting: 
https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1503405&group_i
d=105970

Please note that this message will contain a full copy of the comment
thread, including the initial issue submission, for this request, not just
the latest update.
Category: wixui
Group: Already Exists
Status: Closed
Priority: 5
Submitted By: The Mad Butcher (mad_burcher) Assigned to: Derek (derekc)
Summary: Localized version of License.rtf

Initial Comment:
Hi all,

Isn't it an idea to specify a localization string for the 'License.rtf'
file?

eg use something like $(loc.LicenseFile) in the UI wxs files and in the
WixUI_en-us.wxl you specify:
<String Id="LicenseFile">License.rtf</String>

for the dutch version this can be:
<String Id="LicenseFile">Licentie.rtf</String>

for the other versions you can imagine the idea ;-)

Greetings,

Albert van Peppen


----------------------------------------------------------------------

>Comment By: Derek (derekc)
Date: 2006-06-12 10:47

Message:
Logged In: YES
user_id=518766

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.

----------------------------------------------------------------------

Comment By: The Mad Butcher (mad_burcher)
Date: 2006-06-12 04:49

Message:
Logged In: YES
user_id=295880

Hi,

The suggested solution look solid; however: I still use the
(stable) 2.0 version... In 2.0 it is not possible to use this solution (as
far as i can tell).

I am willing to convert to 3.0 but then i need to be sure this version works
safe for my clients and since it is not yet in a stable state i am a bit
scared it will work in all situations.

Any more suggestions? (beside overriding the standard LicenseAgreement
dialog)


----------------------------------------------------------------------

Comment By: Derek (derekc)
Date: 2006-06-11 15:02

Message:
Logged In: YES 
user_id=518766

That's a good point.  Several different aspects of the
UIExtension changed for 3.0 and there are still a few more
changes needed before things can be properly documented.  I
think it would be a good idea to open a general doc bug
against how to use the UI extension in 3.0.  Please don't
assign it to anyone though - that's going to be quite a
large work item.

----------------------------------------------------------------------

Comment By: Frederik Carlier (fcarlier)
Date: 2006-06-10 02:57

Message:
Logged In: YES 
user_id=1149415

That sounds really cool, but is it documented already? 
>From what I see in CVS:

http://wix.cvs.sourceforge.net/wix/wix/src/chm/html/WixUI_di
alog_library.htm?revision=1.3&view=markup

it is not, so it may be worth reopening it as a doc issue?

----------------------------------------------------------------------

Comment By: Derek (derekc)
Date: 2006-06-09 14:16

Message:
Logged In: YES 
user_id=518766

The method you describe below of putting a license.rtf file
in the same directory as the wxs source file no longer works
with the latest builds of the WixUIExtension.  That method
is a bit dangerous because it could accidentally pickup a
file unintentionally and its also inflexible because you can
only specify one license.rtf file (which doesn't work for
localization as you've found out).

However, both of these issues are now solved.  With the
latest builds, you can override the license text in one of
two ways:

In authoring:
<WixVariable Id="WixUILicenseRtf"
Value="$(env.WIX)\examples\data\test.txt" />

Via the command line:
light.exe
-dWixUILicenseRtf=c:\delivery\dev\wix\examples\data\test.txt

So I'll close this request for now and you can reopen it if
the methods described above are inadequate for your scenario
(and please indicate why).

----------------------------------------------------------------------

Comment By: The Mad Butcher (mad_burcher)
Date: 2006-06-09 13:13

Message:
Logged In: YES 
user_id=295880

PS.
 bmp and ico files are in the Bitmaps directory (added for 
others who migth try working this way as well ;) )


----------------------------------------------------------------------

Comment By: The Mad Butcher (mad_burcher)
Date: 2006-06-09 13:09

Message:
Logged In: YES 
user_id=295880

In our case it is a legal stuffed license file, only we 
provide two versions of our installer; dutch and english, 
with a dutch or an english license file.
All language differences can be done through the 
localization wxl files, except for the license.rtf.

In my wxs source i use the WixUI_Install and inject my own 
dialog (for selecting an existing SQL server), sou i 
override the UI sequense settings. The only thing i can do 
now (for the locilization of the license file) is include 
the license agreement dialog and built-in my own 
localization-string, which can be (tmho) out in the 
standard files, just like you did with the banners, other 
bmps and ico files... (Maybe the license file was 
forgotten?)

BTW i 'override' the default license.rtf by putting one in 
the same dir as where my wxs source resides. Works like a 
charm, for bitmaps and ico files as well. Only locilazation 
for the license file is not yet possible this way :(


----------------------------------------------------------------------

Comment By: Frederik Carlier (fcarlier)
Date: 2006-06-09 08:56

Message:
Logged In: YES 
user_id=1149415

License files are legal stuff, and I don't think the CPL 
allows translations (at least, the GPL does not).

Also, you will almost always override this with you own 
license.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1503405&group_i
d=105970



_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to