https://bugs.documentfoundation.org/show_bug.cgi?id=146260
--- Comment #3 from Kohei Yoshida <ko...@libreoffice.org> --- (In reply to Kevin Suo from comment #2) > I am adding Kohei Yoshida to cc: would you please confirm whether this is an > Orcus issue? Yes, this is an orcus issue. Orcus itself can theoretically process XML documents containing element contents or attribute values encoded in something other than utf-8 since the decoding part is delegated to the handler side (libreoffice). But the XML element and attribute names themselves must be in utf-8 (or utf-16 if proper byte order mark is given). Orcus needs to properly pick up the declared encoding type to the handler during XML mapping, and that *should* in theory fix this issue. The Excel 2003 XML file format import code does support non-unicode encoding by honoring the declared encoding type, so I just need to apply the same mechanism to XML mapping code. -- You are receiving this mail because: You are the assignee for the bug.
