"\ "). the reason is that if a space occurs at the end of a line,
our processing causes it to be eaten. a real-world case of this is
the mysql(1) man page. appending the "\&" prevents that
character=" "
u:name="NO-BREAK SPACE"
u:entity="nbsp"
- string="\ "
+ string="\ \&"
u:block="C1 Controls And Latin-1 Supplement (Latin-1 Supplement)"
u:class="symbols"
/>
<!-- * Unfortunately, roff seems to do some weird things with -->
<!-- * long lines that only have words separated by "\~" -->
<!-- * spaces, so it's safer just to stick with the "\ " space -->
- <xsl:with-param name="replacement">\ </xsl:with-param>
+ <!-- * -->
+ <!-- * We append a "\&" to handle the case of a no-break space that -->
+ <!-- * appears at the end of a line - because later processing will -->
+ <!-- * cause that space to get eaten otherwise. -->
+ <xsl:with-param name="replacement">\ \&</xsl:with-param>
</xsl:call-template>
</xsl:template>