https://bugs.kde.org/show_bug.cgi?id=455255
Alvin Wong <al...@alvinhc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #7 from Alvin Wong <al...@alvinhc.com> ---
I tried reverting 0db3b4718cdf2da4d3461906993716bf5eb6dc66 but it didn't fix
the issue.
Just looking at the code, SVG import goes through QXmlInputSource. From its
doc:
> This class recognizes the encoding of the data by reading the encoding
> declaration in the XML file if it finds one, and reading the data using
> the corresponding encoding. If it does not find an encoding declaration,
> then it assumes that the data is either in UTF-8 or UTF-16, depending on
> whether it can find a byte-order mark.
Checking QXmlInputSource::data() in SvgParser::createDocumentFromSvg, it does
seem to read the non-BMP chars correctly (as two QChar as expected). These
chars are lost after going through QDomDocument::setContent. I skimmed through
the git log but I didn't notice any changes in caf9f20f..868c011a8 that might
have cause this.
--
You are receiving this mail because:
You are watching all bug changes.
