Bug 460393 - Different spacing before & after <programlisting>
Different spacing before & after <programlisting>
Product: Publican
Classification: Community
Component: publican (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Fearn
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-08-27 21:28 EDT by Darrin Mison
Modified: 2010-11-23 23:18 EST (History)
2 users (show)

See Also:
Fixed In Version: 0.35
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-08-27 21:53:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Darrin Mison 2008-08-27 21:28:14 EDT
The spacing after <programlisting> is less than the spacing before it.  It makes the content after it look associated, almost like a title, especially if it is only a single line.  Ideally the spacing either side should be the same.

I have only noticed this in html, I haven't checked pdf.

Example code & screenshot of this attached.
<para>The database can be automatically created if the specified user has enough rights to create tables. 
        Next make sure the isCreateDatabase flag is set to true, and that the sqlFiles parameter settings point 
        to the database you are using. The jUDDI creation scripts are located in the <filename>juddi.jar</filename>.</para>

<programlisting>&lt;!-- &lt;entry key=”juddi.tablePrefix”&gt;JUDDI_&lt;/entry&gt; --&gt;
&lt;entry key="juddi.isCreateDatabase"&gt;true&lt;/entry&gt;
&lt;entry key="juddi.databaseExistsSq"&gt;select * from ${prefix}BUSINESS_ENTITY
&lt;entry key="juddi.sqlFiles"&gt;
	juddi sql/mysql/insert_publishers.sql
        <para>jUDDI supports the following databases:</para>
Comment 1 Jeff Fearn 2008-08-27 21:53:51 EDT
We have done some major work on fixing the white space for the next version, in both HTML and PDF.

0.35 will be out with the week.

Cheers, Jeff.

Note You need to log in before you can comment on or make changes to this bug.