Currently, the following input encodings are available.
This input encoding works only on EBCDIC platforms (and vice versa, the other input encodings don’t work with EBCDIC); the file cp1047.tmac is by default loaded at start-up.
This is the default input encoding on non-EBCDIC platforms; the file latin1.tmac is loaded at start-up.
To use this encoding, either say ‘.mso latin2.tmac’ at the very
beginning of your document or use ‘-mlatin2’ as a command-line
For Turkish. Either say ‘.mso latin5.tmac’ at the very
beginning of your document or use ‘-mlatin5’ as a command-line
This encoding is intended (at least in Europe) to replace latin-1
encoding. The main difference to latin-1 is that latin-9
contains the Euro character. To use this encoding, either say
‘.mso latin9.tmac’ at the very beginning of your document or
use ‘-mlatin9’ as a command-line argument for
Note that it can happen that some input encoding characters are not available for a particular output device. For example, saying
groff -Tlatin1 -mlatin9 ...
fails if you use the Euro character in the input. Usually, this limitation is present only for devices that have a limited set of output glyphs (e.g. -Tascii and -Tlatin1); for other devices it is usually sufficient to install proper fonts that contain the necessary glyphs.
Due to the importance of the Euro glyph in Europe, the groff package now comes with a POSTSCRIPT font called freeeuro.pfa, which provides various glyph shapes for the Euro. In other words, latin-9 encoding is supported for the -Tps device out of the box (latin-2 isn’t).
By its very nature, -Tutf8 supports all input encodings; -Tdvi has support for both latin-2 and latin-9 if the command-line -mec is used also to load the file ec.tmac (which flips to the EC fonts).