Package: unicode
Version: 2.7-1
Severity: minor
Tags: patch

Dear Maintainer,

  Summary:

Remove space at end of lines.

Fix warnings from test-groff.

Change a two-fonts macro to an one-font macro for a
single argument.

Split a single argument into two for a two-font macro.

Change a HYPHEN-MINUS (code 0x55, 2D) to a dash
(minus, '\-')
if it matches " -[:alpha:]" or \[aq]-[:alpha:] (for options).

####

Input file is unicode.1

Output from "mandoc  -T lint unicode.1":

mandoc: unicode.1:7:17: STYLE: whitespace at end of input line
mandoc: unicode.1:18:9: STYLE: whitespace at end of input line
mandoc: unicode.1:19:14: STYLE: whitespace at end of input line
mandoc: unicode.1:27:7: STYLE: whitespace at end of input line
mandoc: unicode.1:29:27: STYLE: whitespace at end of input line
mandoc: unicode.1:35:7: STYLE: whitespace at end of input line
mandoc: unicode.1:37:23: STYLE: whitespace at end of input line
mandoc: unicode.1:43:7: STYLE: whitespace at end of input line
mandoc: unicode.1:45:22: STYLE: whitespace at end of input line
mandoc: unicode.1:51:7: STYLE: whitespace at end of input line
mandoc: unicode.1:53:22: STYLE: whitespace at end of input line
mandoc: unicode.1:59:7: STYLE: whitespace at end of input line
mandoc: unicode.1:67:7: STYLE: whitespace at end of input line
mandoc: unicode.1:124:20: STYLE: whitespace at end of input line
mandoc: unicode.1:167:69: STYLE: whitespace at end of input line
mandoc: unicode.1:194:46: STYLE: whitespace at end of input line
mandoc: unicode.1:200:21: STYLE: whitespace at end of input line

#######


Test nr. 2:

Enable and fix warnings from 'test-groff'.


[ "test-groff" is a developmental version of "groff" ]

Input file is ./unicode.1

Output from test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -rIN=4m -t -w w -z :

<unicode.1>:18 (macro BI): only 1 argument, but more are expected
<unicode.1>:19 (macro BI): only 1 argument, but more are expected
<unicode.1>:24 (macro BI): only 1 argument, but more are expected
<unicode.1>:25 (macro BI): only 1 argument, but more are expected
<unicode.1>:32 (macro BI): only 1 argument, but more are expected
<unicode.1>:33 (macro BI): only 1 argument, but more are expected
<unicode.1>:40 (macro BI): only 1 argument, but more are expected
<unicode.1>:41 (macro BI): only 1 argument, but more are expected
<unicode.1>:48 (macro BI): only 1 argument, but more are expected
<unicode.1>:49 (macro BI): only 1 argument, but more are expected
<unicode.1>:56 (macro BI): only 1 argument, but more are expected
<unicode.1>:57 (macro BI): only 1 argument, but more are expected
<unicode.1>:72 (macro BI): only 1 argument, but more are expected
<unicode.1>:73 (macro BI): only 1 argument, but more are expected
<unicode.1>:80 (macro BI): only 1 argument, but more are expected
<unicode.1>:81 (macro BI): only 1 argument, but more are expected
<unicode.1>:86 (macro BI): only 1 argument, but more are expected
<unicode.1>:87 (macro BI): only 1 argument, but more are expected
<unicode.1>:95 (macro BI): only 1 argument, but more are expected
<unicode.1>:96 (macro BI): only 1 argument, but more are expected
<unicode.1>:104 (macro BI): only 1 argument, but more are expected
<unicode.1>:105 (macro BI): only 1 argument, but more are expected
<unicode.1>:110 (macro BI): only 1 argument, but more are expected
<unicode.1>:111 (macro BI): only 1 argument, but more are expected
<unicode.1>:127 (macro BI): only 1 argument, but more are expected
<unicode.1>:129 (macro BI): only 1 argument, but more are expected
<unicode.1>:132 (macro BI): only 1 argument, but more are expected
<unicode.1>:133 (macro BI): only 1 argument, but more are expected
<unicode.1>:138 (macro BI): only 1 argument, but more are expected
<unicode.1>:139 (macro BI): only 1 argument, but more are expected
<unicode.1>:144 (macro BI): only 1 argument, but more are expected
<unicode.1>:145 (macro BI): only 1 argument, but more are expected
<unicode.1>:150 (macro BI): only 1 argument, but more are expected
<unicode.1>:155 (macro BI): only 1 argument, but more are expected
<unicode.1>:161 (macro BI): only 1 argument, but more are expected

#####

Test nr. 13:

Change -- in x--y to \(em (em-dash), or, if an
option, to \-\-

204:Use --fromcp to query codepoints from other encodings:
206:\fBunicode\fP --fromcp cp1250 -d 200
209:\fBunicode\fP --fromcp big5 -x aff3
213:\fBunicode\fP --fromcp utf-8 -x c599c3adc5a5

#####

Test nr. 25:

Change a HYPHEN-MINUS (code 0x55, 2D) to a minus (\-), if in front of a
name for an option.

177:\fBunicode\fP -r face

#####

Patch:

--- unicode.1   2020-10-11 02:22:43.000000000 +0000
+++ unicode.1.new       2020-10-11 02:40:33.000000000 +0000
@@ -4,7 +4,7 @@
 unicode \- command line unicode database query tool
 .SH SYNOPSIS
 .B unicode
-.RI [ options ] 
+.RI [ options ]
 string
 .SH DESCRIPTION
 This manual page documents the
@@ -15,76 +15,76 @@ command.
 
 .SH OPTIONS
 .TP
-.BI \-h 
-.BI \-\-help 
+.B \-h
+.B \-\-help
 
 Show help and exit.
 
 .TP
-.BI \-x
-.BI \-\-hexadecimal
+.B \-x
+.B \-\-hexadecimal
 
-Assume 
+Assume
 .I string
-to be a hexadecimal number 
+to be a hexadecimal number
 
 .TP
-.BI \-d
-.BI \-\-decimal
+.B \-d
+.B \-\-decimal
 
-Assume 
+Assume
 .I string
-to be a decimal number 
+to be a decimal number
 
 .TP
-.BI \-o
-.BI \-\-octal
+.B \-o
+.B \-\-octal
 
-Assume 
+Assume
 .I string
-to be an octal number 
+to be an octal number
 
 .TP
-.BI \-b
-.BI \-\-binary
+.B \-b
+.B \-\-binary
 
-Assume 
+Assume
 .I string
-to be a binary number 
+to be a binary number
 
 .TP
-.BI \-r
-.BI \-\-regexp
+.B \-r
+.B \-\-regexp
 
-Assume 
+Assume
 .I string
 to be a regular expression
 
 .TP
-.BI \-s
-.BI \-\-string
+.B \-s
+.B \-\-string
 
-Assume 
+Assume
 .I string
 to be a sequence of characters
 
 .TP
-.BI \-a
-.BI \-\-auto
+.B \-a
+.B \-\-auto
 
 Try to guess type of
 .I string
 from one of the above (default)
 
 .TP
-.BI \-mMAXCOUNT
-.BI \-\-max=MAXCOUNT
+.BI \-m MAXCOUNT
+.BI \-\-max= MAXCOUNT
 
 Maximal number of codepoints to display, default: 20; use 0 for unlimited
 
 .TP
-.BI \-iCHARSET
-.BI \-\-io=IOCHARSET
+.BI \-i CHARSET
+.BI \-\-io= IOCHARSET
 
 I/O character set. For maximal pleasure, run \fBunicode\fP on UTF-8
 capable terminal and specify IOCHARSET to be UTF-8. \fBunicode\fP
@@ -92,8 +92,8 @@ tries to guess this value from your loca
 locale, you should not need to specify it.
 
 .TP
-.BI \-\-fcp=CHARSET
-.BI \-\-fromcp=CHARSET
+.BI \-\-fcp= CHARSET
+.BI \-\-fromcp= CHARSET
 
 Convert numerical arguments from this encoding, default: no conversion.
 Multibyte encodings are supported. This is ignored for non-numerical
@@ -101,19 +101,19 @@ arguments.
 
 
 .TP
-.BI \-cADDCHARSET
-.BI \-\-charset\-add=ADDCHARSET
+.BI \-c ADDCHARSET
+.BI \-\-charset\-add= ADDCHARSET
 
 Show hexadecimal reprezentation of displayed characters in this additional 
charset.
 
 .TP
-.BI \-CUSE_COLOUR
-.BI \-\-colour=USE_COLOUR
+.BI \-C USE_COLOUR
+.BI \-\-colour= USE_COLOUR
 
 USE_COLOUR is one of
-.I on
-.I off
-.I auto
+.B on
+.B off
+.B auto
 
 .B \-\-colour=on
 will use ANSI colour codes to colourise the output
@@ -121,50 +121,50 @@ will use ANSI colour codes to colourise
 .B \-\-colour=off
 won't use colours.
 
-.B \-\-colour=auto 
+.B \-\-colour=auto
 will test if standard output is a tty, and use colours only when it is.
 
-.BI \-\-color
+.B \-\-color
 is a synonym of
-.BI \-\-colour
+.B \-\-colour
 
 .TP
-.BI \-v
-.BI \-\-verbose
+.B \-v
+.B \-\-verbose
 
 Be more verbose about displayed characters, e.g. display Unihan information, 
if available.
 
 .TP
-.BI \-w
-.BI \-\-wikipedia
+.B \-w
+.B \-\-wikipedia
 
 Spawn browser pointing to English Wikipedia entry about the character.
 
 .TP
-.BI \-\-wt
-.BI \-\-wiktionary
+.B \-\-wt
+.B \-\-wiktionary
 
 Spawn browser pointing to English Wiktionary entry about the character.
 
 .TP
-.BI \-\-brief
+.B \-\-brief
 
 Display character information in brief format
 
 .TP
-.BI \-\-format=fmt
+.BI \-\-format= fmt
 
 Use your own format for character information display. See the README for 
details.
 
 
 .TP
-.BI \-\-list
+.B \-\-list
 
 List (approximately) all known encodings.
 
 .SH USAGE
 
-\fBunicode\fP tries to guess the type of an argument. In particular, 
+\fBunicode\fP tries to guess the type of an argument. In particular,
 if the arguments looks like a valid hexadecimal representation of a
 Unicode codepoint, it will be considered to be such. Using
 
@@ -174,7 +174,7 @@ will display information about U+FACE CJ
 and it will not search for 'face' in character descriptions \- for the latter,
 use:
 
-\fBunicode\fP -r face
+\fBunicode\fP \-r face
 
 
 For example, you can use any of the following to display information
@@ -191,26 +191,26 @@ about  U+00E1 LATIN SMALL LETTER A WITH
 
 You can specify a range of characters as argumets, \fBunicode\fP will
 show these characters in nice tabular format, aligned to 256-byte boundaries.
-Use two dots ".." to indicate the range, e.g. 
+Use two dots ".." to indicate the range, e.g.
 
 \fBunicode\fP 0450..0520
 
 will display the whole cyrillic and hebrew blocks (characters from U+0400 to 
U+05FF)
 
-\fBunicode\fP 0400.. 
+\fBunicode\fP 0400..
 
 will display just characters from U+0400 up to U+04FF
 
-Use --fromcp to query codepoints from other encodings:
+Use \-\-fromcp to query codepoints from other encodings:
 
-\fBunicode\fP --fromcp cp1250 -d 200
+\fBunicode\fP \-\-fromcp cp1250 \-d 200
 
 Multibyte encodings are supported:
-\fBunicode\fP --fromcp big5 -x aff3
+\fBunicode\fP \-\-fromcp big5 \-x aff3
 
 and multi-char strings are supported, too:
 
-\fBunicode\fP --fromcp utf-8 -x c599c3adc5a5
+\fBunicode\fP \-\-fromcp utf-8 \-x c599c3adc5a5
 
 .SH BUGS
 Tabular format does not deal well with full-width, combining, control


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.10-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages unicode depends on:
ii  python3  3.8.2-3

Versions of packages unicode recommends:
ii  unicode-data  13.0.0-2

unicode suggests no packages.

-- no debconf information

-- 
Bjarni I. Gislason

Reply via email to