http://bugs.winehq.org/show_bug.cgi?id=29265 --- Comment #1 from Nikolay Sivov <bunglehead(a)gmail.com> 2011-12-07 14:01:06 CST --- (In reply to comment #0)
Did some investigation, the log shows this: err:msxml:doparse Document labelled UTF-16 but has UTF-8 content The problem is that this application sets wrong the encoding in xml to UTF-16. The file is UTF-8 and if changed with editor the search went OK.
So application itself writes malformed xml file using msxml functionality or just does it internally somehow? According to XML Spec (as I understand it) such case is considered fatal error: --- It is a fatal error if an XML entity is determined (via default, encoding declaration, or higher-level protocol) to be in a certain encoding but contains byte sequences that are not legal in that encoding. --- and that makes sense, but msxml error handling could differ of course.
For such ill applications to work, the encoding have to be forced/fallbacked to UTF-8 but libxml2 does not have such a functionality by design.
Well, it's possible to add some workarounds for this. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.