POI People,
Sorry, the problem applies only to 2007 beta. 2010 beta is ok. For 2007
beta we do extract the interesting bits with SAX :). It seems to work
well enough. I just wanted to know what's the "official" policy on this
topic. Now I know that forcing poi to grok pre-standard office files is
hardly worth the effort.
Thanks for you answers.
Antoni Myłka
[email protected]
W dniu 2010-04-19 19:54, Yegor Kozlov pisze:
Can you upload sample files created with Office 2010 beta that POI
cannot process? I exercised POI trunk against .xlsx and .pptx created
with the latest build of Office 2010 beta and saw no problems.
The build number is 14.0.4514.1004.
I don't think we should worry about files created with MS Office 2007
beta because they are not fully conformant to the OOXML specification.
The only reasonable workaround is to unzip the OOXML package and extract
interesting bits using SAX or XPath.
Yegor
Hello,
I stumbled upon a problem of having to process files created with MS
Office 2007 beta and Office 2010 beta, i.e. files with wrong namespaces.
I searched the archives and found this http://bit.ly/aehVMw. It is
clear enough. "Wrong" namespaces are not supported, and files created
with office beta versions are unreadable with POI.
But my question to the POI developers is:
If I'm desperate enough to hack POI and add support for broken files
by myself, where should I start looking? I thought about trying to
make xmlbeans namespace-blind, or to accept more than one namespace.
Do you think it's possible?
I'm a complete poi newbie, don't even know how stupid this question
might be :).
Antoni Mylka
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
