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

List:       koffice-devel
Subject:    Re: mass  testing of kword parsing
From:       Jos van den Oever <Jos.van.den.Oever () kogmbh ! com>
Date:       2009-09-08 15:10:19
Message-ID: 200909081710.19719.Jos.van.den.Oever () kogmbh ! com
[Download RAW message or body]

On Tuesday 08 September 2009 04:57:27 pm Werner Trobin wrote:
> On Tuesday 08 September 2009 16:08:54 Jos van den Oever wrote:
> > On Tuesday 08 September 2009 03:44:02 pm Werner Trobin wrote:
> > > If handlertest is able to process the file without problems, it is very
> > > unlikely that it would crash when used from the KOffice part of the
> > > import filter.
> >
> > I've seen a few odt files that are produced by koconverter that crash
> > kword. So it's not as clear cut as it seems. That being said: it's easy
> > to test if the crash is on the doc->odt conversion or the kword loading
> > of the odt file.
> 
> Oh, sorry, there seems to be a misunderstanding. The filter itself consists
>  of two parts, libwv2 (external) and the KOffice "frontend" to libwv2. Then
>  there are potential bugs in KWord, which explains your problems loading
>  some .odt files.
> 
> The test harness in libwv2 is completely independent from KOffice. IMHO the
> first step is to ensure that libwv2 is able to handle everything you throw
>  at it, e.g. by using handlertest. Using koconverter you can subsequently
>  test the KOffice "section" of the filter, and finally the loading in
>  KWord.

Thanks for the explanation, but I was aware of that. :-)
Still, it is true that we can use 3 different executables to run on .doc files:
handlertest, koconverter and kword.

Cheers,
Jos

-- 
Jos van den Oever, software architect
+49 391 25 19 15 53
http://kogmbh.com/legal/
_______________________________________________
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]