1psfpages(1)                        PSF Tools                       psfpages(1)
2
3
4

NAME

6       psfpages - list codepages known to the PSF Tools
7

SYNOPSIS

9       psfpages [codepages]

DESCRIPTION

11       If run with no arguments, psfpages lists the codepages supported by the
12       psftools utilities.
13
14       If one or more codepage names is supplied, psfpages dumps the  contents
15       of the mapping tables for the named codepages.
16
17       There are currently three sorts of codepage compiled into the psftools:
18       ISO 8859 codepages, referred to by encoding name  (eg  "8859-1");  num‐
19       bered codepages, referred to by their number (eg "CP437" or just "437")
20       and nonstandard codepages. Currently the nonstandard codepages are:
21
22       AMSTRAD
23              The codepage used by CP/M on the Amstrad PCW, CPC  and  Spectrum
24              +3.
25
26       BBCMICRO
27              The  codepage  used  by  the BBC Micro (covers characters 32-127
28              only).
29
30       PCGEM  The codepage used by GEM on the IBM PC.
31
32       PPC437, PPC860, PPC865, PPCGREEK
33              The codepages used by the character ROM on Amstrad  PPC  laptops
34              and  their desktop counterpart, the Sinclair PC200. These differ
35              slightly from the standard codepages 437, 860 and 865  to  avoid
36              confusion between the 'epsilon' and 'element-of' characters.
37
38       from  Unicode.org,  and  partly  from the *.uni files supplied with the
39       Linux kbd-1.12 utilities. In most cases  they  have  been  modified  to
40       replace  the  control  code  entries  with the glyphs that are actually
41       observed in the fonts. For  example,  compare  unicode.org's  CP437.TXT
42       with the output of psfpages for codepage 437.
43

BUGS

45       The  AMSTRAD  character  7Fh  (zero without a slash) has been mapped to
46       U+FF10 FULLWIDTH DIGIT ZERO, rather than to U+0030 DIGIT ZERO. This  is
47       not  ideal, but it avoids the information loss of mapping two different
48       character shapes to the same codepoint.
49
50       The PCGEM character 0Ah (bell) has been mapped to U+237E  BELL  SYMBOL,
51       but it's not the same sort of bell at all; the GEM character is a ding‐
52       bat, but the Unicode bell is a symbol for a circuit diagram.
53
54       Six characters in the PCGEM character set (0DAh to 0DFh) appear not  to
55       be  used,  and display as blank in all known PCGEM fonts. Their mapping
56       entries reflect this status; they will be ignored when a Unicode direc‐
57       tory is being created, and set to blank when a PSF is written with this
58       codepage.
59

AUTHOR

61       John Elliott <jce@seasip.demon.co.uk>.
62
63Version 1.0.8                    21 June, 2008                     psfpages(1)
Impressum