RE: DITA-OT and FOP

2014-03-30 Thread Jan Tosovsky
On 2014-03-26 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.
  +1
 
  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.
 

There are two possible interpretations:
(1) user's intent cannot be achieved by XSL-FO
(2) user's intent can be achieved by XSL-FO, but the given functionality is not 
supported by FOP

Anyway, it would be nice to collect these requests (wish list) and create a 
poll targetting DITA community to get real demand for them. If there is 
something FOP related, FOP devs could roughly estimate mandays (and thereof 
costs). The final part is to find sponsors or involve crowdfunding.

But keep in mind that XSL-FO is loosing its attraction. Its standardization has 
been discontinued and no one can expect new features in the near future. I 
strongly suggest joining already mentioned W3C PPL group 
http://www.w3.org/community/ppl/ which is trying to move these things forward.

Standardization has moved primarily into the CSS. There are many proposals 
trying to enhance this standard with paged media related stuff. It is clear 
that this is considered as the future. Check also this article:
http://alistapart.com/article/building-books-with-css3

I personally think it would be much easier to attract developers to create a 
completely new paged media CSS engine than to add several niche XSL-FO features 
into FOP. But when mentioning the new engine, I don't think it is a good idea. 
Sooner or later these CSS features will be adopted by major browsers and in 
that time it won't be necessary to produce PDFs at all :-) 

PDF engines (XSL-FO, CSS) will survive only if they offer any added value. I 
can think of an export into other formats (PS, AFP), a sophisticated index 
rendering (XSL-FO 1.1) or microtypography features 
http://en.wikipedia.org/wiki/Microtypography (not covered by standards yet). 
But AFAIK the latter would require major FOP redesign...

Jan




Re: DITA-OT and FOP

2014-03-30 Thread Ron Wheeler
These are great ideas and I think that getting the DITA community which 
is skilled at document management and document authoring connected with 
the people here who are looking at these issues from a technical point 
of view could energize the modernization of document production.
DITA provides an authoring language that is independent of the output 
format and media. The language is XML so the processing technology has 
to start with XML but could have the output in any form (currently HTML 
and PDF but there is no theoretical restrictions).


More comments in-line.

On 30/03/2014 5:19 PM, Jan Tosovsky wrote:

On 2014-03-26 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.

+1

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.


There are two possible interpretations:
(1) user's intent cannot be achieved by XSL-FO
(2) user's intent can be achieved by XSL-FO, but the given functionality is not 
supported by FOP

Another possible reason
(3) the DITA-OT developers have not been able how to build the XSLT to 
get the required XSL-FO.


I think that it will take a collaboration between the DITA-OT developers 
and the developers of FOP to determine which features are blocked by 
each of these reasons.



Anyway, it would be nice to collect these requests (wish list) and create a 
poll targetting DITA community to get real demand for them. If there is 
something FOP related, FOP devs could roughly estimate mandays (and thereof 
costs). The final part is to find sponsors or involve crowdfunding.

But keep in mind that XSL-FO is loosing its attraction. Its standardization has 
been discontinued and no one can expect new features in the near future. I 
strongly suggest joining already mentioned W3C PPL group 
http://www.w3.org/community/ppl/ which is trying to move these things forward.
I can not imagine that PDF will disappear in the intermediate term but 
mobile is likely to shift the emphasis on DITA-HTML and CSS.

Standardization has moved primarily into the CSS. There are many proposals 
trying to enhance this standard with paged media related stuff. It is clear 
that this is considered as the future. Check also this article:
http://alistapart.com/article/building-books-with-css3




I personally think it would be much easier to attract developers to create a 
completely new paged media CSS engine than to add several niche XSL-FO features 
into FOP. But when mentioning the new engine, I don't think it is a good idea. 
Sooner or later these CSS features will be adopted by major browsers and in 
that time it won't be necessary to produce PDFs at all :-)
The supposes that paper documentation will disappear. There are 
regulatory issues, industry practices, etc. that need to change.
There will still be face to face meetings where someone wants to hand a 
piece of paper to someone for the next few years.

PDF engines (XSL-FO, CSS) will survive only if they offer any added value. I 
can think of an export into other formats (PS, AFP), a sophisticated index 
rendering (XSL-FO 1.1) or microtypography features 
http://en.wikipedia.org/wiki/Microtypography (not covered by standards yet). 
But AFAIK the latter would require major FOP redesign...
Collaboration with the largest authoring community might help keep the 
XMLGraphics group at the forefront of these ideas.

Jan






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



[jira] [Commented] (FOP-2360) Can no longer get -awt (FOP viewer) to work

2014-03-30 Thread Luis Bernardo (JIRA)

[ 
https://issues.apache.org/jira/browse/FOP-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13954864#comment-13954864
 ] 

Luis Bernardo commented on FOP-2360:


the issue with headless was fixed a long time ago in trunk: 
http://svn.apache.org/viewvc?view=revisionrevision=1390331. the exception you 
get I cannot reproduce in general although I have seen that in the past using a 
Mac. however, on Windows 7 and 8.1, I get an empty viewer so it seems there is 
an issue but not the one reported.

 Can no longer get -awt (FOP viewer) to work
 ---

 Key: FOP-2360
 URL: https://issues.apache.org/jira/browse/FOP-2360
 Project: Fop
  Issue Type: Bug
  Components: awt renderer
Affects Versions: 1.1
 Environment: Windows 7, Windows 8.1
Reporter: nick.heyworth
 Attachments: tmp.fo


 Calling
 fop.bat -fo tmp.fo -awt
 results in
 SEVERE: Exception
 java.awt.HeadlessException
 due to
 -Djava.awt.headless=true
 in fop.bat which is there since FOP 1.1. Removing this at least opens the 
 viewer, but no document is displayed, and I get
 org.apache.fop.apps.FOPException: Requested page number is out of range: 0; 
 only 0 page(s) available.
 This occurs for any XML-FO file; an example is attached.



--
This message was sent by Atlassian JIRA
(v6.2#6252)