Bug 604465 - publican clean_ids inserts blank lines in <programlisting>s
Summary: publican clean_ids inserts blank lines in <programlisting>s
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 1.6
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-15 23:53 UTC by Lana Brindley
Modified: 2013-10-23 23:16 UTC (History)
5 users (show)

Fixed In Version: 2.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-05 04:16:37 UTC
Embargoed:


Attachments (Terms of Use)
Screenshot showing inserted blank lines. (39.78 KB, image/png)
2010-06-15 23:53 UTC, Lana Brindley
no flags Details

Description Lana Brindley 2010-06-15 23:53:57 UTC
Created attachment 424322 [details]
Screenshot showing inserted blank lines.

Description of problem:
After running "publican clean_ids", blank lines are inserted before the </programlisting> and </screen> tags.

Version-Release number of selected component (if applicable):
$ rpm -qa publican
publican-1.6.3-0.fc12.noarch

How reproducible:
Every time so far

Steps to Reproduce:
1. Write DocbookXML, including the text:
<programlisting>
deferral_window = 120
</programlisting>
2. Run publican clean_ids and reload page
3. Note text has changed to:
<programlisting>deferral_window = 120

</programlisting>
4. Repeat step 2.
5. Note text has changed to:
<programlisting>deferral_window = 120


</programlisting>
6. Repeat step 4 ad infinitum. Note lots of blank lines!
  
Actual results:
Every time clean_ids is run, an extra blank line is inserted into every <screen> and <programlisting> in the document.

Expected results:
No extraneous blank lines.

Additional info:
Screenshot of staged document attached.

Comment 1 Jeff Fearn 🐞 2010-06-16 02:05:37 UTC
Stopped clean_ids from adding new lines to verbatim items on exit.

Fixed in build; 1.6.3-0.t115


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