[issue1855] Codepage unset in msilib.init_database()

Martin v. Löwis added the comment: [The original link seems down; I found a similar description at http://msdn.microsoft.com/en-us/library/aa372049%28VS.85%29.aspx] I think you are misinterpreting the documentation. It doesn't say that the codepage property is required (in fact, they explicit

[issue1855] Codepage unset in msilib.init_database()

Jim Wilson added the comment: It's been more than a year. I'll work a little longer on the SetProperty(...) example, but here's the "confirming evidence". A related problem is 1884, but I simply don't remember the context and long ago deleted the code in disgust. -- Added file: http:/

[issue1855] Codepage unset in msilib.init_database()

Changes by Daniel Diniz : -- dependencies: +msilib.SetProperty(msilib.PID_CODEPAGE, '1252') raises 0x65d = type mismatch priority: normal -> low stage: -> test needed type: resource usage -> feature request versions: +Python 2.7, Python 3.2 -Python 2.5

[issue1855] Codepage unset in msilib.init_database()

Changes by Christian Heimes: -- assignee: -> loewis components: +Windows -Distutils nosy: +loewis priority: -> normal type: -> resource usage __ Tracker <[EMAIL PROTECTED]> __ _

[issue1855] Codepage unset in msilib.init_database()

New submission from Jim Wilson: At http://msdn2.microsoft.com/en-us/library/aa367864(VS.85,printer).aspx, Satanic Verses sayeth: "The Codepage Summary property must be set before any string properties are set in the summary information.", but so far as I can tell, PID_CODEPAGE is never used in m