From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Cc: jmc@openbsd.org
Subject: line termination in manuals
Date: Sat, 22 Jan 2011 20:56:56 +0100 [thread overview]
Message-ID: <20110122195656.GE12520@iris.usta.de> (raw)
Hi,
deraadt@ pointed out that, if somebody would compile mandoc
on Windows, the C library would take care of different
conventions regarding line termination.
Besides, it goes without saying that text files on a UNIX
system use UNIX conventions, and UNIX tools working on them
expect that. This isn't documented for other text files,
for example configuration files of various tools, either.
OK?
Yours,
Ingo
Index: man.7
===================================================================
RCS file: /cvs/src/share/man/man7/man.7,v
retrieving revision 1.14
diff -u -r1.14 man.7
--- man.7 16 Jan 2011 02:56:47 -0000 1.14
+++ man.7 22 Jan 2011 19:46:09 -0000
@@ -53,9 +53,6 @@
.Nm
documents may contain only graphable 7-bit ASCII characters, the
space character, and the tab character.
-All manuals must have
-.Ux
-line termination.
.Pp
Blank lines are acceptable; where found, the output will assert a
vertical space.
Index: mdoc.7
===================================================================
RCS file: /cvs/src/share/man/man7/mdoc.7,v
retrieving revision 1.62
diff -u -r1.62 mdoc.7
--- mdoc.7 22 Jan 2011 14:05:28 -0000 1.62
+++ mdoc.7 22 Jan 2011 19:46:10 -0000
@@ -52,9 +52,6 @@
.Nm
documents may contain only graphable 7-bit ASCII characters, the space
character, and, in certain circumstances, the tab character.
-All manuals must have
-.Ux
-line terminators.
.Pp
If the first character of a line is a space, that line is printed
with a leading newline.
Index: roff.7
===================================================================
RCS file: /cvs/src/share/man/man7/roff.7,v
retrieving revision 1.8
diff -u -r1.8 roff.7
--- roff.7 9 Jan 2011 15:24:57 -0000 1.8
+++ roff.7 22 Jan 2011 19:46:10 -0000
@@ -57,10 +57,6 @@
documented in the
.Xr mandoc_char 7
manual.
-.Pp
-All manuals must have
-.Ux
-line terminators.
.Sh REQUEST SYNTAX
A request or macro line consists of:
.Pp
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2011-01-22 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 19:56 Ingo Schwarze [this message]
2011-01-22 20:05 ` Joerg Sonnenberger
2011-01-22 21:28 ` Ingo Schwarze
2011-01-22 21:35 ` Joerg Sonnenberger
2011-01-22 22:18 ` Ingo Schwarze
2011-01-22 22:28 ` Kristaps Dzonsons
2011-01-22 22:29 ` Joerg Sonnenberger
2011-01-22 22:59 ` Ingo Schwarze
2011-01-24 23:16 ` Kristaps Dzonsons
2011-01-25 0:09 ` Ingo Schwarze
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=20110122195656.GE12520@iris.usta.de \
--to=schwarze@usta.de \
--cc=jmc@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).