[
https://issues.apache.org/jira/browse/QPID-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092341#comment-15092341
]
Alex Rudyy commented on QPID-6961:
----------------------------------
One more thing can be improved in generated html files is inclusion of
"Content-Type" into html header:
{code:xml}
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
{code}
Firefox renders html files with unspecified content-type using Western encoding
by default which does not render some of the unicode characters properly.
> Use maven to generate Java Broker and (legacy) Java Client docbook
> ------------------------------------------------------------------
>
> Key: QPID-6961
> URL: https://issues.apache.org/jira/browse/QPID-6961
> Project: Qpid
> Issue Type: Improvement
> Components: Documentation, Java Broker, Java Client
> Reporter: Keith Wall
> Assignee: Alex Rudyy
> Fix For: qpid-java-6.1
>
> Attachments:
> 0001-QPID-6961-Mechanically-translate-sources-from-DocBoo.patch
>
>
> Currently the docbook generation for the Java Broker and (legacy) JMS Client
> use Make.
> Switching it to use the docbkx-tools maven plugin will simplify the release
> process by eliminating a number of manual steps. It will remove the need to
> manually synchronise variables between the commonEntities files and the POMs.
> Also as docbkx-tools has no external dependencies (such as Doxia), it will
> mean developers on Windows PC with restricted toolset will be able to
> generate the docbooks.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
