[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice-devel
Subject: Re: Bugs in OOo and compatibility issues
From: Cyrille Berger <cberger () cberger ! net>
Date: 2009-02-25 9:27:21
Message-ID: 200902251027.21939.cberger () cberger ! net
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Wednesday 25 February 2009, Alexandra Leisse wrote:
> > 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.
Users will definitively consider any kind of failure to be KO faults, almost
everybody consider OOo to be the reference implementation of ODF. But yet I do
think that koffice should produce valid ODF files, and we should put pressure OOo
to fix their loading/saving code, and document those issues in our website and
PR material. Accepting to save crappy stuff will turn ODF in a giant mess like
HTML and OOXML.
--
Cyrille Berger
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" \
/><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" \
font-family:'DejaVu Sans'; font-size:9pt; font-weight:400; font-style:normal;">On Wednesday 25 \
February 2009, Alexandra Leisse wrote:<br> > > In this case, I think always always save \
valid ODF. I think that<br> > > regular users minds works like:<br>
> ><br>
> > Save in KOffice -> Load in OOo -> Fail -> OOo's fault<br>
> > Save in OOo -> Load in KOffice -> Fail -> KOffice's fault<br>
><br>
> I'm a bit careful about that. OOo is perceived as an alternative to MS<br>
> Office and I'm afraid that users that are not so much into technical<br>
> details (yes, they do exist) will blame KO for all failures - be it<br>
> fair or not. For that matter you should try as much as possible to<br>
> ensure that the document stays useable in both apps. I'm not aiming<br>
> for perfect but a complete fail would be rather nasty.<br>
Users will definitively consider any kind of failure to be KO faults, almost everybody consider \
OOo to be the reference implementation of ODF. But yet I do think that koffice should produce \
valid ODF files, and we should put pressure OOo to fix their loading/saving code, and document \
those issues in our website and PR material. Accepting to save crappy stuff will turn ODF in a \
giant mess like HTML and OOXML.<br> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"><br></p>-- <br> Cyrille Berger</p></body></html>
_______________________________________________
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic