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

List:       koffice-devel
Subject:    Re: Bugs in OOo and compatibility issues
From:       Alexandra Leisse <leisse () kde ! org>
Date:       2009-02-25 9:11:42
Message-ID: f46093a70902250111n1bbcae6aj3a7fccf34b1defe4 () mail ! gmail ! com
[Download RAW message or body]

On Wed, Feb 25, 2009 at 09:53, Elvis Stansvik <elvstone@gmail.com> wrote:
> 2009/2/25 Thomas Zander <zander@kde.org>:
>> On Tuesday 24. February 2009 20:17:57 jaham@gmx.net wrote:
>>> My opinion is that we should stick to the spec and not copy buggy
>>> behaviour of   OOo.  I mean we are implementing odf support and not copy
>>> an application. That is probably more painful at the moment, but better
>>> for the longterm future.
>>
>> There is a old adage for writing loading/saving code;
>> "Be liberal in what you accept, and conservative in what you send".
>>
>> This still holds; if we can make the actually existing ODP files readable
>> and showing in KPresenter without loosing more than time, then we should.
>> Just because, well, OOo is the only app that creates .odp files right now.
>>
>> So for Thorsten; do you have a problem with a good fix going into KOffice,
>> or do you just not have the time to do it yourself?
>> If you don't have time, please leave the bugreport open as a high priority
>> bug.
>
> +1
>
> There's a lot of content out there saved with this bug I'm sure, and
> handling it well is not so much saying it's okay for OOo to be
> non-conformant to spec as it is about supporting users sitting on that
> content.

Indeed. Noone will switch if they have to rewrite all their content.
And I personally can't blame them ;)

> In this case, I think always always save valid ODF. I think that
> regular users minds works like:
>
> Save in KOffice -> Load in OOo -> Fail -> OOo's fault
> Save in OOo -> Load in KOffice -> Fail -> KOffice's fault

I'm a bit careful about that. OOo is perceived as an alternative to MS
Office and I'm afraid that users that are not so much into technical
details (yes, they do exist) will blame KO for all failures - be it
fair or not. For that matter you should try as much as possible to
ensure that the document stays useable in both apps. I'm not aiming
for perfect but a complete fail would be rather nasty.

> That is, I think that when they encounter problems, they will blame
> the application they're currently using.
>
> So yea, the adage Thomas brings up I think holds very well, both from
> a technical and user point of view.
>
> Of course it's very important to document any deviations from the spec
> in loading, and to isolate it as much as possible in code, using
> strategies or other measures, and also to not give up on trying to
> have a dialog with the OOo people.
>
> Elvis
>
>> --
>> Thomas Zander
>>
>> _______________________________________________
>> koffice-devel mailing list
>> koffice-devel@kde.org
>> https://mail.kde.org/mailman/listinfo/koffice-devel
>>
>>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
_______________________________________________
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]