While building PDFs for standalone libraries (BB2 is one example) works without a glitch, we were unable to build the master "boost.pdf", due to what appears to be a problem in FOP: ... fop-nt ..\bin.v2\doc\debug\boost.pdf [INFO] FOP 0.20.4 [INFO] building formatting object tree [ERROR] property - "font-selection-strategy" is not implemented yet. [ERROR] property - "line-height-shift-adjustment" is not implemented yet. [ERROR] property - "last-line-end-indent" is not implemented yet. [INFO] [4] [INFO] [5] [INFO] [6] [INFO] [7] [INFO] [8] [INFO] [9] [INFO] [10] [INFO] [11] [INFO] [12] [ERROR] region-name 'xsl-footnote-separator' doesn't exist in the layout-master-set. [ERROR] property - "last-line-end-indent" is not implemented yet. ... [ERROR] property - "last-line-end-indent" is not implemented yet. [INFO] [17] [INFO] [18] [INFO] [19] [INFO] [20] [INFO] [21] [INFO] [22] [ERROR] java.lang.NullPointerException set JAVA_HOME=C:/WINDOWS/system32/java.exe C:/PROGRA~1/FOP-02~1.4/fop.bat ..\bin.v2\doc\debug\boost.fo ..\bin.v2\doc\debug\boost.pdf ...failed fop-nt ..\bin.v2\doc\debug\boost.pdf... ...failed updating 1 target... ...updated 32 targets... This is using: xsltproc --version xsltproc was compiled against libxml 20614, libxslt 10111 and libexslt 809 libxslt 10111 was compiled against libxml 20614 libexslt 809 was compiled against libxml 20614 DocBook XSL 1.66.1 stylesheets FOP 0.20.4/0.20.5 (identical results) on Windows. It's probably possible to get to the root of the issue by commenting out different parts of "doc/src/boost.xml" until it's buildable, but in what little time we could devote to investigating this, we didn't have much success going this route. It would be greatly appreciated if somebody could take a look at this. -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy writes:
While building PDFs for standalone libraries (BB2 is one example) works without a glitch, we were unable to build the master "boost.pdf", due to what appears to be a problem in FOP:
[ snip errors, see the original post for details -- http://article.gmane.org/gmane.comp.lib.boost.devel/112563 ]
It's probably possible to get to the root of the issue by commenting out different parts of "doc/src/boost.xml" until it's buildable, but in what little time we could devote to investigating this, we didn't have much success going this route.
It would be greatly appreciated if somebody could take a look at this.
Any volunteers to tackle this? If not resolved soon, this might leave us without "boost.pdf" in the release distribution. -- Aleksey Gurtovoy MetaCommunications Engineering
On Nov 1, 2004, at 11:27 PM, Aleksey Gurtovoy wrote:
It's probably possible to get to the root of the issue by commenting out different parts of "doc/src/boost.xml" until it's buildable, but in what little time we could devote to investigating this, we didn't have much success going this route.
It would be greatly appreciated if somebody could take a look at this.
Any volunteers to tackle this? If not resolved soon, this might leave us without "boost.pdf" in the release distribution.
I've previously had problems getting FOP to generate PDF. Surprisingly enough, it was the Q&A markup that was causing problems last time. I don't expect that I'll have time to look into this before the release :( Doug
participants (2)
-
Aleksey Gurtovoy -
Doug Gregor