From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Cc: Ingo Schwarze <schwarze@usta.de>, jmc@openbsd.org
Subject: Re: better spacing for standards
Date: Sun, 24 Apr 2011 01:10:13 +0200 [thread overview]
Message-ID: <4DB35C55.5000006@bsd.lv> (raw)
In-Reply-To: <20110423230631.GM18756@iris.usta.de>
> i'd like to resolve one gratuitious difference between mandoc and
> groff-1.21: mandoc breaks lines at some places in the middle of
> standard names where groff doesn't. This is annoying for automatic
> comparisons because it occurs at many places.
>
> The following slight changes are included to get identical text
> like in groff:
>
> * "AT&T System V.4 UNIX" -> "AT&T System\\~V Release\\~4 UNIX"
> * Add "Amendment 1", "Technical Corrigendum 1" to the 94/95 ISO C variants
> * "ANSI C" -> "ANSI\\~C89"
Ingo,
I'm fine with this, but please add some notes in chars.in as to the
reason why all the funny escapes are in place.
Thanks!
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2011-04-23 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 23:06 Ingo Schwarze
2011-04-23 23:10 ` Kristaps Dzonsons [this message]
2011-04-23 23:11 ` Kristaps Dzonsons
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=4DB35C55.5000006@bsd.lv \
--to=kristaps@bsd.lv \
--cc=jmc@openbsd.org \
--cc=schwarze@usta.de \
--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).