https://bugs.documentfoundation.org/show_bug.cgi?id=94382
--- Comment #7 from Eike Rathke <[email protected]> --- Old Excel versions did not store the text encoding, they assumed the encoding to be the same code page the operating system runs in, so there is actually no way for us to obtain an encoding from the file in these cases. Other than guess from content or let the user choose. But we don't know in advance unless we have not encountered the code page record before the actual content, and calling a dialog from within the filter code is about a no-go. Given the legacy and rare occurrence of such documents I'm not convinced that implementing a heavy workaround would be worth the effort. Btw, for us people working on the shell command line it would be helpful to not have spaces or parentheses in file names if several files start with the same prefix where file name completion stops at a space or parenthesis ... @Julien: When analyzing .xls files you might be interested in the mso-dumper from http://cgit.freedesktop.org/libreoffice/contrib/mso-dumper but that seems to hang with "the\ old\ \(and\ common\)\ style\ excel\ file.xls", probably because it is not a compound document file format. Patches on gerrit welcome ;) if that plain BIFF5 thingy fits at all.. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
