Package: console-tools
Version: 1:0.2.3dbs-65.1
Severity: normal
The manual claims different usage than the output from
"psfgettable -h":
----From the command----
Usage: psfgettable psffont chartable [outfile]
...
valid options are:
-f --font=f psffont filename
-o --outfile=f output filename
-h --help display this help text and exit
-V --version display version information and exit
----End of output from command----
----From the manual----
psfgettable fontfile [outfile]
If the font file name is a single dash (-), the font is read from
standard input.
---End from the manual-----
The word "chartable" is not explained.
Testing shows (e.g. "gunzip -c \
/usr/share/consolefonts/iso01.f16.psf.gz > file")
1) command line from manual works
2) options -f and -o work
3) if the command reads from standard input according to the
manual, an error is issued:
stdin: Illegal seek
NOTE: The word "illegal" should not be used in error messages
in computer codes. Instead the word "invalid" is appropriate.
See "GNU Coding Standards" in "www.gnu.org/prep/standards/".
"Chapter 6.1 GNU Manuals", second last paragraph. Version from
7th June 2009.
-- System Information:
Debian Release: 5.0.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i586)
Kernel: Linux 2.6.26c
Locale: LANG=is_IS, LC_CTYPE=is_IS (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages console-tools depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libconsole 1:0.2.3dbs-65.1 Shared libraries for Linux console
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
Versions of packages console-tools recommends:
ii console-common 0.7.80 basic infrastructure for text cons
ii console-data 2:1.07-11 keymaps, fonts, charset maps, fall
Versions of packages console-tools suggests:
ii kbd-compat 1:0.2.3dbs-65.1 Wrappers around console-tools for
-- no debconf information
--
B. Gislason
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
