For Product/@Language decimal LCID representation is needed and here
16393 (en-IN) is not allowed. As I understand WiX uses the parent
language for special Locales like e.g. German(German) for
German(Austria) and German(Switzerland) to serve german speaking
installations or en-US for the different
Hi everybody,
Thanks Tobias for his answers.
@Tobias: I not sure if it makes any difference, but I intend to use LCID
without using WixUIExtension. Is your list of supported languages is also valid
when one doesn't use the translated UI?
Another question is to the whole community. Does anybody
Regarding the localization of hi-in. This localization contains the
english strings which is confirmed to be a bug (comp.
http://sourceforge.net/tracker/index.php?func=detail&aid=3163411&group_id=105970&atid=642714)
Think an older (or also newer) version of the WiX toolset has a
correct version of
Hi,
Assume this won't work as the LCID and locale en-IN doesn't exist in
WiX. Try hi-IN and 0x0439 Hindi (India) instead. An overview of the
LCIDs and WiX Culture names you can see in my post
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LCIDs-of-the-supported-languages-of-WixUIE
Hallo everyone,
Recently, I was trying to find some information about how does WiX handle the
issue with the new LCIDs introduced in Windows Vista. I mean for example
"en-IN" locale with LCID as 0x4009.
I tried to build the MSI tables from WiX that contained India files. In that
case the light
5 matches
Mail list logo