From: Ivana Hutarova Varekova <varekova-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: awk.1p, man.1p, printf.1p: groff syntax typos
Date: Thu, 18 Nov 2010 14:19:21 +0100 [thread overview]
Message-ID: <4CE527D9.6050902@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 188 bytes --]
Hello,
in posix man-pages (man-pages-posix-2003-a.tar.bz2) there are several
problems which cause groff syntax errors. The patches which fix them are
attached.
Ivana Hutarova Varekova
[-- Attachment #2: man-pages-posix-2003-awk.patch --]
[-- Type: text/x-patch, Size: 744 bytes --]
diff -up man-pages-3.29/man1p/awk.1p.qqq man-pages-3.29/man1p/awk.1p
--- man-pages-3.29/man1p/awk.1p.qqq 2008-06-05 11:22:12.000000000 +0200
+++ man-pages-3.29/man1p/awk.1p 2010-10-22 15:45:44.000000000 +0200
@@ -2197,7 +2197,7 @@ necessary to use parentheses to enforce
.LP
The \fIawk\fP program specified in the command line is most easily
specified within single-quotes (for example,
-'\fIprogram\fP') for applications using \fIsh\fP, because \fIawk\fP
+\fI'program'\fP) for applications using \fIsh\fP, because \fIawk\fP
programs commonly contain
characters that are special to the shell, including double-quotes.
In the cases where an \fIawk\fP program contains single-quote
diff -up man-pages-3.29/man1p/.qqq man-pages-3.29/man1p/
[-- Attachment #3: man-pages-posix-2003-man.patch --]
[-- Type: text/x-patch, Size: 404 bytes --]
diff -up man-pages-3.29/man1p/man.1p.pom man-pages-3.29/man1p/man.1p
--- man-pages-3.29/man1p/man.1p.pom 2008-06-05 11:22:12.000000000 +0200
+++ man-pages-3.29/man1p/man.1p 2010-10-22 13:35:55.000000000 +0200
@@ -44,10 +44,7 @@ command:
.RS
.nf
-\fBgrep -Ei '
-\fP\fIname
-name\fP\fB...
-'\fP \fIsummary-database\fP
+\fBgrep -Ei '\fP\fIname name\fP\fB...' \fP \fIsummary-database\fP
.fi
.RE
.LP
[-- Attachment #4: man-pages-posix-2003-printf.patch --]
[-- Type: text/x-patch, Size: 657 bytes --]
diff -up man-pages-3.29/man1p/printf.1p.ppp man-pages-3.29/man1p/printf.1p
--- man-pages-3.29/man1p/printf.1p.ppp 2008-06-05 11:22:12.000000000 +0200
+++ man-pages-3.29/man1p/printf.1p 2010-10-22 15:33:14.000000000 +0200
@@ -144,7 +144,8 @@ octal number that shall be converted to
numeric value specified by the octal number
.LP
.IP " *" 3
-\fB'\\c'\fP, which shall not be written and shall cause \fIprintf\fP
+sequence \fB'\\c'\fP
+which shall not be written and shall cause \fIprintf\fP
to ignore any remaining characters in the string
operand containing it, any remaining string operands, and any additional
characters in the \fIformat\fP operand
reply other threads:[~2010-11-18 13:19 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=4CE527D9.6050902@redhat.com \
--to=varekova-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.