'Re: Bugs in OOo and compatibility issues'

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

List:       koffice-devel
Subject:    Re: Bugs in OOo and compatibility issues
From:       Sven Langkamp <sven.langkamp () gmail ! com>
Date:       2009-02-25 10:58:20
Message-ID: 478b087a0902250258g39f74d32t3340970cc4b6b400 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

On Wed, Feb 25, 2009 at 11:20 AM, Jan Hambrecht <jaham@gmx.net> wrote:

> Cyrille Berger wrote:
> > On Wednesday 25 February 2009, Jan Hambrecht wrote:
> >> Yes that is my concern too. If we are to read faulty odf files we should
> >> provide a way (maybe a popup dialog?) to inform the user that the opened
> >> file is buggy in regard to the odf spec.
> > While it might be self satisfactory for us to inform the user that OOo is
> > buggy, I don't think the user will care.
> >
>
> Then i fail to see how we would "put pressure" on OOo. The user would
> certainly not read a website or some pr material, because as you rightly
> said: "I don't think the user will care.".

The only way I see would be to get some independant party to do ODF testing
like the acid test did for html.
The question is how much "pressure" you can put on the OOo developers. My
impression is that they are a bit overloaded with bugs.

PS: One a similar matter regarding strokes in odg, the OOo developer
> proposed to change the spec. Food for thought i think.
>

There are more. I have listed the problems I'm aware of on the wiki, but
that list isn't complete.
http://wiki.koffice.org/index.php?title=KOffice2/ODF_Problems

[Attachment #5 (text/html)]

<div class="gmail_quote">On Wed, Feb 25, 2009 at 11:20 AM, Jan Hambrecht <span dir="ltr">&lt;<a \
href="mailto:jaham@gmx.net">jaham@gmx.net</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt \
0.8ex; padding-left: 1ex;"> <div><div></div><div class="h5">Cyrille Berger wrote:<br>
&gt; On Wednesday 25 February 2009, Jan Hambrecht wrote:<br>
&gt;&gt; Yes that is my concern too. If we are to read faulty odf files we should<br>
&gt;&gt; provide a way (maybe a popup dialog?) to inform the user that the opened<br>
&gt;&gt; file is buggy in regard to the odf spec.<br>
&gt; While it might be self satisfactory for us to inform the user that OOo is<br>
&gt; buggy, I don&#39;t think the user will care.<br>
&gt;<br>
<br>
</div></div>Then i fail to see how we would &quot;put pressure&quot; on OOo. The user would<br>
certainly not read a website or some pr material, because as you rightly<br>
said: &quot;I don&#39;t think the user will care.&quot;.</blockquote><div><br>The only way I \
see would be to get some independant party to do ODF testing like the acid test did for \
html.<br>The question is how much &quot;pressure&quot; you can put on the OOo developers. My \
impression is that they are a bit overloaded with bugs. <br> <br></div><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt \
                0.8ex; padding-left: 1ex;">
PS: One a similar matter regarding strokes in odg, the OOo developer<br>
proposed to change the spec. Food for thought i think.<br></blockquote></div><br>There are \
more. I have listed the problems I&#39;m aware of on the wiki, but that list isn&#39;t \
complete.<br><a href="http://wiki.koffice.org/index.php?title=KOffice2/ODF_Problems">http://wiki.koffice.org/index.php?title=KOffice2/ODF_Problems</a><br>

_______________________________________________
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] 