Apache OpenOffice (AOO) Bugzilla – Issue 95759
docx/xlsx/pptx export filters
Last modified: 2019-07-23 22:17:28 UTC
To improve interoperability with MS Office 12, eventually we will need OOXML [or exactly docx/xslx/pptx ;-)] export. Since OOXML is so similar to the old binary formats, and to aid maintenance & code re-use, we have started refactoring that code to implement both formats. The start of the work is in CWS ooxml01.
Similar/duplicate to issue 88355
As no patch is attached, I changed the type to "feature". If you are working on refactoring code, please make sure that you sync with the existing code quite often, otherwise odds are high that integration would become a nightmare. I also would like to see the code "owners" involved in the refactoring decisions (->cc'ed hbrinkm). BTW: I doubt that such filters are necessary at all: - the export will not be better than with the binary export (as it uses the same code) - as more applications can read the binary format, interop will always be better using the binary formats - Office12 will get ODF import anyway; this is the first time in history where MS will support our file format! Why spoil this moment by doing the same old slave work again. So it will be a huge time investment and in the end OOo will have more code without any benefit for our users. But of course it's everybody's own choice where he wants to waste his resources. ;-) And at least code refactoring to make it better is indeed worthwhile.
mba: Sorry for the wrong issue type & thanks for the correction! > And at least code refactoring to make it better is indeed worthwhile. Yes, I believe so :-) - when the refactoring is in the stage that it is good enough for OOXML, it will be trivial to create a new RTF export [which is very much needed from what I know] using the refactored code [and share the base between these filters]. hbrinkm: If you have time to look at the code, input is most appreciated!
kendy: Do you plan to refactor the code in sw/filter/ww8 or add an export in writerfilter? I would prefer the latter, since our road map is to discard sw/filter/ww8 eventually.
There are no features in OOo that require the OOXML format to be exported instead of the binary formats, therefore I think such a filter is not needed at all. But well...
hbrinkm: So far I'm redesigning the export stuff in sw/source/filter/ww8. I have split the monolithic all-in-one class SwWW8Writer into three [+ some abstraction above this, but in principle it's 3 ;-)]: - one that takes care of writing to the stream(s) - one that manages the logic of the export filter [like collecting various ID's, styles and stuff] - and one that actually outputs the attributes, like actual sprms & things around it When this is done, it is much simplier to move the code to writerfilter, because 'UNOizing' in incremental steps will be more easily achievable. dr: I am involved mostly in the Writer part of the work; but from what I know, at least xls probably cannot handle the new 1024 column limit, while xlsx can...
[Just a correction, not 1024, but 16384, apparently...]
right, I missed the column count expansion :-/
I've changed the dependencies so that we can up-stream the work in more CWSes. CWS ooxml01 should be deleted from EIS.
*** Issue 114914 has been marked as a duplicate of this issue. ***
*** Issue 126423 has been marked as a duplicate of this issue. ***
*** Issue 126818 has been marked as a duplicate of this issue. ***
Reset assigne to the default "issues@openoffice.apache.org".
According with > Similar/duplicate to issue 88355 *** This issue has been marked as a duplicate of issue 88355 ***