On 2011-07-02, Dennis E. Hamilton wrote:
upscope [mailto:upscope@nwi.net] wrote:
Nuno J. Silva wrote:
[ ... ]
LibreOffice *does* have support for .docx, there's no false
advertisement here.
Although this support is not complete, this just means some features
won't be imported/recognized. It should definitely *not* crash.
You probably hit some bug. Does it happen only with that docx? Or
converting other pdf also generates a .docx that crashes LibO?
[...]
I confirm this one opens fine in 3.3.3, does it crash there?:
http://tinyurl.com/libo-docx-sample
I just opened this successfully on LibreOffice 3.3.3.1 on openSUSE 11.4
I tried
<http://tinyurl.com/libo-docx-sample>
On Windows in LibreOffice 3.3.2, LibreOffice 3.4.0, IBM Lotus Symphony
3 with fixpack2, and also Microsoft Office Word 2010. None of them
have any problem with that .docx sample.
So that is not representative of whatever is causing a crash.
That's expected. I should have been clearer, that sample is for the OP
(mazallen) to check if it crashes too.
--
Nuno J. Silva (aka njsg)
gopher://sdf-eu.org/1/users/njsg
--
Unsubscribe instructions: E-mail to users+help@global.libreoffice.org
In case of problems unsubscribing, write to postmaster@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/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.