jfbterm(5)
jfbterm.conf – configuration file for
jfbterm(1)
Description
This manual page documents briefly the jfbterm.conf configuration file that is used in jfbterm(1) command.
Configurations
The format of an entry for this file is:
-
entryName : value
If `+’ is at beginning of the line, value is added to
entryName as an array. This means that one entryName can have multiple values.
A summary of configrations is included below.
termTERM environment variable’s value for a program that runs injfbterm(1). The default isjfbterm.fontsetThis assigns a font for each character set. A term "character set" means a set of characters and is an element for "encodings". In other words, an encoding consists from one or more character sets. In jfbterm, most of character sets are assumed to have ISO-2022-compliant structure, i.e., a character set contains 94 characters, 96 characters, 94^N characters, or 96^N characters.iso10646.1is the only exception.- The format of
fontsetvalue is: - type specifies "pcf" or "alias". If type is "pcf", fontname is a pathname of a font file. If type is "alias", fontname specifies another charsetName, which means that the character set of charsetName will use the same font to the character set of fontname.
- side specifies in which side (GL or GR) the font has glyphs for the character set, in terms of ISO-2022.
Lmeans GL (0x20-0x7f) andRmeans GR (0xa0-0xff). A unique specification,U, is used only for iso10646.1. - For example,
iso8859.1-1987is a character set which contains 96 characters. The glyphs for iso8859.1-1987 characters are available in GR side of *-iso8859-1 fonts. encodingThis defines an encoding. An encoding is what you really use to express texts and consists from one or more character sets. In jfbterm, most of encodings are defined as ISO-2022’s initial state and jfbterm can change character sets by using ISO-2022 escape sequences. However, non-ISO-2022-compliant encodings such as Big5 and KOI8-R are also supported viaiconv(3).- The format of
encodingvalue is - If no `,’ is found in
encodingvalue, it is recognized as encodingName (the second case). If the encodingName matches one ofencoding.encodingName which is explained below, this definition is used. Otherwise, if the encodingName matches one of valid encoding names foriconv(1) oriconv_open(3),jfbtermwill work in UTF-8 mode internally. This means that the font defined byfontset:iso10646.1line will be used andiconv(3) will be used to emulate the given encodingName. This behavior is just as if there is a line: - If a `,’ is found in
encodingvalue, it is recognized as the third case. This format defines an encoding as an ISO-2022 initial state. GL and GR specifies a slot (one ofG0,G1,G2, orG3) which is invoked into GL (0x20-0x7F) and GR (0xA0-0xFF). G0, G1, G2, and G3 specifies the character set which is designated into the corresponding slot. - The default is "locale".
encoding.encodingName This defines an encoding of encodingName as an ISO-2022 initial state, like the third case ofencodingitem which is explained already. The format is like following:- The second case means that the encoding is UTF-8. This is a special case.
- The third case defines an encoding as a conversion of an other encoding.
jfbtermwill use the encoding of internal-encodingName internally and will useiconv(3) for conversion. - Note that, in the third case, internal-encodingName must be a valid encoding name which is defined in other
encoding.encodingName line (which has the first or second format). Both of internal-encodingName and encodingName must be valid encoding names foriconv(1) oriconv_open(3). Also, Both encodingNames (one is a part ofencoding.encodingName and the another appears next to "other,") must be same. color.gammaColor gamma value. The default is 1.7.
charsetName,type,side,fontname
You can see a list of available charsetNames by running "jfbterm –help".
locale or encodingName or GL,GR,G0,G1,G2,G3
If encoding value is "locale" (the first case), then encodingName value is initialized by the current LC_CTYPE locale ("locale -k charmap") and falling into the second case.
encoding.encodingName : other,encodingName,iconv,UTF-8
This mechanism enables jfbterm to support various encodings which are not ISO-2022-compliant.
GL,GR,G0,G1,G2,G3 or UTF-8,iso10646.1 or other,encodingName,iconv,internal-encodingName
The first case is just same as explained in the third case of encoding item.
Files
- /etc/jfbterm.conf
- Configuration file for
jfbterm(1).
See Also
jfbterm(1), locale(1), iconv(3).
Author
This manual page was written by Fumitoshi UKAI <ukai [at] debian.or.jp>.