Ok, thanks :)
I think that would help

-Sneha


Rob Hamflett wrote:
> 
> Yeah.  I just use a response file because I have a fair few preprocessor
> defines.  You can certainly 
> just list them individually on the command line.
> 
> Rob
> 
> Sneha Gharpure wrote:
>> Hi,
>> 
>> Thanks for the reply.
>> 
>> What I understood from your reply is that say English.txt will have list
>> of
>> all the preprocessor variables say $(var.LicenseFile). And these
>> variables
>> are given at the time of compilation to candle. So rather than using   a
>> text file, can it be done by supplying is as a command line argument?
>> Because, if the value is in some text file, parsing logic should be
>> implemented. I am already taking the version of the product as a command
>> line argument and using a preprocessor variable. Would the same trick
>> work?
>> 
>> Thanks,
>> Sneha
>> 
>> Rob Hamflett wrote:
>>> For the parts that can't be localised, I use preprocessor variables. 
>>> All
>>> the English specific stuff 
>>> is defined in English.txt and the Japanese stuff is defined in
>>> Japanese.txt.  In my Makefile I have 
>>> separate command lines for the English and Japanese builds, which take
>>> parameters of @English.txt 
>>> and @Japanese.txt respectively.  You might be able to get away with the
>>> same trick.  Presumably you 
>>> have different command lines so you can specify the correct .loc file?
>>>
>>> Rob
>>>
>>> Sneha Gharpure wrote:
>>>> Hi,
>>>>
>>>> The scenario is that the name of the license agreement file is to be
>>>> localized. The source file for the license agreement is specified as
>>>> follows. 
>>>>
>>>> <Control Id="AgreementText" Type="ScrollableText" X="20" Y="60"
>>>> Width="330"
>>>> Height="120" Sunken="yes" TabSkip="no">
>>>>     <Text SourceFile="$(loc.LicenseFile)"/>
>>>> </Control>
>>>>
>>>> This gives an error error LGHT0100 : File of type 'File' with name
>>>> '$(loc.LicenseFile)' could not be found.
>>>>
>>>> Is there any way to localize the name of the license agreement file?
>>>>
>>>> Thanks in Advance,
>>>> Sneha
>>>>
>>>
>>> -------------------------------------------------------------------------
>>> This SF.net email is sponsored by: Microsoft
>>> Defy all challenges. Microsoft(R) Visual Studio 2008.
>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>>> _______________________________________________
>>> WiX-users mailing list
>>> WiX-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>>
>> 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Localizing-the-Name-of-the-file-that-contains-License-Agreement-tp15870376p15872708.html
Sent from the wix-users mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to