Max,
Since this time there is the Microsoft OSP and you can certainly find
documentation at
http://msdn.microsoft.com/en-us/library/cc313153.aspx
I hope this helps.
Not sure yet but thank you. It's a rather large document. I read the
intro
page several times, does reading this PDF taint me from ever working
on POI
source? I think the answer is no but just checking.
No Taint - not since the Microsoft Open Specification Promise -
without that we would never have taken on OOXML.
That would be great. Be careful about the different licenses. See
http://apache.org/legal/resolved.html
for ASF policy on cross licensing. iText is MPL and compatible with
ASF projects only in binary form. Take care in creating your source.
But I'm not planning to distribute either the source or binaries to
either of
those projects... POI or iText. So surely this wouldn't matter would
it?
No, it would not.
Well if it does I'll just leave most of my work for me then, but
there the
iText stuff is just one class in one package (of writers) and the
POI stuff is
just one class in one package (of parsers).
That would work. We want contributions, but we can't take any
"CopyLeft" contributions.
Thanks again for the feedback, suggestions and the link.
Here is another - http://dev.plutext.org/blog/category/docx4j/
I saw on the other thread that you were looking at tools for docx. I
am at the 35,000 foot level, but the major difference between out POI
ooxml approach is that we use XMLBeans and docx4j uses JAXP.
Regards,
Dave
---------------------------------------------------------------------
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]
