Re: KOffice 2.0 beta hints at improved capabilities
Posted by: Dummy00001
on October 11, 2008 01:04 PM
I had such problems in past, but can't comment on present state.
OO.o2 wasn't always 100% ODF compliant and for some things was dumping SXW into ODT. Pretty much no other (ODF compliant) suit could read it. I ran several OO.o's ODTs through ODF verification tool ( http://wiki.services.openoffice.org/wiki/ODFValidator ) and it produced some thousands of warnings for each file.
KOffice 1.x was crashing trying to read such files. I know for sure that 2.x doesn't crash (my bug report was closed), yet, until OO.o wouldn't improve its own ODF support (I heard OO.o3 claims to be compliant) and KOffice wouldn't crash on broken files, interoperability is all but remote target.
Also I had huge fonts problems. OO.o was trying to make document M$Wind0ze compliant by using weird fonts like Arial and Verdana (which were never present on my Linux). And obviously KOffice couldn't find them when trying to open the document. Result was less than pleasing rendering of what was before quite simple document.
I did also try opening KOffice 1.x ODF files in OO.o2, what was triggering different kind of bugs in OO.o: half of first page was rendered properly, but rest of document had fonts of size 4pt or something similar.
I think it is worth for somebody with writing skills to actually test KOffice 2.x and OO.o3 for two way interoperability.
Learn about Linux
Download Linux
Get Linux help
Re: KOffice 2.0 beta hints at improved capabilities
Posted by: Dummy00001 on October 11, 2008 01:04 PMOO.o2 wasn't always 100% ODF compliant and for some things was dumping SXW into ODT. Pretty much no other (ODF compliant) suit could read it. I ran several OO.o's ODTs through ODF verification tool ( http://wiki.services.openoffice.org/wiki/ODFValidator ) and it produced some thousands of warnings for each file.
KOffice 1.x was crashing trying to read such files. I know for sure that 2.x doesn't crash (my bug report was closed), yet, until OO.o wouldn't improve its own ODF support (I heard OO.o3 claims to be compliant) and KOffice wouldn't crash on broken files, interoperability is all but remote target.
Also I had huge fonts problems. OO.o was trying to make document M$Wind0ze compliant by using weird fonts like Arial and Verdana (which were never present on my Linux). And obviously KOffice couldn't find them when trying to open the document. Result was less than pleasing rendering of what was before quite simple document.
I did also try opening KOffice 1.x ODF files in OO.o2, what was triggering different kind of bugs in OO.o: half of first page was rendered properly, but rest of document had fonts of size 4pt or something similar.
I think it is worth for somebody with writing skills to actually test KOffice 2.x and OO.o3 for two way interoperability.
#