psfpages(1)

📦
version 1.1.3 · 2 versions
, in nixpkgs unstable, ubuntu stonking

💖 psfpages(1) 💖

okay bestie, welcome to psfpages — she's the little tool that tells you which codepages the PSF Tools even know about. Iconic behaviour. No cap.

✨ NAME ✨

psfpages — list codepages known to the PSF Tools 💅

🦋 SYNOPSIS 🦋

psfpages [codepages]

🌸 DESCRIPTION 🌸

So here's the deal, gorgeous:

If you run it with no arguments at all, psfpages just lists the codepages supported by the psftools utilities. Like a little roll call. A vibe check of codepages, if you will. ✨

If you hand it one or more codepage names, then psfpages dumps the contents of the mapping tables for the codepages you named. It's giving receipts. Fr fr.

Right now there are three sorts of codepage compiled into the psftools:

  • ISO 8859 codepages — you refer to these by their encoding name, e.g. "8859-1". 💖
  • Numbered codepages — you refer to these by their number, e.g. "CP437" or just "437". Both slay equally.
  • Nonstandard codepages — the special ones, the main characters. 👑

Currently the nonstandard codepages are:

  • AMSTRAD — the codepage used by CP/M on the Amstrad PCW, CPC and Spectrum +3. 🎀
  • BBCMICRO — the codepage used by the BBC Micro (heads up: it covers characters 32-127 only). 🌈
  • PCGEM — the codepage used by GEM on the IBM PC.
  • PPC437, PPC860, PPC865, PPCGREEK — the codepages used by the character ROM on Amstrad PPC laptops and their desktop counterpart, the Sinclair PC200. These differ slightly from the standard codepages 437, 860 and 865, because they're trying to avoid confusion between the 'epsilon' and 'element-of' characters. Very thoughtful of them honestly. 🧚
⚠️ okay so real talk: the next paragraph in this manpage literally starts mid-sentence (the beginning got lost somewhere, RIP). But here it is exactly as she wrote it, because we do not lose details in this house: from Unicode.org, and partly from the *.uni files supplied with the Linux kbd-1.12 utilities. In most cases they have been modified to replace the control code entries with the glyphs that are actually observed in the fonts. For example, compare unicode.org's CP437.TXT with the output of psfpages for codepage 437.

😭 BUGS 😭

Bestie. It's not all perfect. Sit down, take a breath. 🫶

  • The AMSTRAD character 7Fh (zero without a slash) has been mapped to U+FF10 FULLWIDTH DIGIT ZERO, rather than to U+0030 DIGIT ZERO. This is not ideal, but it avoids the information loss of mapping two different character shapes to the same codepoint. A sacrifice was made. 🙈
  • The PCGEM character 0Ah (bell) has been mapped to U+237E BELL SYMBOL, but it's not the same sort of bell at all — the GEM character is a dingbat, but the Unicode bell is a symbol for a circuit diagram. Two totally different bells. 💀
  • Six characters in the PCGEM character set (0DAh to 0DFh) appear not to be used, and display as blank in all known PCGEM fonts. Their mapping entries reflect this status: they will be ignored when a Unicode directory is being created, and set to blank when a PSF is written with this codepage. They're just out here being nothing. Respect.

👑 AUTHOR 👑

John Elliott <seasip.webmaster@gmail.com>.

and that's the whole page, bestie!! 🎀✨ one last thing before you go: this is Version 1.1.3, dated 28 April, 2026, and yeah — she's psfpages(1). mwah 💋

📦 where this page comes from