Neil Sleightholm wrote:
> May be it could provide a warning message for missing strings that would
> make it obvious what was happening. I have worked around the Dutch
> problem for now by including "-loc WixUI_en-us.wxl" on the light command
> line, but as you have observed, I now don't know what
;t translated.
Neil
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 27 September 2008 19:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Light cultures option
Neil Sleightholm wrote:
> The difference is that when you build your o
Neil Sleightholm wrote:
> The difference is that when you build your own localisation you can
> specify more than more wxl but when you include an extension cultures
> only selects the first culture it finds and does read anymore, in
> Library.cs - GetLocalization() it returns on the first culture
hen more English added) then
they can't fall back to en-us.
Neil
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 25 September 2008 03:44
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Light cultures option
Neil Sleightholm wrote:
Neil Sleightholm wrote:
> Following some earlier posts on this topic I believed that
> "-cultures:nl-nl;en-us" meant "use the Dutch localization but if a
> string is missing use English". This seems to be true for my own
> localization strings but not for the WiX UI Extension (or any other
> extens
I wonder if someone could clarify how the light cultures option should
work?
Following some earlier posts on this topic I believed that
"-cultures:nl-nl;en-us" meant "use the Dutch localization but if a
string is missing use English". This seems to be true for my own
localization strings but no
6 matches
Mail list logo
