Hello!
Do I support LibreOffice? Yes, I do.
Let me show some positive numbers:
When I downloaded 400 .doc files, I opened 399 files in LibreOffice.
Only 1 could not be opened.
All 400 files were smaller than or equal to 692.5 KB. I started the testing from the smallest file
to the largest file. It happened to be that I could not open that one file which was 692.5 KB.
I am not a Maths expert. 399/400 = 99.75%
Congratulations! This is excellent! Well done.
To make a rough conclusion, I claim in a reasonable way that LibreOffice can open 99.75% of the
.doc files I may come across in future if these files are smaller than 700KB.
I do not know if these numbers are scientific enough. However, such information definitely helps me
to say that LibreOffice 4 is really good!
Microsoft Office is not my area of interest, by the way. It is just that someone uses it. There
were cases when Word could not open .doc files in the past. These cases are not my area of interest.
Regards,
C. H. D.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _
________________________________
寄件人︰ e-letter <inpost@gmail.com>
收件人︰ C. H. D. <webofht-libreoffice001@yahoo.com.hk>
副本(CC)︰ LibreOffice User Support Mailing List <users@global.libreoffice.org>
傳送日期︰ 2013年02月12日 (週二) 5:53 PM
主題︰ Re: [libreoffice-users] Bug 60390 - FILEOPEN: Cannot open particular document
On 12/02/2013, C. H. D. <webofht-libreoffice001@yahoo.com.hk> wrote:
Hello!
Yes, my Microsoft Office is legal. (Just happened that many other people use
it.)
I think it is an interoperability issue.
If you are very concerned about interoperability, you should be
contacting m$ and ask them why they cannot open odf documents created
using LO. Have you done this?
I searched the Internet and looked for documents randomly to test if
LibreOffice can open them. This is the authentic test.
No, a more authentic test is to search for odf documents and compare
of LO and m$ opens these types of documents.
If Microsoft Office opens the .doc files correctly, LibreOffice should also
open them correctly.
No, LO is not a m$-clone. If LO opens the odt document correctly, m$
should also. Have you tested this?
If Microsoft went bankrupt, what office suite would be able to handle
thousands of .doc files?
Unlikely, but that is the fault entirely of the user that creates the
document in the m$ file format!!!
If LO, or any other odf-compliant software disappears, you can find
another. That is why you should be testing "interoperability" with odf
and not m$ formats.
Then, the data in the .doc files would be lost if no other office suite was
able to open them, I am afraid.
I hope that happens (but a small possibility).
Not many people like converting .doc files into .odt files, I am afraid.
That is their choice. Start creating documents in odf!
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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.