On 19/05/2014 Andre Fischer wrote:
As one of the first tasks in the OOXML area I would like to propose to redesign and re-implement the OOXML parser.
I can only agree with this one. We've already discussed it many times, but even the many users who prefer ODF need a good support for OOXML for interoperability, and better support for the Microsoft Office native formats is consistently in the top requests.
I propose a new and unified approach that will essentially replace the current design and implementation.
Sounds good. Especially the idea to be able to automatically know how much of the specification is covered will be helpful.
I also propose to focus first on Impress. Its complexity regarding OOXML is less than that of Writer and Calc
And this is probably good for users too. In my experience, the import of .PPTX files is the most unsatisfactory one at the moment, with many obvious deficiencies. Improving this one first would already give good results for users.
I have made several experiments regarding the reading of the specification and generation of parsers and am confident that the outlined approach will work.
A not-so-original question: we have another Apache project, POI, http://poi.apache.org/ that among the other things has an OOXML parser. If we are starting from scratch, why not reusing their code? And, if there are reasons for not reusing it, could we validate this roadmap with the POI developers, who are probably more familiar with OOXML parsing than the average reader of this list?
Regards, Andrea. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
