[ docbook-Bugs-3599520 ] manpages: spurious newline in output for <simpara><emphasis>

[SourceForge.net <no...@so...>]

Bugs item #3599520, was opened at 2013-01-04 12:54
Message generated for change (Settings changed) made by bobstayton
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373747&aid=3599520&group_id=21935

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: XSL
Group: output: manpages
>Status: Pending
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Rainer Müller (raimue)
>Assigned to: Robert Stayton (bobstayton)
Summary: manpages: spurious newline in output for <simpara><emphasis>

Initial Comment:
A spurious line break is added to the man page output when a <para> or <simpara> contains a <emphasis> tag as first children. This item in a definition list with multiple terms has an empty line between the term and its definition:

<variablelist>
<varlistentry>
<term>
bar
</term>
<listitem>
<simpara>
    <emphasis role="strong">abc</emphasis>def
</simpara>
</listitem>
</varlistentry>
</variablelist>

I compiled the full example source document attached to this report using the following command (on Mac OS X using docbook-xsl from MacPorts):
xsltproc -nonet /opt/local/share/xsl/docbook-xsl/manpages/docbook.xsl foo.xml

The generated man page output of the snippet above is the following:

.PP
bar
.RS 4

\fBabc\fRdef
.RE

The new line after ".RS 4" is unexpected and does not exist when adding at least one non-whitespace character in before the <emphasis> tag in the example source above. The attached file contains both a working (term "foo") and a broken example (term "bar").

This was encountered with docbook-xsl 1.76.1 and reproduced with the latest docbook-xsl 1.78.0. xsltproc is from libxslt 1.1.27. I tried to provide a minimal example, so the compilation returns some warnings due to missing fields, but they should not influence the result.

----------------------------------------------------------------------

Comment By: Robert Stayton (bobstayton)
Date: 2013-01-07 12:13

Message:
A fix for this issue has been added to the current codebase.
Please test the fix with the latest snapshot from:

  http://docbook.sourceforge.net/snapshots/


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373747&aid=3599520&group_id=21935