[ http://issues.apache.org/jira/browse/DERBY-408?page=comments#action_12443070 ] Kim Haase commented on DERBY-408: ---------------------------------
Here's another problem that occurs in the PDF and monohtml but not the plain HTML. It may well be related to the other problem. If you have two adjacent <ph> tags with white space between them, the white space is ignored. This happens outside of <codeblock> elements. For example, the JDBC 4 disclaimer that appears in the 10.2 docs begins as follows: <p><ph id="jdbc4disclaimer"> <note type="attention"> <ph conref="toolsconrefs.dita#prod/productshortname"></ph> <ph conref="toolsconrefs.dita#vers/fullversionnumber"></ph> includes JDBC 4.0 functionality based on a pre-release of Java SE 6. .... The conrefs translate to "Derby" and "Version 10.2". What shows up in the PDF is "DerbyVersion" all run together: Attention: DerbyVersion 10.2 includes JDBC 4.0 functionality based on a pre-release of Java SE 6. Putting both <ph> tags on the same line doesn't help. It's possible this only happens when the <ph> tags are inside another <ph>. > Fix formatting of manuals in PDF output > --------------------------------------- > > Key: DERBY-408 > URL: http://issues.apache.org/jira/browse/DERBY-408 > Project: Derby > Issue Type: Bug > Components: Documentation > Environment: all > Reporter: Jeff Levitt > Assigned To: Andrew McIntyre > Priority: Minor > Fix For: 10.3.0.0 > > Attachments: derby-408.diff > > > 1. The syntax boxes in many of the Derby manuals seem to output with extra > End-of-line feeds in the PDF's. Some syntax boxes print one word per line. > For example: > http://incubator.apache.org/derby/docs/tools/tools-single.html#rtoolsijpropref10135 > This might be a bug with the DITA toolkit, because the DITA source files dont > have these End-of-line feeds in them. > This bug was originally reported in the doc reviews for version 10.1: > http://issues.apache.org/jira/browse/DERBY-383 > (see Myrna's comments) > 2. Based on http://issues.apache.org/jira/browse/DERBY-384 comments to the > doc review (see Sunitha's comments), we need to figure out how to et the > table numbers to ascend. Currently, they all output as table 1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira