Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index

Re: [tdf-discuss] Old Bugs


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/02/2010 03:48 PM, Peter Rodwell wrote:

1. Complete file compatibility. I frequently handle documents with very
 complex formatting.

Funny thing here.

I get better compatibility using OOo and LibO, than I did when I was
using MSO.  I still receive documents in both .doc and .docx formats
that can not be opened with MSO, but can be easily opened and displayed
with both OOo and LibO.

They *must* retain 100% of the original formatting. So far this has
not been the case with Oo.

If that is the case, then you have to be using the same computer as the
document was created on, using the same settings, and the same edition
and the same version of MSO. Otherwise compatibility is going to be less
than 100%. Even with that configuration, you aren't guaranteed 100%
compatibility.

jonathon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzQqmQACgkQaC1raifmCuF1JgCdHAcVFR7aZQyJdwOuzNBCUeUd
FmEAn1PyGuSunMKsDRZZ755QuinvOtxt
=2UJi
-----END PGP SIGNATURE-----

-- 
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***

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.