Menu
▾
▴
[ docbook-Bugs-2793877 ] man: a leading space in a ulink leads to a newline
|
From: SourceForge.net <no...@so...> - 2009-07-18 17:55:31
|
Bugs item #2793877, was opened at 2009-05-19 16:17 Message generated for change (Settings changed) made by mzjn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=2793877&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: Daniel Leidert (dleidert) Assigned to: Nobody/Anonymous (nobody) Summary: man: a leading space in a ulink leads to a newline Initial Comment: Consider the following sample: This is <ulink url='about:blank'> not</ulink>. This renders as (note the linebreak): This is not[1]. If you compare the result from the sample with one, which doesn't contain a leading, space, then you get this: -\m[blue]\fB not\fR\m[]\&\s-2\u[1]\d\s+2\&. +\m[blue]\fBnot\fR\m[]\&\s-2\u[1]\d\s+2\&. Following GTROFF/GROFF, a line beginning with a space (and that's the case here; macros are not considered), leads to a linebreak (see "Implicit Line Breaks"). The leading space needs to be removed or preceded by a '\&'. Probably a simple starts-with() test can do the job. See http://bugs.debian.org/519442. ---------------------------------------------------------------------- Comment By: Mauritz Jeanson (mzjn) Date: 2009-07-18 19:55 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=2793877&group_id=21935 |