Description: OK: "D:\TMP\libre\a\p19.xml" NG: "D:\TMP\libre\あ\p19.xml" Steps to Reproduce: 1.Start Calc 2.Select "XML source" menu 3.Select XML file 4.Select cell 5.Push Import button Actual Results: import is not done. Expected Results: import is done. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.7.2 (x64)
Could you give a try with LO 7.3.5 ?
Repro using Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 66cc8eb6cb5f20251df4e925477653a12ef27297 CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL
Code pointer: ScOrcusXMLContextImpl::importXML. See also: https://gerrit.libreoffice.org/c/core/+/108483 and https://gitlab.com/orcus/orcus/-/issues/30 Kohei: do you have an idea how to fix this, other than that GetShortPathNameW workaround? Note that it would fail in many cases, including increasingly growing number of disabled short names, as well as UNC paths.
Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/c2e86396b741b956efc05e9dfea1e1c3286dfb9d tdf#150247: patch orcus to use UTF-16 paths on Windows It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Mike Kaganski committed a patch related to this issue. It has been pushed to "libreoffice-7-4": https://git.libreoffice.org/core/commit/3984aa54e43ce2cf342937b9afedbf1d5e79592c tdf#150247: patch orcus to use UTF-16 paths on Windows It will be available in 7.4.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
dongshili: could you please take a look at this - does the issue we have discussed in bug 114093 is the same as discussed here, i.e. the xml import fails if the file path contains Chinese characters but success if the file path is flat ascii characters (e.g. put in the root of the C or D drive)?
*** Bug 146221 has been marked as a duplicate of this bug. ***