[ docbook-Bugs-3524417 ] output of email element in manpages suboptimal

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

Bugs item #3524417, was opened at 2012-05-07 10:31
Message generated for change (Comment added) made by bobstayton
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=373747&aid=3524417&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: Peter Eisentraut (petere78)
>Assigned to: Robert Stayton (bobstayton)
Summary: output of email element in manpages suboptimal

Initial Comment:
An email element in manpages will be rendered simply as plain text.  That's not broken, but it could be better.  There is support for email elements in *info sections, but nothing for appearance in normal text.

What happens is that the email element is actually processed by the html layer, which calls the template inline.monoseq with parameter content.  But the manpages version of the inline.monoseq template does not use the parameter content, and so it simply falls back to processing the children.  This could be made more consistent, and then the email element could be processed like in html in monospace with angle brackets by default.

Attached is an example document, which I processed with xsltproc /usr/share/xml/docbook/stylesheet/docbook-xsl/manpages/docbook.xsl test.xml .

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

>Comment By: Robert Stayton (bobstayton)
Date: 2012-10-26 15:44

Message:
I did as suggested and added the 'content' param to inline.monoseq, and
that seems to fix the email address format.

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

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