On 26/03/2014 6:34 PM, Luis Bernardo wrote:

Since the FO in FOP is the same as the FO in XSL-FO and think there will be consensus that FOP will only ingest FO natively. That is my opinion too.

DITA-OT currently produces valid FO and there is no desire to change this unless FOP requires this. This is a working setup that leverages the current power of FOP to produce PDF documents from an OASIS standard. The role of the DITA sub-project would be to support the conversion of DocBook and DITA to FO and HTML and other formats through XSLT or other XML transformation tools.

Now, in principle, I have no objection in having a new sub-project under the XMLGraphics umbrella that will convert DITA input to FO output, specially if that leads to an expanded user base for FOP.

My hope would be that the huge DITA user community would help fund and support the FOP and XMLGraphics community and that the XML expertise here in the XMLGraphics team would help the DITA community to improve the tools available to convert DITA to useful output - HTML/CSS, OO, MS-Office, RTF, interactive Javascript/HTML5/CSS output and outputs that we can not predict today.

The DITA community consists of mainstream commercial institutions that depend on XML to integrate their technical and commercial documentation.

My inquiry is a first step in a long process but I think that there is a lot of mutual benefit to incorporating DITA-OT into Apache's XMLGraphics projects.


On 3/26/14, 7:12 PM, Ron Wheeler wrote:
On 26/03/2014 2:59 PM, Jan Tosovsky wrote:
On 2014-03-26 Christopher R. Maden wrote:
Although I don’t get a vote, I completely agree with Glenn that DITA
integration into FOP is completely inappropriate.

FOP consumes standardized XSL-FO.

DITA-OT should produce standardized XSL-FO. Period ;-)
It does but FOP does not support all PDF features so some of the things that people can express in DITA's XML can not produce the PDF output that people want/need.

>From my POV it has nothing to do with FOP, it is rather XSLT (or whatever) part.

But I agree FOP could be enhanced to be more conformant to the standard. It requires engaging developers and sponsors.

I would hope that engaging the DITA community that has the need and the resources will get the support for these features. The separation into tool-making and document making communities makes it harder for the tool guys to get funded or staffed.
The document makers don't have the knowhow to fix the tools.
There is a lot of potential locked up in the current situation.
Some ideas appear in this mailing list from time to time.

The DITA community has not been very good at pestering the FOP team to get things fixed. They have tended to accept that FOP is static and can not respond to the needs of the document makers.


Ron Wheeler
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

Reply via email to