* roff escaped space character
@ 2012-07-29 15:06 Ingo Schwarze
0 siblings, 0 replies; only message in thread
From: Ingo Schwarze @ 2012-07-29 15:06 UTC (permalink / raw)
To: tech; +Cc: jmc, millert
on September 23, 2009, you have put the following descriptions
.It \e~ Ta non-breaking, non-collapsing space
.It \e Ta breaking, non-collapsing n-width space
However, chars.in has this:
CHAR(" ", ascii_nbrsp, 160)
CHAR("~", ascii_nbrsp, 160)
So the two are the same, which is correct behaviour for -Tascii.
I have just added a few lines to
showing that the code is indeed correct.
So, groff actually handles "\\ " as non-breaking as well.
Checking the current version of groff_char(7), i find this:
160 the ISO latin1 no-break space is mapped to `\~', the stretchable
However, i fail to find anything regarding "\\ ".
Apparently, the difference is that "\\~" is stretchable,
while "\\ " is fixed-width 1n?
Do you still remember where you got the idea from that "\\ "
is breaking (and 1n), or am i missing something?
The following would have to be changed if it turns out
that's actually a documentation error:
* mandoc_char(7), subsection "Spaces":
Part of that would have to be rewritten.
* mandoc_char(7), SPECIAL CHARACTERS section:
\ non-breaking, non-collapsing n-width space
\~ non-breaking, non-collapsing strechable space
* att.in, lib.in, st.in, mdoc_html.c, man_html.c:
We might keep "\\~" there in case we ever implement
variable width fonts in -Tps to get nicer spacing;
or should we use "\\ " to give a better example
regarding portability? I tend to leave that as it is.
I tought i might ask first before spending time cooking up
To unsubscribe send an email to email@example.com
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-07-29 15:06 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-29 15:06 roff escaped space character Ingo Schwarze
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).