Hi :)
DocX normally opens easily in LO and OOo (3.3.0 and after). Which OS; Windows,
Ubuntu, other linux, Bsd or Mac?
Regards from
Tom :)
________________________________
From: Joep L. Blom <jlblom@neuroweave.nl>
To: Libre-office lijst <users@libreoffice.org>
Sent: Mon, 2 May, 2011 10:10:26
Subject: [libreoffice-users] .docx can't be read
I recently received a .docx file as an attachment.
However, what I tried, LO wouldn't read it. It opened it but gave a blank page.
The people who sent the file are complete computer illiterate who follow MS$
like slaves. I assume it is the latest Word or whatever MS$ uses as text
application. It can well be that the file is composed of pictures. When I open
the file with Hexedit I see content and the first 2 bytes are hex 50 4B (PK) and
byte 31 till 49 contains "[Content_Types] xml, the byte beween ] and x is hex
2E.
Can anybody explain why LO can't read this file?
Help is much appreciated.
Joep
-- Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.