|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #59203] [octave forge] (io) Problem with xlsread importing accent marks |
Date: | Tue, 6 Oct 2020 15:36:17 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36 Edg/85.0.564.68 |
Update of bug #59203 (project octave): Status: Confirmed => Patch Submitted Depends on: => bugs #59214 _______________________________________________________ Follow-up Comment #21: John accepted the patch in bug #59214 and pushed it to the repo. When that change will be released, it will no longer be necessary to convert anything when using the COM interface. The attached patch makes the according preparations for that change. And it also tries to recover/write as much as possible with older versions of the windows package. Like already written before it also removes the (optional but incorrect) character conversions with the OCT interface. Wrt to the Java interfaces or LibreOffice: I don't have Java, the interfaces or LibreOffice installed. But if you are interested, you could try to read "Unicode.xlsx" or write a file with "tst_unicode_xlsx.m" with each of them. My hopes are that they are cross-platform enough to assume UTF-8 and everything Just Works (TM). ;-) (file #49929) _______________________________________________________ Additional Item Attachment: File name: bug59203_xls_unicode_v2.patch Size:10 KB <https://file.savannah.gnu.org/file/bug59203_xls_unicode_v2.patch?file_id=49929> _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?59203> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |