You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Hadrian Zbarcea (JIRA)" <ji...@apache.org> on 2009/08/11 01:06:35 UTC
[jira] Created: (CAMEL-1898) Cannot generate the PDF manual
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
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.
[jira] Updated: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated CAMEL-1898:
-----------------------------------
Affects Version/s: (was: 2.0-M3)
2.0.0
Fix Version/s: (was: 2.0.0)
2.1.0
> 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.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.1.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.
[jira] Commented: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58861#action_58861 ]
Claus Ibsen commented on CAMEL-1898:
------------------------------------
After the Apache attack the confluence wiki now appears to return the book in one page, but now there is an issue with the maven html2pdf plugin reporting about a missing div tag.
> 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.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.3.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53576#action_53576 ]
Hadrian Zbarcea commented on CAMEL-1898:
----------------------------------------
Yes Willem, it works much better with prince 7.0b1.
One issue is the following div generated by Confluence near the end of every page:
{code}
</div>
<br clear="none" class="clear">
</div>
{code}
Another (bigger) issue is the css for the code. I'll try to get that fixed tomorrow.
> 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.
[jira] Updated: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated CAMEL-1898:
-----------------------------------
Fix Version/s: (was: 2.1.0)
2.2.0
> 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.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.2.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.
[jira] Commented: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58896#action_58896 ]
Claus Ibsen commented on CAMEL-1898:
------------------------------------
@Willem
Ah yeah of course. I bet I didn't notice the http redirect when using a browser :) Good catch.
> 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.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.3.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated CAMEL-1898:
-----------------------------------
Priority: Major (was: Blocker)
The pdf manual is now generated, but there is an issue with the CSS that depends more on the wiki than the code.
> 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
> 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.
[jira] Commented: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53575#action_53575 ]
Willem Jiang commented on CAMEL-1898:
-------------------------------------
@ hadrian
I tried it on my mac box with latest beta version of prince 7.0b1, I don't got the error of the bad argument.
And the pdf file was generated.
{code}
[INFO] [prince] prince: /Users/jiangning/Work/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html:36959: error: Unexpected end tag : div
[INFO] [prince] prince: /Users/jiangning/Work/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html:36961: error: Unexpected end tag : div
[INFO] [prince] prince: /Users/jiangning/Work/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html:36974: error: Unexpected end tag : body
[INFO] [prince] prince: http://www.enterpriseintegrationpatterns.com/img/ChannelIcon.gif: warning: Unknown image MIME type: text/html
[INFO] Stored: /Users/jiangning/Work/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.pdf
{code}
But the pdf have some formate issue of the code sections, please see the captured file.
> 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
>
>
> 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.
[jira] Issue Comment Edited: (CAMEL-1898) Cannot generate the PDF
manual
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53575#action_53575 ]
Willem Jiang edited comment on CAMEL-1898 at 8/10/09 6:44 PM:
--------------------------------------------------------------
@ hadrian
I tried it on my mac box with latest beta version of prince 7.0b1, I didn't get the error of the bad argument.
And the pdf file was generated.
{code}
[INFO] [prince] prince: /Users/jiangning/Work/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html:36959: error: Unexpected end tag : div
[INFO] [prince] prince: /Users/jiangning/Work/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html:36961: error: Unexpected end tag : div
[INFO] [prince] prince: /Users/jiangning/Work/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html:36974: error: Unexpected end tag : body
[INFO] [prince] prince: http://www.enterpriseintegrationpatterns.com/img/ChannelIcon.gif: warning: Unknown image MIME type: text/html
[INFO] Stored: /Users/jiangning/Work/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.pdf
{code}
But the pdf have some formate issue of the code sections, please see the screen captured file that I attached with this JIRA.
was (Author: njiang):
@ hadrian
I tried it on my mac box with latest beta version of prince 7.0b1, I don't got the error of the bad argument.
And the pdf file was generated.
{code}
[INFO] [prince] prince: /Users/jiangning/Work/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html:36959: error: Unexpected end tag : div
[INFO] [prince] prince: /Users/jiangning/Work/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html:36961: error: Unexpected end tag : div
[INFO] [prince] prince: /Users/jiangning/Work/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.html:36974: error: Unexpected end tag : body
[INFO] [prince] prince: http://www.enterpriseintegrationpatterns.com/img/ChannelIcon.gif: warning: Unknown image MIME type: text/html
[INFO] Stored: /Users/jiangning/Work/camel/trunk/tooling/camel-manual/target/site/manual/camel-manual-2.0-SNAPSHOT.pdf
{code}
But the pdf have some formate issue of the code sections, please see the captured file.
> 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.
[jira] Resolved: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea resolved CAMEL-1898.
------------------------------------
Resolution: Fixed
> 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.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.3.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.
[jira] Commented: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Issue Comment Edited: (CAMEL-1898) Cannot generate the PDF
manual
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58891#action_58891 ]
Hadrian Zbarcea edited comment on CAMEL-1898 at 4/16/10 9:43 AM:
-----------------------------------------------------------------
When I used wget http://cwiki.apache.org/confluence/display/CAMEL/Book+In+One+Page to get the page,
the request was redirect to https://cwiki.apache.org/confluence/display/CAMEL/Book+In+One+Page.
So I changed the html2pdf plugin's url, then the plugin can get the page rightly.
After checking the generated PDF, all the content in the 'code' section are gone :(.
I don't know if it relates to the CSS, maybe some CSS expert can help us.
was (Author: njiang):
When I used wget http://cwiki.apache.org/confluence/display/CAMEL/Book+In+One+Page to get the page,
the request was redirect to https://cwiki.apache.org/confluence/display/CAMEL/Book+In+One+Page.
So I changed the html2pdf plugin's url, then the plugin can get the page rightly.
After checking the generated PDF, all the content in the {code} section are gone :(.
I don't know if it relates to the CSS, maybe some CSS expert can help us.
> 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.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.3.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated CAMEL-1898:
-----------------------------------
Fix Version/s: (was: 2.2.0)
2.3.0
> 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.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.3.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.
[jira] Updated: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang updated CAMEL-1898:
--------------------------------
Attachment: Picture 1.png
> 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.
[jira] Commented: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58874#action_58874 ]
Hadrian Zbarcea commented on CAMEL-1898:
----------------------------------------
I think there is a trickier issue related to some headers, I suspect ContentLength. It sometimes happens with wget as well. I'll need to find some time to look into this, hopefully this weekend.
> 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.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.3.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58862#action_58862 ]
Claus Ibsen commented on CAMEL-1898:
------------------------------------
Hadrian can you try it out? What is the maven goal btw to generate the manual?
> 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.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.3.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53611#action_53611 ]
Claus Ibsen commented on CAMEL-1898:
------------------------------------
@Hadrian
If that psg:sign issue is still around I suggest to revert back the changes in the pom xml files to as there where for the M3 release so we can get 2.0 out.
And its also very important that releases can be build on Max OS X as that is what all/most of all committers use.
And it should be possible for them /us/other than you to do releases as well.
We need a bit quicker pace on release cycles for Camel. For instance a 1.6.2 should also be out in the near future.
> 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.
[jira] Commented: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58891#action_58891 ]
Willem Jiang commented on CAMEL-1898:
-------------------------------------
When I used wget http://cwiki.apache.org/confluence/display/CAMEL/Book+In+One+Page to get the page,
the request was redirect to https://cwiki.apache.org/confluence/display/CAMEL/Book+In+One+Page.
So I changed the html2pdf plugin's url, then the plugin can get the page rightly.
After checking the generated PDF, all the content in the {code} section are gone :(.
I don't know if it relates to the CSS, maybe some CSS expert can help us.
> 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.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.3.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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59163#action_59163 ]
Claus Ibsen commented on CAMEL-1898:
------------------------------------
I think the manual can be downloaded now. So we should be able to generate the manual.
> 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.0
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.3.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.
[jira] Commented: (CAMEL-1898) Cannot generate the PDF manual
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53628#action_53628 ]
Claus Ibsen commented on CAMEL-1898:
------------------------------------
@Hadrian
Can you give an ETA when a RC can be released? You said that you thought the pgp:sign issue was resolved?
We cant keep postponing a release, a lot of other Apache releases depend on Camel 2.0 being GA.
> 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.