26 Oct
2017
26 Oct
'17
15:00
http://bugzilla.suse.com/show_bug.cgi?id=1065270 http://bugzilla.suse.com/show_bug.cgi?id=1065270#c4 --- Comment #4 from Jan Matejek <jmatejek@suse.com> --- That doesn't seem to be necesary, so maybe for upstream to decide. The "proper" solution for this is probably in libxml2 itself, not returning undecodable strings as error messages. (there's actually a related bug: the error handler emits a "^" to mark the error location, but it's spaced to bytes, so if the error text contains Unicode characters, the "^" is misplaced. ISTM these two should be fixed together, by making the error reporting encoding-aware) -- You are receiving this mail because: You are on the CC list for the bug.