JFBTERM.CONF(5)

🌸 NAME 🌸

okay so bestie, welcome to the JFBTERM.CONF(5) page — it's a File Formats Manual situation, and it's all about jfbterm.conf, the configuration file for jfbterm(1). 💖 That's literally the whole NAME section, no gatekeeping here.

---

✨ DESCRIPTION ✨

This manual page documents briefly the jfbterm.conf configuration file that gets used by the jfbterm(1) command. That's it, that's the description, short and sweet like a good text-back. 🎀

---

🦋 CONFIGURATIONS 🦋

The format of an entry for this file is:

entryName : value

If + is at the beginning of the line, the value is added to entryName as an array. Which means one entryName can have multiple values — it's giving polyamorous config entries, and honestly? iconic. 👑

A summary of configurations is included below.

• term — the value of the TERM environment variable for a program that runs in jfbterm(1). The default is jfbterm. 🌈
• fontset — this assigns a font for each character set. A term "character set" means a set of characters, and it's an element for "encodings". In other words, an encoding consists of one or more character sets. In jfbterm, most of the 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.1 is the only exception. 🙈

The format of the fontset value is:

charsetName,type,side,fontname

You can see a list of available *charsetName*s by running jfbterm --help. 👀

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 as 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. L means GL (0x20-0x7f) and R means GR (0xa0-0xff). A unique specification, U, is used only for iso10646.1. ⭐

For example, iso8859.1-1987 is a character set which contains 96 characters. The glyphs for iso8859.1-1987 characters are available in the GR side of *-iso8859-1 fonts. 🧚

• encoding — this defines an encoding. An encoding is what you really use to express texts, and it consists of one or more character sets. In jfbterm, most of the 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 via iconv(3). no cap. 🔥

The format of encoding value is

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. 🫶

If no , is found in encoding value, it is recognized as encodingName (the second case). If the encodingName matches one of encoding.encodingName which is explained below, this definition is used. Otherwise, if the encodingName matches one of valid encoding names for iconv(1) or iconv_open(3), jfbterm will work in UTF-8 mode internally. This means that the font defined by the fontset:iso10646.1 line will be used and iconv(3) will be used to emulate the given encodingName. This behavior is just as if there is a line:

encoding.encodingName : other,encodingName,iconv,UTF-8

This mechanism enables jfbterm to support various encodings which are not ISO-2022-compliant. it's giving adaptability, it's giving range. 🌸

If a , is found in encoding value, it is recognized as the third case. This format defines an encoding as an ISO-2022 initial state. GL and GR specify a slot (one of G0, G1, G2, or G3) which is invoked into GL (0x20-0x7F) and GR (0xA0-0xFF). G0, G1, G2, and G3 specify 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 of the encoding item which is explained already. The format is like following:

GL,GR,G0,G1,G2,G3

or

UTF-8,iso10646.1

or

other,encodingName,iconv,internal-encodingName

The first case is just the same as explained in the third case of the encoding item. 🎀

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 another encoding. jfbterm will use the encoding of internal-encodingName internally and will use iconv(3) for conversion. 🦋

Note that, in the third case, internal-encodingName must be a valid encoding name which is defined in another encoding.encodingName line (which has the first or second format). Both of internal-encodingName and encodingName must be valid encoding names for iconv(1) or iconv_open(3). Also, both *encodingName*s (one is a part of encoding.encodingName and the other appears next to other,) must be the same. 💀 yeah it's strict, it's highkey a whole vibe check for your config, do not play with it.

• color.gamma — Color gamma value. The default is 1.7. 🌈

---

🎀 FILES 🎀

• /etc/jfbterm.conf — Configuration file for jfbterm(1). the main character, the moment, the one file to rule them all. 👑

---

💖 SEE ALSO 💖

jfbterm(1), locale(1), iconv(3). go read those too bestie, iykyk. 🫶

---

🌟 AUTHOR 🌟

This manual page was written by Fumitoshi UKAI <ukai@debian.or.jp>. thank you king, we are obsessed. 💅

---

and that's the whole page fr fr — this version of the JFBTERM.CONF(5) page comes from the File Formats Manual, dated Aug 30, 2003, and we're signing off, periodt. 🦋✨💜