From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Cc: jmc@openbsd.org, millert@openbsd.org
Subject: roff escaped space character
Date: Sun, 29 Jul 2012 17:06:38 +0200 [thread overview]
Message-ID: <20120729150638.GC10723@iris.usta.de> (raw)
Hi Kristaps,
on September 23, 2009, you have put the following descriptions
into mandoc_char(7):
.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
http://www.openbsd.org/cgi-bin/cvsweb/src/regress/usr.bin/mandoc/char/space/nobreak.in
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
space character.
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
actual patches...
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
reply other threads:[~2012-07-29 15:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120729150638.GC10723@iris.usta.de \
--to=schwarze@usta.de \
--cc=jmc@openbsd.org \
--cc=millert@openbsd.org \
--cc=tech@mdocml.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).