The file properties displayed in Windows Explorer for an MSI built on code page 1251 Cyrillic for Russian are not being encoded correctly. Effected file properties are “Subject”, “Tags”, and “Comments”.
Examination of the MSI file in a binary editor shows that all characters from the translation were converted to the value 7F instead of the code page 1251 Cyrillic character values.
This appears to be a problem with code page 1251 Cyrillic/Russian. The problem did not appear on code pages: 932, 936, 949, 950 or 1252.
Problem exists in WiX v3.5 release and WiX v3.6 RC0.
See attachments.
Windows Explorer showing problem with encoding.
Binary Editor showing failed encoding of Russian properties
Please attach WiX authoring and .wxl files used for the strings.
barnson:
Please look at the attachment Windows_Exporer_Showing_Properties.png and you will see that when light.exe creted the binary MSI files it set the Subject, Tags, and Comment file properties for Windows Explorer. It used the product name which was "PTC Windchill SocialLink Client" which I provided. The text that it appended (the formatted string) is not within my own .wxl files. It must be pulling the resources directly from its own compilation (light.exe). I never asked for these properties to be set, nor did I provide any strings (other than the product name) to set them. It was some internal feature of the light.exe or Windows Installer API.
So I think you will find little of interest in my WiX files.
Dave
Basic Wix 3.5 UI messages
Application specific strings. (BTW Missing Resources was some extension strings we added)
Wix File used to generate MSI
The wixobj file from the MSI creation
I'm looking to see the Product and Package elements and any loc strings you used.
The .wixobj file was compiled with the CODEPAGE variable set to 1252. You can use WixLocalization/@Codepage to specify a codepage in your .wxl and avoid the preprocessor.
barnson,
Thank you. As you can see the WiX files are auto generated. I went through all the build scripts and found the flaw. Sorry I did not catch that sooner. Thank you for taking your time on this.
Dave
Yet another reason not to over-autogenerate.