[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Bugs in OOo and compatibility issues
From:       Thorsten Zachmann <t.zachmann () zagge ! de>
Date:       2009-02-24 15:55:22
Message-ID: 200902241655.22928.t.zachmann () zagge ! de
[Download RAW message or body]

Hello Inge,

> Bug 185354 (https://bugs.kde.org/show_bug.cgi?id=185354) is about a bug
> that introduces an incompatibility with OpenOffice.org.  The bug itself is
> in OOo, in the way that it saves its files, no doubt about that.

I can't see any incompatibility here. What happens is that we show some more 
text oo files to mark accordingly. This is easy to fix. Just go to the master 
slide and remove the content of that fields you don't like to have. Not sure 
why you call that a incompatibility. 

> However, the nature of the bug is such that if we don't work around it,
> then we can just forget about anybody that ever saved a presentation in OO
> Impress to ever use KPresenter. Yes, it's that bad.
>
> I would like to discuss how to handle this.  In general I don't think we
> should encourage buggy files by supporting the bugginess in our
> application. But in this case, we can't just ignore it IMHO.

Unfortunately it is not possible to work around that bug easily. It would 
require to look at the OO source code to find out when to handle a shape as a 
placeholder and when not. 
I think that is out of scope as it is quite easy to work around the problem 
inside koffice.

I have one workaround for a bug inside kpresenter where ooimpress saved data 
quite wrong. However in that case it is easy to see that it is wrong and also 
it is easy to fix.

In general I'm against putting workarounds inside our code to fix bugs of 
other apps. That only makes the code much more difficult to handle and to 
understand.

One idea might be to create a script that tries to fix the odp saved by OO. 
However as I said above this will only be a try as there are so many 
questionmarks in what oo does there. No garante that the converted odp is 
what the user is expecting.

Another idea would also be an FAQ entry describing the problem and how to work 
around it.

Thorsten
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]