https://bugs.freedesktop.org/show_bug.cgi?id=57769
Priority: medium Bug ID: 57769 Assignee: libreoffice-bugs@lists.freedesktop.org Summary: FILEOPEN: .docx file considered as damaged if using .doc extension Severity: normal Classification: Unclassified OS: All Reporter: nalimi...@club.fr Hardware: Other Status: NEW Version: 3.5.6.2 release Component: Writer Product: LibreOffice Created attachment 70866 --> https://bugs.freedesktop.org/attachment.cgi?id=70866&action=edit Empty .docx file incorrectly ending with .doc It happens that .docx files are using a .doc extension. I found this for several files on a website, even though I don't understand why. In that case LO 3.5.7.2 and 3.6.3.2 (tested on Linux for the first, on Mac OS X for the second) consider the file as damaged, ask whether to attempt to fix it, and eventually fail to open it. Users can then only blame LO, because it appears to work with MS Word. Would it be possible to do a basic detection during the attempt at fixing the file, or even before? Document formats have magic sequences that allow the 'file' UNIX command to detect them. This would make LO much more robust. Many applications do not even use the extension for anything, and detect the format from the contents of the file. Attached is an empty .docx file incorrectly ending with .doc to illustrate the problem. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs