You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Angelo zerr <an...@gmail.com> on 2011/08/11 15:22:08 UTC
Re: [odfdom-dev] Status of the Simple Java API for ODF and ODFDOM - 08/10/2011
Hi Biao,
Thank a lot to mention XDocReport in your mail. I would like give some
information about it. You can find XDocReport at
http://code.google.com/p/xdocreport/. By default XDocReport generate report
source 2 source (odt 2 odt, docx 2 docx...). At this step ODFDOM IS NOT
Used. ODFDOM is used for convert ODT 2 XHTM or PDF that we have called
ODFDOMConverter <http://code.google.com/p/xdocreport/wiki/ODFDOMConverter>
THe ODFDOMConverter is Java implementation to convert ODT 2 PDF (with itext)
and XHTML. This project is used by XDocReport (if you wish convert your
generated report 2 XHTML, PDF) BUT you can use ODFDOMConverter without
XDocReport (package is
org.odftoolkit.odfdom.converter<https://xdocreport.googlecode.com/svn/trunk/org.odftoolkit.odfdom.converter>
)
My idea was to give to ODFDOM Team the sources of the ODFDOMConverter
project. But since you wish gives the project 2 Apache, I'm not sure that
ODFDOM Converter will interest Apacahe. Why? Because we are using iText for
PDF and not FOP. I believe that Apache Fondation don't want use iText.
We have the same proble with our DOCX converter
http://code.google.com/p/xdocreport/wiki/XWPFConverter
If you think iText is not a problem for Apache Fondation, we will happy to
give your the ODFDOMConverter project.
Regards Angelo
2011/8/10 Biao Han <ha...@cn.ibm.com>
>
> *(**We should send this to project mailing list, but we don't have one
> yet**. so sorry for interrupt those guys in **incubator general mailing
> list**)*
>
> *ODF Toolkit move to Apache*
> 1. SVN account has been created and is now available for use. We will
> discuss and start the code move after mail lists are ready;
> 2. The first board meeting is scheduled for Wed, 17 August 2011, 10 am
> Pacific. We have submitted a quarterly board report to here<http://wiki.apache.org/incubator/August2011>
> .
> 3. As we have been an Apache incubator project, so we will discuss and
> release ODF Toolkit in the new community. The original release plan have to
> be cancelled.
>
> *Simple ODF*
> 1. Reviewed and pushed a bug about TextProperties (#bug 357).
> 2. Reviewed and pushed three unit test coverage enhancement patches
> (#bug 241) .
> 3. The downloads of Simple ODF 0.6.5 has been to 204. This number
> equals with Simple ODF 0.4. But version 0.4 uses more 6 months get it, while
> version 0.6.5 uses only 40 days.
>
> *ODFDOM*
> 1. Working on data signature. There are two issues caused by OpenOffice
> block the process.
> (1) OpenOffice.org generate a Namespace unaware signature document.
> ODFDOM loads it fails.
> (2) OpenOffice.org creates multiple X509Certificates instead of the
> correct certification chain under ds:KeyInfo.
> see also:
> https://bugs.freedesktop.org/show_bug.cgi?id=39657 (ds namespace in
> LibreOffice)
> http://openoffice.org/bugzilla/show_bug.cgi?id=107864 (ds
> namespace in OOo)
> http://openoffice.org/bugzilla/show_bug.cgi?id=66276 (multiple
> X509Certificate in OOo)
> http://openoffice.org/bugzilla/show_bug.cgi?id=108286
> We have to supply two modes to fix it. One follows ODF
> specification, the other follows Open Office. The question is which is the
> default?
> 2. A new user: XDocReport uses ODFDOM to load and manipulate ODF
> document. It's Java API to merge XML document created with MS Office (docx)
> or OpenOffice (odt), LibreOffice (odt) with a Java model to generate report
> and convert it if you need to another format (PDF, XHTML...).
>
>
> Regards
>
> Biao Han (Devin)
> SOA Standards Growth, Emerging Technology Institute(ETI), IBM China
> Software Development Laboratory
> Tel:(86-10)82450541
> Email: hanbiao@cn.ibm.com
> Address: 3/F Ring Building, No.28 Building, Zhong Guan Cun Software Park,
> No. 8 Dong Bei Wang West Road, ShangDi, Haidian District, Beijing,
> P.R.C.100193
>
Re: [odfdom-dev] Status of the Simple Java API for ODF and ODFDOM - 08/10/2011
Posted by Biao Han <ha...@cn.ibm.com>.
Angelo zerr <an...@gmail.com> wrote on 2011-08-12 17:26:24:
> From: Angelo zerr <an...@gmail.com>
> To: Biao Han/China/IBM@IBMCN
> Cc: dev@odftoolkit.odftoolkit.org, dev@odfdom.odftoolkit.org,
> general@incubator.apache.org, dev@simple.odftoolkit.org
> Date: 2011-08-12 17:27
> Subject: Re: [odfdom-dev] Status of the Simple Java API for ODF and
> ODFDOM - 08/10/2011
>
> Hi Biao,
>
> Thanks for your contribution intention. But we found iText uses the
> AGPL license: http://itextpdf.com/terms-of-use/index.php
> So it would be difficult to use that in an Apache 2.0 licensed project.
>
> Yes I thought that. That's very shame -(
>
>
> Do you have plan to supply a version using PDFBox pr FOP? Both of
> them will be OK for Apache 2.0 license.
> And as far as I know, PDFBox may be easier. Its API is similar with
iText.
>
> XDocReport uses iText because ODT->PDF processes like this :
>
> 1) load ODT with ODFDOM
> 2) visit ODFDOM and generate iText structure PDF per ODFDOM structure
>
> Problem with FOP is that you must have XML FO to generate PDF. I
> have tried to do that (without ODFDOM) with XSL-FO, but performance
> are very bad (even with XSLT cache, use xsl:key to cache compute of
> styles....). Perhaps it's possible to use FOP with pur Java (without
> XML FO) but I have not found samples.
>
> For PDFBox, I have never used. Do you think this library manage the
> same thing than iText (Table, table row, images widget...) and with
> the same peformance? I must study it to see if it's possible to
> implement a new converter with PDFBox.
Please reference the cookbook
http://pdfbox.apache.org/userguide/cookbook.html
Or we can request help from their user mail list
http://pdfbox.apache.org/mail-lists.html#users
>
> Thank a lot for your information;,
>
> Regards Angelo
>
> Whatever, thank you for your eager contribution intention!
>
>
> >
> > Regards Angelo
> >
>
> > 2011/8/10 Biao Han <ha...@cn.ibm.com>
> > (We should send this to project mailing list, but we don't have one
> > yet. so sorry for interrupt those guys in incubator general mailing
list)
> >
> > ODF Toolkit move to Apache
> > 1. SVN account has been created and is now available for use. We
> > will discuss and start the code move after mail lists are ready;
> > 2. The first board meeting is scheduled for Wed, 17 August 2011, 10
> > am Pacific. We have submitted a quarterly board report to here.
> > 3. As we have been an Apache incubator project, so we will discuss
> > and release ODF Toolkit in the new community. The original release
> > plan have to be cancelled.
> >
> > Simple ODF
> > 1. Reviewed and pushed a bug about TextProperties (#bug 357).
> > 2. Reviewed and pushed three unit test coverage enhancement patches
> > (#bug 241) .
> > 3. The downloads of Simple ODF 0.6.5 has been to 204. This number
> > equals with Simple ODF 0.4. But version 0.4 uses more 6 months get
> > it, while version 0.6.5 uses only 40 days.
> >
> > ODFDOM
> > 1. Working on data signature. There are two issues caused by
> > OpenOffice block the process.
> > (1) OpenOffice.org generate a Namespace unaware signature document.
> > ODFDOM loads it fails.
> > (2) OpenOffice.org creates multiple X509Certificates instead of the
> > correct certification chain under ds:KeyInfo.
> > see also:
> > https://bugs.freedesktop.org/show_bug.cgi?id=39657 (ds namespace in
> > LibreOffice)
> > http://openoffice.org/bugzilla/show_bug.cgi?id=107864 (ds namespace in
OOo)
> > http://openoffice.org/bugzilla/show_bug.cgi?id=66276 (multiple
> > X509Certificate in OOo)
> > http://openoffice.org/bugzilla/show_bug.cgi?id=108286
> > We have to supply two modes to fix it. One follows ODF
> > specification, the other follows Open Office. The question is which
> > is the default?
> > 2. A new user: XDocReport uses ODFDOM to load and manipulate ODF
> > document. It's Java API to merge XML document created with MS Office
> > (docx) or OpenOffice (odt), LibreOffice (odt) with a Java model to
> > generate report and convert it if you need to another format (PDF,
> XHTML...).
> > Regards
> >
> > Biao Han (Devin)
> > SOA Standards Growth, Emerging Technology Institute(ETI), IBM China
> > Software Development Laboratory
> > Tel:(86-10)82450541
> > Email: hanbiao@cn.ibm.com
> > Address: 3/F Ring Building, No.28 Building, Zhong Guan Cun Software
> > Park, No. 8 Dong Bei Wang West Road, ShangDi, Haidian District,
> > Beijing, P.R.C.100193
Re: [odfdom-dev] Status of the Simple Java API for ODF and ODFDOM - 08/10/2011
Posted by Angelo zerr <an...@gmail.com>.
Hi Biao,
> Thanks for your contribution intention. But we found iText uses the AGPL
> license: http://itextpdf.com/terms-of-use/index.php
> So it would be difficult to use that in an Apache 2.0 licensed project.
>
Yes I thought that. That's very shame -(
>
> Do you have plan to supply a version using PDFBox<http://pdfbox.apache.org/index.html> pr
> FOP? Both of them will be OK for Apache 2.0 license.
> And as far as I know, PDFBox may be easier. Its API is similar with iText.
>
XDocReport uses iText because ODT->PDF processes like this :
1) load ODT with ODFDOM
2) visit ODFDOM and generate iText structure PDF per ODFDOM structure
Problem with FOP is that you must have XML FO to generate PDF. I have tried
to do that (without ODFDOM) with XSL-FO, but performance are very bad (even
with XSLT cache, use xsl:key to cache compute of styles....). Perhaps it's
possible to use FOP with pur Java (without XML FO) but I have not found
samples.
For PDFBox, I have never used. Do you think this library manage the same
thing than iText (Table, table row, images widget...) and with the same
peformance? I must study it to see if it's possible to implement a new
converter with PDFBox.
Thank a lot for your information;,
Regards Angelo
>
> Whatever, thank you for your eager contribution intention!
>
>
> >
> > Regards Angelo
> >
>
> > 2011/8/10 Biao Han <ha...@cn.ibm.com>
> > (We should send this to project mailing list, but we don't have one
> > yet. so sorry for interrupt those guys in incubator general mailing list)
> >
> > ODF Toolkit move to Apache
> > 1. SVN account has been created and is now available for use. We
> > will discuss and start the code move after mail lists are ready;
> > 2. The first board meeting is scheduled for Wed, 17 August 2011, 10
> > am Pacific. We have submitted a quarterly board report to here.
> > 3. As we have been an Apache incubator project, so we will discuss
> > and release ODF Toolkit in the new community. The original release
> > plan have to be cancelled.
> >
> > Simple ODF
> > 1. Reviewed and pushed a bug about TextProperties (#bug 357).
> > 2. Reviewed and pushed three unit test coverage enhancement patches
> > (#bug 241) .
> > 3. The downloads of Simple ODF 0.6.5 has been to 204. This number
> > equals with Simple ODF 0.4. But version 0.4 uses more 6 months get
> > it, while version 0.6.5 uses only 40 days.
> >
> > ODFDOM
> > 1. Working on data signature. There are two issues caused by
> > OpenOffice block the process.
> > (1) OpenOffice.org generate a Namespace unaware signature document.
> > ODFDOM loads it fails.
> > (2) OpenOffice.org creates multiple X509Certificates instead of the
> > correct certification chain under ds:KeyInfo.
> > see also:
> > https://bugs.freedesktop.org/show_bug.cgi?id=39657 (ds namespace in
> > LibreOffice)
> > http://openoffice.org/bugzilla/show_bug.cgi?id=107864 (ds namespace in
> OOo)
> > http://openoffice.org/bugzilla/show_bug.cgi?id=66276 (multiple
> > X509Certificate in OOo)
> > http://openoffice.org/bugzilla/show_bug.cgi?id=108286
> > We have to supply two modes to fix it. One follows ODF
> > specification, the other follows Open Office. The question is which
> > is the default?
> > 2. A new user: XDocReport uses ODFDOM to load and manipulate ODF
> > document. It's Java API to merge XML document created with MS Office
> > (docx) or OpenOffice (odt), LibreOffice (odt) with a Java model to
> > generate report and convert it if you need to another format (PDF,
> XHTML...).
> > Regards
> >
> > Biao Han (Devin)
> > SOA Standards Growth, Emerging Technology Institute(ETI), IBM China
> > Software Development Laboratory
> > Tel:(86-10)82450541
> > Email: hanbiao@cn.ibm.com
> > Address: 3/F Ring Building, No.28 Building, Zhong Guan Cun Software
> > Park, No. 8 Dong Bei Wang West Road, ShangDi, Haidian District,
> > Beijing, P.R.C.100193
>
Re: [odfdom-dev] Status of the Simple Java API for ODF and ODFDOM - 08/10/2011
Posted by Biao Han <ha...@cn.ibm.com>.
Angelo zerr <an...@gmail.com> wrote on 2011-08-11 21:22:08:
> From: Angelo zerr <an...@gmail.com>
> To: dev@odfdom.odftoolkit.org
> Cc: dev@simple.odftoolkit.org, dev@odftoolkit.odftoolkit.org,
> general@incubator.apache.org
> Date: 2011-08-11 21:22
> Subject: Re: [odfdom-dev] Status of the Simple Java API for ODF and
> ODFDOM - 08/10/2011
>
> Hi Biao,
>
> Thank a lot to mention XDocReport in your mail. I would like give
> some information about it. You can find XDocReport at http://
> code.google.com/p/xdocreport/. By default XDocReport generate report
> source 2 source (odt 2 odt, docx 2 docx...). At this step ODFDOM IS
> NOT Used. ODFDOM is used for convert ODT 2 XHTM or PDF that we have
called
> ODFDOMConverter
>
> THe ODFDOMConverter is Java implementation to convert ODT 2 PDF
> (with itext) and XHTML. This project is used by XDocReport (if you
> wish convert your generated report 2 XHTML, PDF) BUT you can use
> ODFDOMConverter without XDocReport (package is
org.odftoolkit.odfdom.converter
> )
>
> My idea was to give to ODFDOM Team the sources of the
> ODFDOMConverter project. But since you wish gives the project 2
> Apache, I'm not sure that ODFDOM Converter will interest Apacahe.
> Why? Because we are using iText for PDF and not FOP. I believe that
> Apache Fondation don't want use iText.
>
> We have the same proble with our DOCX converter http://
> code.google.com/p/xdocreport/wiki/XWPFConverter
>
> If you think iText is not a problem for Apache Fondation, we will
> happy to give your the ODFDOMConverter project.
Thanks for your contribution intention. But we found iText uses the AGPL
license: http://itextpdf.com/terms-of-use/index.php
So it would be difficult to use that in an Apache 2.0 licensed project.
Do you have plan to supply a version using PDFBox pr FOP? Both of them will
be OK for Apache 2.0 license.
And as far as I know, PDFBox may be easier. Its API is similar with iText.
Whatever, thank you for your eager contribution intention!
>
> Regards Angelo
>
> 2011/8/10 Biao Han <ha...@cn.ibm.com>
> (We should send this to project mailing list, but we don't have one
> yet. so sorry for interrupt those guys in incubator general mailing list)
>
> ODF Toolkit move to Apache
> 1. SVN account has been created and is now available for use. We
> will discuss and start the code move after mail lists are ready;
> 2. The first board meeting is scheduled for Wed, 17 August 2011, 10
> am Pacific. We have submitted a quarterly board report to here.
> 3. As we have been an Apache incubator project, so we will discuss
> and release ODF Toolkit in the new community. The original release
> plan have to be cancelled.
>
> Simple ODF
> 1. Reviewed and pushed a bug about TextProperties (#bug 357).
> 2. Reviewed and pushed three unit test coverage enhancement patches
> (#bug 241) .
> 3. The downloads of Simple ODF 0.6.5 has been to 204. This number
> equals with Simple ODF 0.4. But version 0.4 uses more 6 months get
> it, while version 0.6.5 uses only 40 days.
>
> ODFDOM
> 1. Working on data signature. There are two issues caused by
> OpenOffice block the process.
> (1) OpenOffice.org generate a Namespace unaware signature document.
> ODFDOM loads it fails.
> (2) OpenOffice.org creates multiple X509Certificates instead of the
> correct certification chain under ds:KeyInfo.
> see also:
> https://bugs.freedesktop.org/show_bug.cgi?id=39657 (ds namespace in
> LibreOffice)
> http://openoffice.org/bugzilla/show_bug.cgi?id=107864 (ds namespace in
OOo)
> http://openoffice.org/bugzilla/show_bug.cgi?id=66276 (multiple
> X509Certificate in OOo)
> http://openoffice.org/bugzilla/show_bug.cgi?id=108286
> We have to supply two modes to fix it. One follows ODF
> specification, the other follows Open Office. The question is which
> is the default?
> 2. A new user: XDocReport uses ODFDOM to load and manipulate ODF
> document. It's Java API to merge XML document created with MS Office
> (docx) or OpenOffice (odt), LibreOffice (odt) with a Java model to
> generate report and convert it if you need to another format (PDF,
XHTML...).
> Regards
>
> Biao Han (Devin)
> SOA Standards Growth, Emerging Technology Institute(ETI), IBM China
> Software Development Laboratory
> Tel:(86-10)82450541
> Email: hanbiao@cn.ibm.com
> Address: 3/F Ring Building, No.28 Building, Zhong Guan Cun Software
> Park, No. 8 Dong Bei Wang West Road, ShangDi, Haidian District,
> Beijing, P.R.C.100193