|
NAMEpsfpages - list codepages known to the PSF ToolsSYNOPSISpsfpages [codepages]DESCRIPTIONIf run with no arguments, psfpages lists the codepages supported by the psftools utilities.If one or more codepage names is supplied, psfpages dumps the contents of the mapping tables for the named codepages. There are currently three sorts of codepage compiled into the psftools: ISO 8859 codepages, referred to by encoding name (eg "8859-1"); numbered codepages, referred to by their number (eg "CP437" or just "437") and nonstandard codepages. Currently the nonstandard codepages are:
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. BUGSThe 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.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. 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. AUTHORJohn Elliott <seasip.webmaster@gmail.com>.
Visit the GSP FreeBSD Man Page Interface. |