On 02-Nov-11 11:43, Gareth wrote:
> So what is the correct usage of Localizable="no" as an attribute of String?
It might be helpful to quote a message you're replying to, especially
when it's 2.5 years old. @Localizable is ignored; it's documentation
for people doing the loc work.
> Perhaps thi
We also reference the same localized string to write the version number to
the registry so we can query it as a potential launch condition for other
products, ie. "This package will only install if so and so is version x or
above." Hardcoding it requires a synchronized change in several places
rat
So what is the correct usage of Localizable="no" as an attribute of String?
Are loc files not effectively just a string table, which are conveniently
localizable?
I too use localised version numbers, the reason being we release the same
software in different markets/countries under different name
Matthias Rainer wrote:
> Is there a reason why the version string cannot be localized?
> Even though the version would be the same in every language,
That's why: Loc strings are designed to be used for loc purposes. Feel
free to file a bug so we can consider expanding the version parsing to
con
eason why the product
version cannot or should not be localized?
Regards,
Matthias
-Ursprüngliche Nachricht-
Von: Matthias Rainer [mailto:matthias.rai...@alumni.tuwien.ac.at]
Gesendet: Donnerstag, 26. Februar 2009 00:45
An: wix-users@lists.sourceforge.net
Betreff: [WiX-users] Loca
Hi everybody,
I'm trying to use a localized product version but I get this error running
candle:
package.wxs(20) : error CNDL0108 : The Product/@Version attribute's value,
'!(loc.Version)', is not a valid version. Legal version values should look
like 'x.x.x.x' where x is an integer from 0 to 65
6 matches
Mail list logo
