Re: kofficetests validation
Jos van den Oever <[email protected]>
| Newsgroups | gmane.comp.kde.devel.koffice |
|---|---|
| Organization | KO GmbH |
| Message-ID | <[email protected]> |
On Tuesday, November 09, 2010 14:28:22 pm Cyrille Berger Skott wrote: > As I have said to Inge on IRC. I would agree to treat invalid ODF as > release blockers, under the following conditions: > > 1) That a proper explanation on why the use of the koffice namespace is > invalid is provided (while, it seems the openoffice namespace is > acceptable) 2) There are people commited to fix the problems I am not committed to doing the fixes, but I have put quite some effort in making the errors visible. Since I'm working on entirely different code atm, I hope other people will have a look at the invalidly saved documents. > 3) We have an easy way to get reports on the ODF validity (aka a page which > list which documents are saved invalid) This list can be found on http://158.36.191.251:8080/overview.html We're not that far off. Currently 224 out of 3026 files are invalid or cause a crash. > But I am unsure, if it is not too late in the 2.3 cycle to add this as > release blocker, and if it should not be set as requirement for the next > release. To be clear, Chanis mail was not about the fact that koffice saves files as invalid ODF in about 5% of the cases. The question was, what to do about the fact that many of the files in kofficetests seem to be invalid ODF. Do we want to fix them? Chani is currently roundtripping files with ODFKit from zip to flat back to zip and checking that the files do not lose information or become invalid. Since many are invalid to begin with the size of the useful pool of documents is smaller than it could be. Cheers, Jos -- Jos van den Oever, software architect +49 391 25 19 15 53 http://kogmbh.com/legal/