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


Hello tml, I work on a licensed library in one of my organization products
that renders office and PDF documents just fine. But lately, we have been
getting several requests to support open document formats as well, and we
are considering/evaluating libreoffice as our solution if it works fairly
well and I am trying to see if I can contribute and fix the issues related
to at least fixing basic .odt,.odp and .ods viewing. Thanks for the info on
the warnings :).

On Sat, Oct 10, 2015 at 9:28 AM, Tor Lillqvist <tml@iki.fi> wrote:

I am able to open couple of .odt documents, but opening of .odp and .ods
fails,

Yep, that is more or less what I see too, and if you seriously plan to
work on this, you need to figure out what causes that. (Are you doing this
just out of personal interest, or is there some organisation backing you?
Perhaps even commercial interest, which would be a good thing?)

Also, note that many of the warnings that are displayed in Xcode show up
also when running (a developer build of) LibreOffice on a desktop OS. They
are often misleading and not really worth being displayed as warnings. I
think. But our codebase is so vast that people seldom bother removing
pointless warning messages. Also, there is the "yes, yes, I know, this is a
sign of something that we really should fix so let's not remove that
warning" phenomenon.

--tml



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.