1JFBTERM.CONF(5) File Formats Manual JFBTERM.CONF(5)
2
6 jfbterm.conf - configuration file for jfbterm(1)
7
9 This manual page documents briefly the jfbterm.conf configuration file
10 that is used in jfbterm(1) command.
11
13 The format of an entry for this file is:
14 entryName : value
16 If `+' is at beginning of the line, value is added to entryName as an
18 array. This means that one entryName can have multiple values.
19 A summary of configrations is included below.
21 term TERM environment variable's value for a program that runs in
23 jfbterm(1). The default is jfbterm.
24 fontset
26 This assigns a font for each character set. A term "character
27 set" means a set of characters and is an element for "encod‐
28 ings". In other words, an encoding consists from one or more
29 character sets. In jfbterm, most of character sets are assumed
30 to have ISO-2022-compliant structure, i.e., a character set con‐
31 tains 94 characters, 96 characters, 94^N characters, or 96^N
32 characters. iso10646.1 is the only exception.
33 The format of fontset value is:
35 charsetName,type,side,fontname
37 You can see a list of available charsetNames by running "jfbterm
39 --help".
40 type specifies "pcf" or "alias". If type is "pcf", fontname is
42 a pathname of a font file. If type is "alias", fontname speci‐
43 fies another charsetName, which means that the character set of
44 charsetName will use the same font to the character set of font‐
45 name.
46 side specifies in which side (GL or GR) the font has glyphs for
48 the character set, in terms of ISO-2022. L means GL (0x20-0x7f)
49 and R means GR (0xa0-0xff). A unique specification, U, is used
50 only for iso10646.1.
51 For example, iso8859.1-1987 is a character set which contains 96
53 characters. The glyphs for iso8859.1-1987 characters are avail‐
54 able in GR side of *-iso8859-1 fonts.
55 encoding
57 This defines an encoding. An encoding is what you really use to
58 express texts and consists from one or more character sets. In
59 jfbterm, most of encodings are defined as ISO-2022's initial
60 state and jfbterm can change character sets by using ISO-2022
61 escape sequences. However, non-ISO-2022-compliant encodings
62 such as Big5 and KOI8-R are also supported via iconv(3).
63 The format of encoding value is
65 locale
67 or
68 encodingName
69 or
70 GL,GR,G0,G1,G2,G3
71 If encoding value is "locale" (the first case), then encoding‐
73 Name value is initialized by the current LC_CTYPE locale
74 ("locale -k charmap") and falling into the second case.
75 If no `,' is found in encoding value, it is recognized as encod‐
77 ingName (the second case). If the encodingName matches one of
78 encoding.encodingName which is explained below, this definition
79 is used. Otherwise, if the encodingName matches one of valid
80 encoding names for iconv(1) or iconv_open(3), jfbterm will work
81 in UTF-8 mode internally. This means that the font defined by
82 fontset:iso10646.1 line will be used and iconv(3) will be used
83 to emulate the given encodingName. This behavior is just as if
84 there is a line:
85 encoding.encodingName : other,encodingName,iconv,UTF-8
87 This mechanism enables jfbterm to support various encodings
89 which are not ISO-2022-compliant.
90 If a `,' is found in encoding value, it is recognized as the
92 third case. This format defines an encoding as an ISO-2022 ini‐
93 tial state. GL and GR specifies a slot (one of G0, G1, G2, or
94 G3) which is invoked into GL (0x20-0x7F) and GR (0xA0-0xFF).
95 G0, G1, G2, and G3 specifies the character set which is desig‐
96 nated into the corresponding slot.
97 The default is "locale".
99 encoding.encodingName
101 This defines an encoding of encodingName as an ISO-2022 initial
102 state, like the third case of encoding item which is explained
103 already. The format is like following:
104 GL,GR,G0,G1,G2,G3
106 or
107 UTF-8,iso10646.1
108 or
109 other,encodingName,iconv,internal-encodingName
110 The first case is just same as explained in the third case of
112 encoding item.
113 The second case means that the encoding is UTF-8. This is a
115 special case.
116 The third case defines an encoding as a conversion of an other
118 encoding. jfbterm will use the encoding of internal-encoding‐
119 Name internally and will use iconv(3) for conversion.
120 Note that, in the third case, internal-encodingName must be a
122 valid encoding name which is defined in other encoding.encoding‐
123 Name line (which has the first or second format). Both of
124 internal-encodingName and encodingName must be valid encoding
125 names for iconv(1) or iconv_open(3). Also, Both encodingNames
126 (one is a part of encoding.encodingName and the another appears
127 next to "other,") must be same.
128 color.gamma
130 Color gamma value. The default is 1.7.
131
133 /etc/jfbterm.conf
134 Configuration file for jfbterm(1).
135
137 jfbterm(1), locale(1), iconv(3).
138
140 This manual page was written by Fumitoshi UKAI <ukai@debian.or.jp>.
141 Aug 30, 2003 JFBTERM.CONF(5)