{"id":4126,"date":"2022-12-20T17:39:28","date_gmt":"2022-12-20T20:39:28","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/groff_char-man7\/"},"modified":"2022-12-20T17:39:28","modified_gmt":"2022-12-20T20:39:28","slug":"groff_char-man7","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/groff_char-man7\/","title":{"rendered":"GROFF_CHAR (man7)"},"content":{"rendered":"

GROFF_CHAR<\/h1>\n

NAME<\/a>
DESCRIPTION<\/a>
REFERENCE<\/a>
AUTHORS<\/a>
SEE ALSO<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

groff_char \u2212 groff glyph names<\/p>\n

DESCRIPTION <\/a> <\/h2>\n

This manual page lists the standard groff<\/b> glyph names and the default input mapping, latin1. The glyphs in this document look different depending on which output device was chosen (with option \u2212T<\/b> for the man<\/b>(1) program or the roff formatter). Glyphs not available for the device that is being used to print or view this manual page are marked with \u2018(N\/A)\u2019; the device currently used is \u2018html\u2019.<\/p>\n

In the actual version, groff<\/b> provides only 8-bit characters for direct input and named entities for further glyphs. On ASCII platforms, input character codes in the range 0 to 127 (decimal) represent the usual 7-bit ASCII characters, while codes between 127 and 255 are interpreted as the corresponding characters in the latin1<\/i> (ISO-8859-1<\/i>) code set by default. This mapping is contained in the file latin1.tmac and can be changed by loading a different input encoding. Note that some of the input characters are reserved by groff<\/b>, either for internal use or for special input purposes. On EBCDIC platforms, only code page cp1047<\/i> is supported (which contains the same characters as latin1; the input encoding file is called cp1047.tmac). Again, some input characters are reserved for internal and special purposes.<\/p>\n

All roff systems provide the concept of named glyphs. In traditional roff systems, only names of length\u00a02 were used, while groff also provides support for longer names. It is strongly suggested that only named glyphs are used for all character representations outside of the printable 7-bit ASCII range.<\/p>\n

Some of the predefined groff escape sequences (with names of length\u00a01) also produce single glyphs; these exist for historical reasons or are printable versions of syntactical characters. They include \u2018\\\u2019, \u2018’\u2019, \u2018`\u2019, \u2018\u2212\u2019, \u2018.\u2019, and \u2018e\u2019; see groff<\/b>(7).<\/p>\n

In groff, all of these different types of characters and glyphs can be tested positively with the \u2018.if\u00a0c\u2019 conditional.<\/p>\n

REFERENCE <\/a> <\/h2>\n

In this section, the glyphs in groff are specified in tabular form. The meaning of the columns is as follows.<\/p>\n\n\n\n\n
<\/td>\n\n

Output<\/i><\/p>\n<\/td>\n

<\/td>\n\n

shows how the glyph is printed for the current device; although this can have quite a different shape on other devices, it always represents the same glyph.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

Input<\/i><\/p>\n<\/td>\n

<\/td>\n\n

specifies how the glyph is input either directly by a key on the keyboard, or by a groff escape sequence.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

Code<\/i><\/p>\n<\/td>\n

<\/td>\n\n

applies to glyphs which can be input with a single character, and gives the ISO latin1 decimal code of that input character. Note that this code is equivalent to the lowest 256 Unicode characters, including 7-bit ASCII in the range 0 to\u00a0127.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

PostScript<\/i><\/p>\n

gives the usual PostScript name of the glyph.<\/p>\n

Unicode<\/i><\/p>\n

is the glyph name used in composite glyph names. The names in the Unicode column look like u0021<\/b> or u0041_0300<\/b>. In groff, the corresponding Unicode characters can be constructed by adding a backslash and a pair of square brackets, for example [u0021]<\/b> or [u0041_0300]<\/b>.<\/p>\n

7-bit Character Codes 32\u2013126<\/b>
These are the basic glyphs having 7-bit ASCII code values assigned. They are identical to the printable characters of the character standards ISO-8859-1 (latin1) and Unicode (range Basic Latin<\/i>). The glyph names used in composite glyph names are \u2018u0020\u2019 up to \u2018u007E\u2019.<\/p>\n

Note that input characters in the range 0\u221231 and character 127 are not<\/i> printable characters. Most of them are invalid input characters for groff<\/b> anyway, and the valid ones have special meaning. For EBCDIC, the printable characters are in the range 66\u2212255.<\/p>\n\n\n\n\n
<\/td>\n\n

48\u221257<\/p>\n<\/td>\n

<\/td>\n\n

Decimal digits 0 to\u00a09 (print as themselves).<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

65\u221290<\/p>\n<\/td>\n

<\/td>\n\n

Upper case letters A\u2212Z (print as themselves).<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

97\u2212122<\/p>\n<\/td>\n

<\/td>\n\n

Lower case letters a\u2013z (print as themselves).<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

Most of the remaining characters not in the just described ranges print as themselves; the only exceptions are the following characters:<\/p>\n\n\n\n\n\n\n
<\/td>\n\n

`<\/b><\/p>\n<\/td>\n

<\/td>\n\n

the ISO latin1 \u2018Grave Accent\u2019 (code\u00a096) prints as \u2018, a left single quotation mark (Unicode u2018). The same output glyph can be requested explicitly with \u2018(oq\u2019. The original character can be obtained with \u2018\u2018\u2019 (Unicode u0060).<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

‘<\/b><\/p>\n<\/td>\n

<\/td>\n\n

the ISO latin1 \u2018Apostrophe\u2019 (code\u00a039) prints as \u2019, a right single quotation mark (Unicode u2019). The same output glyph is commonly used in typography to represent a punctation apostrophe, for example in contractions. It can be requested explicitly with \u2018(cq\u2019. The original character can be obtained with \u2018(aq\u2019 (Unicode u0027).<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

–<\/b><\/p>\n<\/td>\n

<\/td>\n\n

the ISO latin1 \u2018Hyphen, Minus Sign\u2019 (code\u00a045) prints as a hyphen (Unicode u2010). The same output glyph can be requested explicitly with \u2018(hy\u2019. A minus sign can be obtained with \u2018-\u2019 (Unicode u2212).<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

~<\/b><\/p>\n<\/td>\n

<\/td>\n\n

the ISO latin1 \u2018Tilde\u2019 (code\u00a0126) is reduced in size to be usable as a diacritic (Unicode u02DC). A larger glyph can be obtained with \u2018(ti\u2019 (Unicode u007E).<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

^<\/b><\/p>\n<\/td>\n

<\/td>\n\n

the ISO latin1 \u2018Circumflex Accent\u2019 (code\u00a094) is reduced in size to be usable as a diacritic (Unicode u02C6); a larger glyph can be obtained with \u2018(ha\u2019 (Unicode u005E).<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\"Image<\/p>\n

8-bit Character Codes 160 to 255<\/b>
They are interpreted as printable characters according to the latin1<\/i> (ISO-8859-1<\/i>) code set, being identical to the Unicode range Latin-1 Supplement<\/i>.<\/p>\n

Input characters in range 128\u2212159 (on non-EBCDIC hosts) are not printable characters.<\/p>\n\n\n\n
<\/td>\n\n

160<\/p>\n<\/td>\n

<\/td>\n\n

the ISO latin1 no-break space<\/i> is mapped to \u2018~\u2019, the stretchable space character.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

173<\/p>\n<\/td>\n

<\/td>\n\n

the soft hyphen control character. groff<\/b> never uses this character for output (thus it is omitted in the table below); the input character\u00a0173 is mapped onto \u2018%\u2019.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

The remaining ranges (161\u2212172, 174\u2212255) are printable characters that print as themselves. Although they can be specified directly with the keyboard on systems with a latin1 code page, it is better to use their glyph names; see the next section.<\/p>\n

\"Image<\/p>\n

Named Glyphs<\/b>
Glyph names can be embedded into the document text by using escape sequences. groff<\/b>(7) describes how these escape sequences look. Glyph names can consist of quite arbitrary characters from the ASCII or latin1 code set, not only alphanumeric characters. Here some examples:<\/p>\n\n\n
<\/td>\n\n

(ch<\/i><\/p>\n<\/td>\n

<\/td>\n\n

A glyph having the 2-character name ch<\/i>.<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

[char_name<\/i>]<\/p>\n

A glyph having the name char_name<\/i> (having length 1, 2, 3, …). Note that \u2018c<\/i>\u2019 is not the same as \u2018[c<\/i>]\u2019 (c\u00a0<\/i>a single character): The latter is internally mapped to glyph name \u2018c<\/i>\u2019. By default, groff defines a single glyph name starting with a backslash, namely \u2018-\u2019, which can be either accessed as \u2018\u2212\u2019 or \u2018[-]\u2019.<\/p>\n

[base_glyph composite_1 composite_2 …<\/i>]<\/p>\n

A composite glyph; see below for a more detailed description.<\/p>\n

In groff, each 8-bit input character can also referred to by the construct \u2018[charn<\/i>]\u2019 where n<\/i> is the decimal code of the character, a number between 0 and\u00a0255 without leading zeros (those entities are not<\/i> glyph names). They are normally mapped onto glyphs using the .trin request.<\/p>\n

Another special convention is the handling of glyphs with names directly derived from a Unicode code point; this is shown in the \u2018Unicode\u2019 column of the table below. In general, all glyphs not having a name as listed in this manual page can be accessed with the \u2018[uXXXX<\/i>]\u2019 construct. Refer to section \u201cUsing Symbols\u201d in Groff: The GNU Implementation of troff<\/i>, the groff<\/i> Texinfo manual, which describes how groff<\/i> glyph names are constructed.<\/p>\n

Moreover, new glyph names can be created by the .char request; see groff<\/b>(7).<\/p>\n

In the following, a plus sign \u2018+\u2019 in the \u2018Notes\u2019 column indicates that this particular glyph name appears in the PS version of the original troff documentation, CSTR\u00a054.<\/p>\n

Entries marked with \u2018***\u2019 denote glyphs for mathematical purposes (mainly used for DVI output). Normally, such glyphs have metrics which make them unusable in normal text.<\/p>\n

\"Image<\/p>\n

Ligatures and Other Latin Glyphs<\/i><\/p>\n

\"Image<\/p>\n

Accented Characters<\/i><\/p>\n

\"Image<\/p>\n

Accents<\/i><\/p>\n

The composite<\/b> request is used to map most of the accents to non-spacing glyph names; the values given in parentheses are the original (spacing) ones.<\/p>\n

\"Image<\/p>\n

Quotes<\/i><\/p>\n

\"Image<\/p>\n

Punctuation<\/i><\/p>\n

\"Image<\/p>\n

Brackets<\/i><\/p>\n

The extensible bracket pieces are font-invariant glyphs. In classical troff only one glyph was available to vertically extend brackets, braces, and parentheses: \u2018bv\u2019. We map it rather arbitrarily to u23AA.<\/p>\n

Note that not all devices contain extensible bracket pieces which can be piled up with \u2018b\u2019 due to the restrictions of the escape\u2019s piling algorithm. A general solution to build brackets out of pieces is the following macro:<\/p>\n

.\" Make a pile centered vertically 0.5em .\" above the baseline. .\" The first argument is placed at the top. .\" The pile is returned in string \u2019pile\u2019 .eo .de pile-make . nr pile-wd 0 . nr pile-ht 0 . ds pile-args . . nr pile-# n[.$] . while n[pile-#] { . nr pile-wd (n[pile-wd] >? w\u2019$[n[pile-#]]\u2019) . nr pile-ht +(n[rst] - n[rsb]) . as pile-args v\u2019n[rsb]u\u2019\" . as pile-args Z\u2019$[n[pile-#]]\u2019\" . as pile-args v\u2019-n[rst]u\u2019\" . nr pile-# -1 . } . . ds pile v\u2019(-0.5m + (n[pile-ht]u \/ 2u))\u2019\" . as pile *[pile-args]\" . as pile v\u2019((n[pile-ht]u \/ 2u) + 0.5m)\u2019\" . as pile h\u2019n[pile-wd]u\u2019\" .. .ec<\/pre>\n
Another complication is the fact that some glyphs which represent bracket pieces in original troff can be used for other mathematical symbols also, for example \u2018lf\u2019 and \u2018rf\u2019 which provide the \u2018floor\u2019 operator. Other devices (most notably for DVI output) don\u2019t unify such glyphs. For this reason, the four glyphs \u2018lf\u2019, \u2018rf\u2019, \u2018lc\u2019, and \u2018rc\u2019 are not unified with similarly looking bracket pieces. In groff<\/b>, only glyphs with long names are guaranteed to pile up correctly for all devices (provided those glyphs exist).<\/p>\n
\"Image<\/p>\n
Arrows<\/i><\/p>\n
\"Image<\/p>\n
Lines<\/i><\/p>\n
The font-invariant glyphs \u2018br\u2019, \u2018ul\u2019, and \u2018rn\u2019 form corners; they can be used to build boxes. Note that both the PostScript and the Unicode-derived names of these three glyphs are just rough approximations.<\/p>\n
\u2018rn\u2019 also serves in classical troff as the horizontal extension of the square root sign.<\/p>\n
\u2018ru\u2019 is a font-invariant glyph, namely a rule of length 0.5m.<\/p>\n
\"Image<\/p>\n
Use \u2018[radicalex]\u2019, not \u2018[overline]\u2019, for continuation of square root.<\/p>\n
Text markers<\/i><\/p>\n
\"Image<\/p>\n
Legal Symbols<\/i><\/p>\n
\"Image<\/p>\n
The Bell Labs logo is not supported in groff.<\/p>\n
Currency symbols<\/i><\/p>\n
\"Image<\/p>\n
Units<\/i><\/p>\n
\"Image<\/p>\n
Logical Symbols<\/i><\/p>\n
\u00a0<\/p>\n
\"Image<\/p>\n
Mathematical Symbols<\/i><\/p>\n
\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/p>\n
\"Image<\/p>\n
Greek glyphs<\/i><\/p>\n
These glyphs are intended for technical use, not for real Greek; normally, the uppercase letters have upright shape, and the lowercase ones are slanted. There is a problem with the mapping of letter phi to Unicode. Prior to Unicode version\u00a03.0, the difference between U+03C6, GREEK SMALL LETTER PHI, and U+03D5, GREEK PHI SYMBOL, was not clearly described; only the glyph shapes in the Unicode book could be used as a reference. Starting with Unicode\u00a03.0, the reference glyphs have been exchanged and described verbally also: In mathematical context, U+03D5 is the stroked variant and U+03C6 the curly glyph. Unfortunately, most font vendors didn\u2019t update their fonts to this (incompatible) change in Unicode. At the time of this writing (January 2006), it is not clear yet whether the Adobe Glyph Names \u2018phi\u2019 and \u2018phi1\u2019 also change its meaning if used for mathematics, thus compatibility problems are likely to happen \u2013 being conservative, groff currently assumes that \u2018phi\u2019 in a PostScript symbol font is the stroked version.<\/p>\n
In groff, symbol \u2018[*f]\u2019 always denotes the stroked version of phi, and \u2018[+f]\u2019 the curly variant.<\/p>\n
\"Image<\/p>\n
Card symbols<\/i><\/p>\n
\"Image<\/p>\n
AUTHORS <\/a> <\/h2>\n
This document was written by James Clark<\/a>, with additions by Werner Lemberg<\/a> and Bernd Warken<\/a>, and revised to use real tables by Eric S. Raymond<\/a>.<\/p>\n
SEE ALSO <\/a> <\/h2>\n
Groff: The GNU Implementation of troff<\/i>, by Trent A. Fisher and Werner Lemberg, is the primary groff<\/i> manual. Section \u201cUsing Symbols\u201d may be of particular note. You can browse it interactively with \u201cinfo ‘(groff)Using Symbols’\u201d. 
 groff<\/b>(1)<\/p>\n
the GNU roff formatter<\/p>\n
groff<\/b>(7)<\/p>\n
a short reference of the groff formatting language<\/p>\n
An extension to the troff character set for Europe<\/i>, E.G. Keizer, K.J. Simonsen, J. Akkerhuis; EUUG Newsletter, Volume 9, No. 2, Summer 1989 
 The Unicode Standard<\/a><\/p>\n
\n","protected":false},"excerpt":{"rendered":"
  groff_char \u2212 groff glyph names <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[971],"tags":[973,1205,972],"class_list":["post-4126","post","type-post","status-publish","format-standard","hentry","category-7-miscelanea","tag-973","tag-groff_char","tag-man7"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4126","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=4126"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/4126\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=4126"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=4126"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=4126"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}