camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-1898) Cannot generate the PDF manual
Date Wed, 12 Aug 2009 05:42:37 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53588#action_53588
] 

Claus Ibsen commented on CAMEL-1898:
------------------------------------

Hadrian can we get a RC out without the manual. We should really get one out sooner the better
to give people a chance to test it throughly.

The manual can always bee fixed later, generated and uploaded to the apache web site.
We should not hold a release because of this _minor_ issue.

And we do anticipate that we need another RC build before its final then the manual could
have been fixed in the meantime.


> Cannot generate the PDF manual
> ------------------------------
>
>                 Key: CAMEL-1898
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1898
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 2.0-M3
>            Reporter: Hadrian Zbarcea
>            Assignee: Hadrian Zbarcea
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: Picture 1.png
>
>
> While building the camel-manual we get the log below:
> {code}
> [INFO] About to execute PrinceXml (see www.princexml.com)
> [INFO]  prince /w1/apache/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html
/w1/apache/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.pdf
> [INFO] [prince] prince: /w1/apache/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html:36888:
error: Unexpected end tag : div
> [INFO] [prince] prince: /w1/apache/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html:36890:
error: Unexpected end tag : div
> [INFO] [prince] prince: /w1/apache/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html:36903:
error: Unexpected end tag : body
> [INFO] [prince] prince: warning: bad argument
> [INFO] [prince] prince: warning: bad argument
> [INFO] [prince] prince: warning: bad argument
> [INFO] [prince] prince: warning: no glyphs for character U+006E, fallback to '?'
> [INFO] [prince] Uncaught Mercury exception:
> [INFO] [prince] Software Error: no fallback glyph for character U+006E
> [ERROR] PDF Conversion failed due to return code: 1
> {code}
> The first errors are because of the html being improperly generated by the maven-html-to-pdf.
 The "prince: warning: bad argument" interestingly seem to be generated by prince having to
create its own font, which it cannot do, for cases where the requested font is not available,
like for instance a <b> bold tag with a Courier font.
> We know that the pdf was not generated in the 2.0-M3 release either.  The cause of this
errors popping up appears to be the wiki changes at apache. The fact that the book-in-one-page
is that big does not help either.  I quickly tried with the deployed version at http://camel.apache.org/book-in-one-page.html
and I get a very similar result unfortunately, so there's no quick fix or workaround it seems.
> I will try to resolve this asap.  Any help/ideas I could get are highly appreciated.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message