Package: tin
Version: 1:2.6.4-1
Severity: minor
Tags: patch
* What led up to the situation?
Checking for defects with a new version
test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man
page"
[Use "groff -e ' $' -e '\\~$' <file>" to find obvious trailing spaces.]
["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).
[The fate of "test-nroff" was decided in groff bug #55941.]
* What was the outcome of this action?
an.tmac:<stdin>:2841: style: 1 leading space(s) on input line
* What outcome did you expect instead?
No output (no warnings).
-.-
General remarks and further material, if a diff-file exist, are in the
attachments.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.12-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1),
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages tin depends on:
ii debconf [debconf-2.0] 1.5.89
ii libc6 2.40-6
ii libcanlock3 3.3.0-1+b2
ii libgsasl18 2.2.1-1+b2
ii libicu72 72.1-6
ii libidn2-0 2.3.7-2+b1
ii libncursesw6 6.5+20250125-2
ii libpcre2-8-0 10.44-5
ii libssl3t64 3.4.0-2
ii libtinfo6 6.5+20250125-2
ii liburiparser1 0.9.8+dfsg-2
ii libuu0 0.5.20+20241111-1
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
Versions of packages tin recommends:
ii exim4-daemon-light [mail-transport-agent] 4.98-3+b1
Versions of packages tin suggests:
ii gnupg 2.2.46-1
ii ispell 3.4.06-1
-- debconf information excluded
Input file is tin.5
Output from "mandoc -T lint tin.5": (shortened list)
35 skipping paragraph macro: sp after PP
-.-.
Output from "test-groff -mandoc -t -ww -z tin.5": (shortened list)
1 Use macro '.B' for one argument or split argument.
1 Use macro '.I' for one argument or split argument.
1 .BR is for at least 2 arguments, got 1
1 .IR is for at least 2 arguments, got 1
-.-.
Change '-' (\-) to '\(en' (en-dash) for a (numeric) range.
GNU gnulib has recently (2023-06-18) updated its
"build_aux/update-copyright" to recognize "\(en" in man pages.
tin.5:307:news.software.b! 1\-666,669
tin.5:309:news.software.nntp: 1\-13245,13247,13249
tin.5:311:news.software.readers: 1\-19567,19571\-19597
tin.5:898:subj=\\b(cd|[rk]?)?tin(d|pre)?[\-.0\-9]*\\b
tin.5:1210:[::1]:1119 /tmp/localhost6\-1119 lh6
-.-.
Use "\e" to print the escape character instead of "\\" (which gets
interpreted in copy mode).
190:image/*;\\
193:xv \-8 \-geometry +0 '%s';\\
195:description=%{name} %t\-Image;\\
197:test=test "$DISPLAY" != "";\\
202:message/rfc822;\\
205:${PAGER:\-"more"} '%s';\\
207:edit=${EDITOR:\-"vi"} '%s';\\
209:compose=${EDITOR:\-"vi"} '%s';\\
211:print=a2ps '%s';\\
898:subj=\\b(cd|[rk]?)?tin(d|pre)?[\-.0\-9]*\\b
906:path=\\.googlegroups\\.com!not-for-mail$
907:msgid_only=@googlegroups\\.com>
-.-.
Use the word (in)valid instead of (il)legal,
if not related to legal matters.
See "www.gnu.org/prep/standards".
Think about translations into other languages!
tin.5:65:The "type" field is simply any legal content type name. It is the
string
[Following not changed in a patch]
tin.5:851:\fB202\fP GNKSA_ILLEGAL_DOMAIN
tin.5:855:\fB206\fP GNKSA_ILLEGAL_LABEL_LENGTH
tin.5:856:\fB207\fP GNKSA_ILLEGAL_LABEL_HYPHEN
tin.5:857:\fB208\fP GNKSA_ILLEGAL_LABEL_BEGNUM
tin.5:864:\fB400\fP GNKSA_ILLEGAL_UNQUOTED_CHAR
tin.5:865:\fB401\fP GNKSA_ILLEGAL_QUOTED_CHAR
tin.5:866:\fB402\fP GNKSA_ILLEGAL_ENCODED_CHAR
tin.5:868:\fB404\fP GNKSA_ILLEGAL_PAREN_CHAR
-.-.
Strings longer than 3/4 of a standard line length (80)
Use "\:" to split the string at the end of an output line, for example a
long URL (web address)
317 .I
${TIN_HOMEDIR:\-"$HOME"}/.tin/$NNTPSERVER${NNTPPORT:+":$NNTPPORT"}/.oldnewsrc
348 .I ${TIN_INDEX_MAILDIR:\-"${TIN_HOMEDIR:\-"$HOME"}/.tin"}/.mail/
356 .I
${TIN_INDEX_NEWSDIR:\-"${TIN_HOMEDIR:\-"$HOME"}/.tin"}/.news${NNTPSERVER:+"\-$NNTPSERVER"}/
364 .I ${TIN_INDEX_SAVEDIR:\-"${TIN_HOMEDIR:\-"$HOME"}/.tin"}/.save/
914 .I
${TIN_HOMEDIR:\-"$HOME"}/.tin/keymap${${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}:+".${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}"}
916 .I
/etc/tin/keymap${${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}:+".${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}"}
1258 .I ${TIN_HOMEDIR:\-"$HOME"}/.tin/$NNTPSERVER${NNTPPORT:+":$NNTPPORT"}/motd
1269 .I
${TIN_HOMEDIR:\-"$HOME"}/.tin/$NNTPSERVER${NNTPPORT:+":$NNTPPORT"}/msglog
1279 .I
${TIN_HOMEDIR:\-"$HOME"}/.tin/$NNTPSERVER${NNTPPORT:+":$NNTPPORT"}/newsgroups
1298 .I
${TIN_HOMEDIR:\-"$HOME"}/.tin/$NNTPSERVER${NNTPPORT:+":$NNTPPORT"}/serverrc
2145 The news \fI${TIN_LIBDIR:\-NEWSLIBDIR}"/"${TIN_ACTIVEFILE:\-active}\fR file
-.-.
Wrong distance between sentences in the input file.
Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
Mark a final abbreviation point as such by suffixing it with "\&".
Some sentences (etc.) do not begin on a new line.
N.B.
The number of lines affected can be too large to be in a patch.
18:newsreader. All files are expected to have unix style ('\(rsn' aka LF) line
[...]
[Similar lines removed from the list]
[...]
2866:which the fields will appear in the database. See also
-.-.
Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.
Add "\:" to split the string for the output, "\<newline>" in the source.
Line 356, length 94
.I
${TIN_INDEX_NEWSDIR:\-"${TIN_HOMEDIR:\-"$HOME"}/.tin"}/.news${NNTPSERVER:+"\-$NNTPSERVER"}/
Line 914, length 155
.I
${TIN_HOMEDIR:\-"$HOME"}/.tin/keymap${${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}:+".${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}"}
Line 916, length 134
.I
/etc/tin/keymap${${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}:+".${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}"}
Line 1991, length 94
\fBNFKC_CF\fP: Compatibility Decomposition, followed by Canonical Composition
and Case Folding
Line 2335, length 86
\fBLast posting date (descending)\fP, sort threads by date of last posting
descending.
Line 2337, length 84
\fBLast posting date (ascending)\fP, sort threads by date of last posting
ascending.
-.-.
Use \(en (en-dash) for a dash at the beginning (en) of a line,
or between space characters,
not a minus (\-) or a hyphen (-), except in the NAME section.
tin.5:143:- it is a requirement for the environment in which the program will be
-.-.
Remove reverse slash (\) in front of a period (.) that is to be printed
as such, and can not come a control character in the first column of a line.
Use "\&" to protect the period to avoid that.
This is a sign, that the man page was transformed from another source
file with a program, whose name is NOT mentioned in a comment.
906:path=\\.googlegroups\\.com!not-for-mail$
907:msgid_only=@googlegroups\\.com>
-.-.
Put a parenthetical sentence, phrase on a separate line,
if not part of a code.
See man-pages(7), item "semantic newline".
Not considered in a patch, too many lines.
[List of affected lines removed]
-.-.
Use a hyphen between a number and the unit (name) "bit",
see "man-pages(7)", item "Terms to avoid".
1799:Allows 8bit characters unencoded in the header of mail message. Default is
2015:Allows 8bit characters unencoded in the header of a news article, if
2019:hierarchies where 8bit characters are used, using unencoded (raw)
2020:8bit characters in header is acceptable and sometimes even
-.-.
Use a character "\(->" instead of plain "->" or "\->".
1345:news.software.readers \-> n.software.readers \-> n.s.readers \-> n.s.r.
1670:Allows groups/articles to be selected by an arrow '\->' if set ON or
2543:If ON use UTF-8 characters for indicator ('\->'), thread/attachment tree
and
-.-.
Section headings (.SH and .SS) do not need quoting.
2890:.SH "SEE ALSO"
-.-.
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z
":
an.tmac:<stdin>:220: misuse, warning: .IR is for at least 2 arguments, got 1
Use macro '.I' for one argument or split argument.
an.tmac:<stdin>:722: misuse, warning: .BR is for at least 2 arguments, got 1
Use macro '.B' for one argument or split argument.
-.-
Additionally:
Long lines (with "/etc/tin/keymap): removed '.nf' and '.fi' around them.
Used '\:' to split them in the output.
Used '\<newline>' to shorten them in the input file.
--- tin.5 2025-02-17 01:42:37.594761150 +0000
+++ tin.5.new 2025-02-17 03:53:25.161185139 +0000
@@ -6,7 +6,7 @@
.\" Notes : needs a some work, see TODOs
.\"
.\"
-.TH tin 5 "December 24th, 2024" "2.6.4" "Usenet newsreader"
+.TH tin 5 "December 24th, 2024" 2.6.4 "Usenet newsreader"
.SH NAME
tin, rtin \- related files
@@ -62,7 +62,7 @@ may be continued by ending them with a b
Each individual mailcap entry consists of a content-type specification, a
command to execute, and (possibly) a set of optional "flag" values.
.sp
-The "type" field is simply any legal content type name. It is the string
+The "type" field is simply any valid content type name. It is the string
that will be matched against the ''Content\-Type:'' header to decide if this
is the mailcap entry that matches the current message. Additionally, the
type field may specify a subtype or a wildcard to match all subtypes.
@@ -140,7 +140,7 @@ exclusively to the view-command because
possible for such programs to tell whether or not they are on interactive
terminals.) The needsterminal command should be assumed to apply to the
compose and edit commands, too, if they exist. Note that this is NOT a test
-- it is a requirement for the environment in which the program will be
+\(en it is a requirement for the environment in which the program will be
executed, and should typically cause the creation of a terminal window when
not executed on either a real terminal or a terminal window.
.TP
@@ -187,28 +187,28 @@ Example:
.nf
# mailcap file example
.br
-image/*;\\
+image/*;\e
.br
.in +0.3i
-xv \-8 \-geometry +0 '%s';\\
+xv \-8 \-geometry +0 '%s';\e
.br
-description=%{name} %t\-Image;\\
+description=%{name} %t\-Image;\e
.br
-test=test "$DISPLAY" != "";\\
+test=test "$DISPLAY" != "";\e
.br
nametemplate=%s.IMAGE
.in -0.3i
.sp
-message/rfc822;\\
+message/rfc822;\e
.br
.in +0.3i
-${PAGER:\-"more"} '%s';\\
+${PAGER:\-"more"} '%s';\e
.br
-edit=${EDITOR:\-"vi"} '%s';\\
+edit=${EDITOR:\-"vi"} '%s';\e
.br
-compose=${EDITOR:\-"vi"} '%s';\\
+compose=${EDITOR:\-"vi"} '%s';\e
.br
-print=a2ps '%s';\\
+print=a2ps '%s';\e
.br
needsterminal
.in -0.3i
@@ -216,8 +216,7 @@ needsterminal
.RE
.RE
.PP
-
-.IR /etc/nntpserver
+.I /etc/nntpserver
.sp
.RS
default NNTP-server to read news from if not reading from the local spool.
@@ -226,7 +225,6 @@ that order), the default server given at
priority.
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.cancelsecret
.sp
.RS
@@ -236,7 +234,6 @@ is built with support for it. An empty s
creation in that case. This file should be readable only by the user.
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.mime.types
.br
.I /etc/mime.types
@@ -247,7 +244,6 @@ creation in that case. This file should
mime type / filename extension pairs
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.newsauth
.sp
.RS
@@ -282,18 +278,17 @@ news.example.com "top secret" james.bo
.RE
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.newsrc
.sp
.RS
-"\fInewsgroup\fR\fIflag\fR [\fIarticle\fR[,\fIarticle\fR |
\-\fIarticle\fR]...]"
+"\fInewsgroupflag\fR [\fIarticle\fR[,\fIarticle\fR | \-\fIarticle\fR]...]"
lines.
.TP
.B newsgroup
the name of the newsgroup.
.TP
.B flag
-a flag indicating if the group is subscribed ':' or not '!\&'.
+a flag indicating if the group is subscribed ':' or not '!'.
.TP
.B article
range of already read articles from that group; numbers separated by commas
@@ -304,15 +299,14 @@ Example:
.RS
# sample .newsrc file
.br
-news.software.b! 1\-666,669
+news.software.b! 1\(en666,669
.br
-news.software.nntp: 1\-13245,13247,13249
+news.software.nntp: 1\(en13245,13247,13249
.br
-news.software.readers: 1\-19567,19571\-19597
+news.software.readers: 1\(en19567,19571\(en19597
.RE
.RE
.PP
-
.nf
.I
${TIN_HOMEDIR:\-"$HOME"}/.tin/$NNTPSERVER${NNTPPORT:+":$NNTPPORT"}/.oldnewsrc
.fi
@@ -321,7 +315,6 @@ news.software.readers: 1\-19567,19571\-1
backup of \fI${TIN_HOMEDIR:\-"$HOME"}/.newsrc\fR
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.signature
.br
.I ${TIN_HOMEDIR:\-"$HOME"}/.Sig
@@ -330,44 +323,38 @@ backup of \fI${TIN_HOMEDIR:\-"$HOME"}/.n
signature
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.sigfixed
.sp
.RS
fixed part of a randomly generated signature, this will be added first
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/.inputhistory
.sp
.RS
history of last used strings
.RE
.PP
-
.I ${TIN_INDEX_MAILDIR:\-"${TIN_HOMEDIR:\-"$HOME"}/.tin"}/.mail/
.sp
.RS
mailgroups index files
.RE
.PP
-
.nf
-.I
${TIN_INDEX_NEWSDIR:\-"${TIN_HOMEDIR:\-"$HOME"}/.tin"}/.news${NNTPSERVER:+"\-$NNTPSERVER"}/
+.I
${TIN_INDEX_NEWSDIR:\-"${TIN_HOMEDIR:\-"$HOME"}/\:.tin"}/\:.news${NNTPSERVER:+"\-$NNTPSERVER"}/
.fi
.sp
.RS
newsgroups index files
.RE
.PP
-
.I ${TIN_INDEX_SAVEDIR:\-"${TIN_HOMEDIR:\-"$HOME"}/.tin"}/.save/
.sp
.RS
saved newsgroups index files
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/active.mail
.sp
.RS
@@ -402,14 +389,12 @@ This allows access to the 'inbox' and 'o
They are accessed via /home/foo/Mail/inbox and /home/foo/Mail/outbox
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/active.save
.sp
.RS
active file of user's saved newsgroups, used by \fBtin \-R\fP.
.RE
.PP
-
.\" tin uses inns old (pre 2.x) Path convention.
.\" as with inn >= 2.2.x getting more and more popular
.\" we should think about checking for the new Paths (/news/etc/)
@@ -719,7 +704,7 @@ This attribute works only on systems wit
or
.BR \%ucnv_* ()
and
-.BR \%ucsdet_getName()
+.BR \%ucsdet_getName ()
from libicui18n. It has no effect if undeclared_charset is also set.
.TP
Example:
@@ -766,7 +751,6 @@ undeclared_charset=ISO\-2022\-JP\-2
.RE
.RE
.PP
-
.\" TODO: add missing descriptions and explain things in detail.
.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/filter
.sp
@@ -895,26 +879,29 @@ comment=tind, ktin or cdtin as hot
group=*
case=1
score=hot
-subj=\\b(cd|[rk]?)?tin(d|pre)?[\-.0\-9]*\\b
+subj=\eb(cd|[rk]?)?tin(d|pre)?[\-.0\(en9]*\eb
comment=downscore postings in nsr from google based on
comment=message-id or path, if both hit they end up with
-comment=a score of -66 which is enough to mark them killed
+comment=a score of \-66 which is enough to mark them killed
group=news.software.readers
case=1
-score=-33
-path=\\.googlegroups\\.com!not-for-mail$
-msgid_only=@googlegroups\\.com>
+score=\-33
+path=.googlegroups.com!not-for-mail$
+msgid_only=@googlegroups.com>
.fi
.RE
.RE
.PP
-
-.nf
-.I
${TIN_HOMEDIR:\-"$HOME"}/.tin/keymap${${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}:+".${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}"}
-.br
-.I
/etc/tin/keymap${${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}:+".${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}"}
-.fi
+.\".nf
+.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/keymap${${LC_ALL:\-"${LC_MESSAGES:\:\
+\-"${LC_CTYPE:\:\-"$LANG"}"}"}:\:+".${LC_ALL:\:\-"${LC_MESSAGES:\:\
+\-"${LC_CTYPE:\:\-"$LANG"}"}"}"}
+.sp 1v
+.I
+/etc/tin/keymap${${LC_ALL:\-"${LC_MESSAGES:\-"${LC_CTYPE:\-"$LANG"}"}"}:\:\
++".${LC_ALL:\:\-"${LC_MESSAGES:\:\-"${LC_CTYPE:\:\-"$LANG"}"}"}"}
+.\".fi
.sp
.RS
Keymap-file, containing "\fIkeyname\fR \fIvalue\fR \fI[value]\fR" pairs
@@ -1158,7 +1145,6 @@ is bound to NULL it is unassigned.
.fi
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/mailgroups
.sp
.RS
@@ -1174,7 +1160,6 @@ is the name of the newsgroup
is a short single-line description of the group
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/newsrctable
.sp
.RS
@@ -1207,7 +1192,7 @@ news.tin.org .newsrc\-tin.org tinorg
.br
news.example.org /tmp/nrc\-ex example ex
.br
-[::1]:1119 /tmp/localhost6\-1119 lh6
+[::1]:1119 /tmp/localhost6\(en1119 lh6
.br
# catch all rules should go last
.br
@@ -1219,7 +1204,6 @@ news.example.org /tmp/nrc\-ex example ex
.RE
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/posted
.sp
.RS
@@ -1234,7 +1218,6 @@ message was sent to, the subject of the
messages ''Message\-ID'' if known.
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/Mail/posted
.sp
.RS
@@ -1244,7 +1227,6 @@ format. The filename can be changed by s
\fBposted_articles_file\fP.
.RE
.PP
-
.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/postponed.articles
.sp
.RS
@@ -1253,7 +1235,6 @@ Pool of postponed articles. This file is
format.
.RE
.PP
-
.nf
.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/$NNTPSERVER${NNTPPORT:+":$NNTPPORT"}/motd
.fi
@@ -1264,7 +1245,6 @@ It is automatically created on startup e
command-line option and is unlinked on exit.
.RE
.PP
-
.nf
.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/$NNTPSERVER${NNTPPORT:+":$NNTPPORT"}/msglog
.fi
@@ -1274,9 +1254,9 @@ File to store $\fBNNTPSERVER\fP and $\fB
error-messages. The file is overwritten on startup and meant for debugging.
.RE
.PP
-
.nf
-.I
${TIN_HOMEDIR:\-"$HOME"}/.tin/$NNTPSERVER${NNTPPORT:+":$NNTPPORT"}/newsgroups
+.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/$NNTPSERVER${NNTPPORT:+":$NNTPPORT"}/\
+newsgroups
.fi
.sp
.RS
@@ -1293,7 +1273,6 @@ is the name of the newsgroup
is a short single-line description of the group
.RE
.PP
-
.nf
.I ${TIN_HOMEDIR:\-"$HOME"}/.tin/$NNTPSERVER${NNTPPORT:+":$NNTPPORT"}/serverrc
.fi
@@ -1317,7 +1296,6 @@ Internal timestamp used by
to keep track of new newsgroups on the server.
.RE
.PP
-
.\" tin uses inns old (pre 2.x) Path convention.
.\" as with inn >= 2.2.x getting more and more popular
.\" we should think about checking for the new Paths (/news/etc/)
@@ -1342,7 +1320,7 @@ users who have no private tinrc yet (see
.B abbreviate_groupname
If ON abbreviate long newsgroup names at group selection level and article
level (if necessary) like this:
-news.software.readers \-> n.software.readers \-> n.s.readers \-> n.s.r.
+news.software.readers \(-> n.software.readers \(-> n.s.readers \(-> n.s.r.
Default is OFF.
.TP
.B add_posted_to_filter
@@ -1667,7 +1645,7 @@ Do not break long lines inside a word. T
except for verbatim blocks. See also \fBwrap_column\fP. Default is OFF.
.TP
.B draw_arrow
-Allows groups/articles to be selected by an arrow '\->' if set ON or
+Allows groups/articles to be selected by an arrow '\(->' if set ON or
by a highlighted bar if set OFF. Default is OFF.
.TP
.B editor_format
@@ -1796,7 +1774,7 @@ option. Killed articles simply does not
.RE
.TP
.B mail_8bit_header
-Allows 8bit characters unencoded in the header of mail message. Default is
+Allows 8-bit characters unencoded in the header of mail message. Default is
OFF. Turning it ON is effective only if \fBmail_mime_encoding\fP is also set
to 8bit. Leaving it OFF is safe for most users and compliant to Internet
Mail Standard (\fBRFC\%5322\fP and \fBRFC\%2047\fP). Default is OFF.
@@ -2012,12 +1990,12 @@ If ON put cursor at first unread article
article. Default is ON.
.TP
.B post_8bit_header
-Allows 8bit characters unencoded in the header of a news article, if
+Allows 8-bit characters unencoded in the header of a news article, if
set this also disables the generation of MIME-headers when they are
usually required. Default is OFF. Only enacted if
\fBpost_mime_encoding\fP is also set to 8bit. In a number of local
-hierarchies where 8bit characters are used, using unencoded (raw)
-8bit characters in header is acceptable and sometimes even
+hierarchies where 8-bit characters are used, using unencoded (raw)
+8-bit characters in header is acceptable and sometimes even
recommended so that you need to check the convention adopted in the
local hierarchy of your interest to determine what to do with this
and \fBpost_mime_encoding\fP.
@@ -2273,13 +2251,13 @@ The path that specifies the signature fi
up to or replying to an article. If the path is a directory then the
signature will be randomly generated from files that are in the specified
directory. If a file named \fI.sigfixed\fR does exist in that dir
-or \fI${TIN_HOMEDIR:-"$HOME"}/.sigfixed\fR does exist it will be
+or \fI${TIN_HOMEDIR:\-"$HOME"}/.sigfixed\fR does exist it will be
prepended to the chosen signature (first match counts). If the path starts
with a ! the program the path points to will be executed to generate a
signature. In order to pass the group name to the program, %G can be specified.
This will be replaced by the name of the current newsgroup. \-\-none will
suppress any signature. Default is \fI${TIN_HOMEDIR:\-"$HOME"}/.Sig\fR.
-See also \fI${TIN_HOMEDIR:-"$HOME"}/.sigfixed\fR.
+See also \fI${TIN_HOMEDIR:\-"$HOME"}/.sigfixed\fR.
.TP
.B signature_repost
If ON add signature to reposted articles. Default is ON.
@@ -2540,7 +2518,7 @@ and
must be in your $\fBPATH\fP. Default is OFF.
.TP
.B utf8_graphics
-If ON use UTF-8 characters for indicator ('\->'), thread/attachment tree and
+If ON use UTF-8 characters for indicator ('\(->'), thread/attachment tree and
ellipsis ('...'). Default is OFF.
.TP
.B verbatim_begin_regex
@@ -2624,7 +2602,6 @@ answering to a crossposting to several g
set.
.RE
.PP
-
.I /etc/tin/tin.defaults
.sp
.RS
@@ -2722,7 +2699,6 @@ file resides in \fInewslibdir\fR and is
so you only have to change this setting if your configuration differs.
.RE
.PP
-
.I /usr/local/share/locale/$LC_MESSAGES/LC_MESSAGES/tin.mo
.sp
.RS
@@ -2730,7 +2706,6 @@ translation into language specified in $
$\fBLANG\fP
.RE
.PP
-
.\" tin uses inns old (pre 2.x) Path convention.
.\" as with inn >= 2.2.x getting more and more popular
.\" we should think about checking for the new Paths
@@ -2795,7 +2770,6 @@ uses the LIST (\fBRFC\%3977\fP) or LIST
instead.
.RE
.PP
-
.I ${TIN_LIBDIR:\-NEWSLIBDIR}/active.times
.sp
.RS
@@ -2822,7 +2796,6 @@ if you read news via NNTP,
uses the NEWGROUPS (\fBRFC\%3977\fP) command instead.
.RE
.PP
-
.I ${TIN_LIBDIR:\-NEWSLIBDIR}/newsgroups
.sp
.RS
@@ -2845,7 +2818,6 @@ if you read news via NNTP,
uses the LIST NEWSGROUPS (\fBRFC\%3977\fP) command instead.
.RE
.PP
-
.I ${TIN_LIBDIR:\-NEWSLIBDIR}/organization
.sp
.RS
@@ -2854,7 +2826,6 @@ the ''Organization:'' header. $\fBORGANI
if set.
.RE
.PP
-
.I ${TIN_LIBDIR:\-NEWSLIBDIR}/overview.fmt
.\" is the Path correct? or is it /news/etc/overview.fmt
.sp
@@ -2872,7 +2843,6 @@ if you read news via NNTP,
uses the LIST OVERVIEW.FMT (\fBRFC\%3977\fP) command instead.
.RE
.PP
-
.I ${TIN_LIBDIR:\-NEWSLIBDIR}/subscriptions
.\" is the Path correct? or is it /news/etc/subscriptions
.sp
@@ -2887,7 +2857,7 @@ if you read news via NNTP,
uses the LIST SUBSCRIPTIONS (\fBRFC\%6048\fP) command instead.
.RE
-.SH "SEE ALSO"
+.SH SEE ALSO
.BR \%inews (1),
.BR \%ispell (1),
.BR \%lp (1),
Any program (person), that produces man pages, should check the output
for defects by using (both groff and nroff)
[gn]roff -mandoc -t -ww -b -z -K utf8 <man page>
The same goes for man pages that are used as an input.
For a style guide use
mandoc -T lint
-.-
Any "autogenerator" should check its products with the above mentioned
'groff', 'mandoc', and additionally with 'nroff ...'.
It should also check its input files for too long (> 80) lines.
This is just a simple quality control measure.
The "autogenerator" may have to be corrected to get a better man page,
the source file may, and any additional file may.
Common defects:
Not removing trailing spaces (in in- and output).
The reason for these trailing spaces should be found and eliminated.
"git" has a "tool" to point out whitespace,
see for example "git-apply(1)" and git-config(1)")
Not beginning each input sentence on a new line.
Line length and patch size should thus be reduced.
The script "reportbug" uses 'quoted-printable' encoding when a line is
longer than 1024 characters in an 'ascii' file.
See man-pages(7), item "semantic newline".
-.-
The difference between the formatted output of the original and patched file
can be seen with:
nroff -mandoc <file1> > <out1>
nroff -mandoc <file2> > <out2>
diff -d -u <out1> <out2>
and for groff, using
\"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -mandoc -Z - \"
instead of 'nroff -mandoc'
Add the option '-t', if the file contains a table.
Read the output from 'diff -d -u ...' with 'less -R' or similar.
-.-.
If 'man' (man-db) is used to check the manual for warnings,
the following must be set:
The option \"-warnings=w\"
The environmental variable:
export MAN_KEEP_STDERR=yes (or any non-empty value)
or
(produce only warnings):
export MANROFFOPT=\"-ww -b -z\"
export MAN_KEEP_STDERR=yes (or any non-empty value)
-.-
