{
    "mode": "man",
    "parameter": "groff_char",
    "section": "7",
    "url": "https://www.chedong.com/phpMan.php/man/groff_char/7/json",
    "generated": "2026-10-04T13:34:07Z",
    "sections": {
        "Name": {
            "content": "groffchar - GNU roff special character and glyph repertoire\n",
            "subsections": []
        },
        "Description": {
            "content": "The  GNU roff typesetting system has a large glyph repertoire suitable for production of var‐\nied literary, professional, technical, and mathematical documents.  groff works with  charac‐\nters; an output device renders glyphs.  groff's input character set is restricted to that de‐\nfined  by  the  standards  ISO  Latin-1  (ISO  8859-1)  and CCSID “code page” 1047 (an EBCDIC\narrangement of Latin-1).  For ease of document maintenance in UTF-8 environments, it  is  ad‐\nvisable  to  use  only  the Unicode basic Latin code points, a subset of all of the foregoing\nhistorically referred to as US-ASCII, which has only 94 visible, printable code  points.   In\ngroff, these are termed ordinary characters.  Often, many more are desired in output.\n\nAT&T  troff in the 1970s faced a similar problem: the available typesetter's glyph repertoire\ndiffered from that of the computers that controlled it.  troff's solution was a form  of  es‐\ncape  sequence  known as a special character to access several dozen additional glyphs avail‐\nable in the fonts prepared for mounting in the phototypesetter.   These  glyphs  were  mapped\nonto a two-character name space for a degree of mnemonic convenience; for example, the escape\nsequence \\(aa encoded an acute accent and \\(sc a section sign.\n\ngroff  has  lifted  historical roff limitations on special character name lengths, but recog‐\nnizes and retains compatibility with the historical names.   groff  expands  the  lexicon  of\nglyphs  available  by name and permits users to define their own special character escape se‐\nquences with the char request.  Special character names are groff  identifiers;  see  section\n“Identifiers” in groff(7).  Our discussion uses the terms “glyph name” and “special character\nname” interchangeably; we assume no character translations or redefinitions.\n\nThis  document  lists all of the glyph names predefined by groff's font description files and\npresents the systematic notation by which it enables access to arbitrary Unicode code  points\nand  construction  of composite glyphs.  Glyphs listed may be unavailable, or may vary in ap‐\npearance, depending on the output device and font chosen when the page was  formatted.   This\npage was rendered for device utf8 using font R.\n\nA few escape sequences that are not groff special characters also produce glyphs; these exist\nfor  syntactical  or  historical  reasons.  \\', \\`, \\-, and \\ are translated on input to the\nspecial character escape sequences \\[aa], \\[ga], \\[-], and \\[ul], respectively.   Others  in‐\nclude  \\\\,  \\.  (backslash-dot),  and \\e; see groff(7).  A small number of special characters\nrepresent glyphs that are not encoded in Unicode; examples include the  baseline  rule  \\[ru]\nand the Bell System logo \\[bs].\n\nIn groff, you can test output device support for any character (ordinary or special) with the\nconditional expression operator “c”.\n.ie c \\[bs] \\{Welcome to the \\[bs] Bell System;\ndid you get the Wehrmacht helmet or the Death Star?\\}\n.el No Bell System logo.\n\nFor  brevity  in  the remainder of this document, we shall refer to systems conforming to the\nISO 646:1991 IRV, ISO 8859, or ISO 10646 (“Unicode”) character encoding  standards  as  “ISO”\nsystems,  and those employing IBM code page 1047 as “EBCDIC” systems.  That said, EBCDIC sys‐\ntems that support groff are known to also support UTF-8.\n\nWhile groff accepts eight-bit encoded input, not all such code points are valid as input.  On\nISO platforms, character codes 0, 11, 13–31, and 128–159 are invalid.  (This is all C0 and C1\ncontrols except for SOH through LF [Control+A to Control+J], and FF [Control+L].)  On  EBCDIC\nplatforms,  0,  8–9,  11, 13–20, 23–31, and 48–63 are invalid.  Some of these code points are\nused by groff for internal purposes, which is one reason it does not support UTF-8 natively.\n",
            "subsections": [
                {
                    "name": "Fundamental character set",
                    "content": "The ordinary characters catalogued above, plus the space,  tab,  newline,  and  leader  (Con‐\ntrol+A),  form  the fundamental character set for groff input; anything in the language, even\nover one million code points in Unicode, can be expressed using it.   On  ISO  systems,  code\npoints  in the range 33–126 comprise a common set of printable glyphs in all of the aforemen‐\ntioned ISO character encoding standards.  It is this character set and (with some  noteworthy\nexceptions)  the  corresponding  glyph  repertoire  for which AT&T troff was implemented.  On\nEBCDIC systems, printable characters are in the range 66–201 and 203–254; those without coun‐\nterparts in the ISO range 33–126 are discussed in the next subsection.\n\nAll of the following characters map to glyphs as you would expect.\n┌───────────────────────────────────────────────────────────┐\n│ ! # $ % & ( ) * + , . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ │\n│ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ ]  │\n│ a b c d e f g h i j k l m n o p q r s t u v w x y z { | } │\n└───────────────────────────────────────────────────────────┘\nThe remaining ordinary characters surprise computing professionals and others intimately  fa‐\nmiliar  with  the  ISO  character encodings.  The developers of AT&T troff chose mappings for\nthem that would be useful for typesetting technical literature in a broad range of scientific\ndisciplines: Bell Labs used the system for preparation of AT&T's patent filings with the U.S.\ngovernment.  Further, the prevailing character encoding standard in the 1970s, USAS X3.4-1968\n(“ASCII”), deliberately supported semantic ambiguity at some code points, and  outright  sub‐\nstitution  at  several others, to suit the localization demands of various national standards\nbodies.\n\nThe table below presents the seven exceptional code points with their typical keycap  engrav‐\nings,  their glyph mappings and semantics in roff systems, and the escape sequences producing\nthe Unicode basic Latin character they replace.  The first, the neutral double  quote,  is  a\npartial  exception because it does represent itself, but since the roff language also uses it\nto quote macro arguments, groff supports a special character escape sequence as  an  alterna‐\ntive  form  so that the glyph can be easily included in macro arguments without requiring the\nuser to master the quoting rules that AT&T troff required in that context.   (Some  requests,\nlike  ds,  also treat \" non-literally.)  Furthermore, not all of the special character escape\nsequences are portable to AT&T troff and all of its descendants; these groff  extensions  are\npresented using its special character form \\[], whereas portable special character escape se‐\nquences  are  shown  in the traditional \\( form.  \\- and \\e are portable to all known troffs.\n\\e means “the glyph of the current escape character”; it  therefore  can  produce  unexpected\noutput  if the ec request is used.  On devices with a limited glyph repertoire, glyphs in the\n“keycap” and “appearance” columns on the same row of the table may look identical; except for\nthe neutral double quote, this will not be the case on  more-capable  devices.   Review  your\ndocument using as many different output devices as possible.\n\n┌───────────────────────────────────────────────────────────────────┐\n│ Keycap   Appearance and meaning   Special character and meaning   │\n├───────────────────────────────────────────────────────────────────┤\n│ \"        \" neutral double quote   \\[dq] neutral double quote      │\n│ '        ’ closing single quote   \\[aq] neutral apostrophe        │\n│ -        - hyphen                 \\- or \\[-] minus sign/Unix dash │\n│ \\        (escape character)       \\e or \\[rs] reverse solidus     │\n│ ^        ˆ modifier circumflex    \\(ha circumflex/caret/“hat”     │\n│ `        ‘ opening single quote   \\(ga grave accent               │\n│ ~        ˜ modifier tilde         \\(ti tilde                      │\n└───────────────────────────────────────────────────────────────────┘\n\nThe  hyphen-minus is a particularly unfortunate case of overloading.  Its awkward name in ISO\n8859 and later standards reflects the many distinguishable purposes to which it  had  already\nbeen  put by the 1980s, including a hyphen, a minus sign, and (alone or in repetition) dashes\nof varying widths.  For best results in roff systems, use the “-” character in input  outside\nan  escape sequence only to mean a hyphen, as in the phrase “long-term”.  For a minus sign in\nrunning text or a Unix command-line option dash, use \\- (or \\[-] in  groff  if  you  find  it\nhelps  the  clarity  of  the  source document).  (Another minus sign, for use in mathematical\nequations, is available as \\[mi]).  AT&T troff supported em-dashes as \\(em, as does groff.\n\nThe special character escape sequence for the apostrophe as a neutral single quote  is  typi‐\ncally  needed  only in technical content; typing words like “can't” and “Anne's” in a natural\nway will render correctly, because in ordinary prose an apostrophe is  typeset  either  as  a\nclosing  single quotation mark or as a neutral single quote, depending on the capabilities of\nthe output device.  By contrast, special character escape sequences should be used for quota‐\ntion marks unless portability to limited or historical troff implementations is necessary; on\nthose systems, the input convention is to pair the grave accent with the apostrophe for  sin‐\ngle  quotes,  and to double both characters for double quotes.  AT&T troff defined no special\ncharacters for quotation marks or the apostrophe.  Repeated single quotes (‘‘thus’’) will  be\nvisually distinguishable from double quotes (“thus”) on terminal devices, and perhaps on oth‐\ners (depending on the font selected).\n┌─────────────────────────────────────────────────────────────────┐\n│ AT&T troff input          recommended groff input               │\n├─────────────────────────────────────────────────────────────────┤\n│ A Winter's Tale           A Winter's Tale                       │\n│ `U.K. outer quotes'       \\[oq]U.K. outer quotes\\[cq]           │\n│ `U.K. ``inner'' quotes'   \\[oq]U.K. \\[lq]inner\\[rq] quotes\\[cq] │\n│ ``U.S. outer quotes''     \\[lq]U.S. outer quotes\\[rq]           │\n│ ``U.S. `inner' quotes''   \\[lq]U.S. \\[oq]inner\\[cq] quotes\\[rq] │\n└─────────────────────────────────────────────────────────────────┘\nIf  you  frequently require quotation marks in your document, see if the macro package you're\nusing supplies strings or macros to facilitate quotation, or define them yourself (except  in\nman pages).\n\nUsing Unicode basic Latin characters to compose boxes and lines is ill-advised.  roff systems\nhave  special characters for drawing horizontal and vertical lines; see subsection “Rules and\nlines” below.  Preprocessors like tbl(1) and pic(1) draw boxes and will produce the best pos‐\nsible output for the device, falling back to basic Latin glyphs only when necessary.\n"
                },
                {
                    "name": "Eight-bit encodings and Latin-1 supplement",
                    "content": "ISO 646 is a seven-bit code encoding 128 code points; eight-bit codes  are  twice  the  size.\nISO  8859-1  and code page 1047 allocated the additional space to what Unicode calls “C1 con‐\ntrols” (control characters) and the “Latin-1 supplement”.  The C1 controls are neither print‐\nable nor usable as groff input.\n\nTwo Latin-1 supplement characters are handled specially on input.  troff never produces  them\nas output.\n\nNBSP   encodes a no-break space; it is mapped to \\~, the adjustable non-breaking space escape\nsequence.\n\nSHY    encodes a soft hyphen; it is mapped to \\%, the hyphenation control escape sequence.\n\nThe  remaining  characters in the Latin-1 supplement represent themselves.  Although they can\nbe specified directly with the keyboard on systems configured to use Latin-1 as the character\nencoding, it is more portable, both to other roff systems and to UTF-8 environments,  to  use\ntheir  special  character  escape  sequences, shown below.  The glyph descriptions we use are\nnon-standard in some cases, for brevity.\n\n¡  \\[r!] inverted exclamation mark     Ñ  \\[~N] N tilde\n¢  \\[ct] cent sign                     Ò  \\[`O] O grave\n£  \\[Po] pound sign                    Ó  \\['O] O acute\n¤  \\[Cs] currency sign                 Ô  \\[^O] O circumflex\n¥  \\[Ye] yen sign                      Õ  \\[~O] O tilde\n¦  \\[bb] broken bar                    Ö  \\[:O] O dieresis\n§  \\[sc] section sign                  ×  \\[mu] multiplication sign\n¨  \\[ad] dieresis accent               Ø  \\[/O] O slash\n©  \\[co] copyright sign                Ù  \\[`U] U grave\nª  \\[Of] feminine ordinal indicator    Ú  \\['U] U acute\n«  \\[Fo] left double chevron           Û  \\[^U] U circumflex\n¬  \\[no] logical not                   Ü  \\[:U] U dieresis\n®  \\[rg] registered sign               Ý  \\['Y] Y acute\n¯  \\[a-] macron accent                 Þ  \\[TP] uppercase thorn\n°  \\[de] degree sign                   ß  \\[ss] lowercase sharp s\n±  \\[+-] plus-minus                    à  \\[`a] a grave\n²  \\[S2] superscript two               á  \\['a] a acute\n³  \\[S3] superscript three             â  \\[^a] a circumflex\n´  \\[aa] acute accent                  ã  \\[~a] a tilde\nµ  \\[mc] micro sign                    ä  \\[:a] a dieresis\n¶  \\[ps] pilcrow sign                  å  \\[oa] a ring\n·  \\[pc] centered period               æ  \\[ae] ae ligature\n¸  \\[ac] cedilla accent                ç  \\[,c] c cedilla\n¹  \\[S1] superscript one               è  \\[`e] e grave\nº  \\[Om] masculine ordinal indicator   é  \\['e] e acute\n»  \\[Fc] right double chevron          ê  \\[^e] e circumflex\n¼  \\[14] one quarter symbol            ë  \\[:e] e dieresis\n½  \\[12] one half symbol               ì  \\[`i] i grave\n¾  \\[34] three quarters symbol         í  \\['i] e acute\n¿  \\[r?] inverted question mark        î  \\[^i] i circumflex\nÀ  \\[`A] A grave                       ï  \\[:i] i dieresis\nÁ  \\['A] A acute                       ð  \\[Sd] lowercase eth\n  \\[^A] A circumflex                  ñ  \\[~n] n tilde\nà  \\[~A] A tilde                       ò  \\[`o] o grave\nÄ  \\[:A] A dieresis                    ó  \\['o] o acute\nÅ  \\[oA] A ring                        ô  \\[^o] o circumflex\nÆ  \\[AE] AE ligature                   õ  \\[~o] o tilde\nÇ  \\[,C] C cedilla                     ö  \\[:o] o dieresis\nÈ  \\[`E] E grave                       ÷  \\[di] division sign\nÉ  \\['E] E acute                       ø  \\[/o] o slash\nÊ  \\[^E] E circumflex                  ù  \\[`u] u grave\nË  \\[:E] E dieresis                    ú  \\['u] u acute\nÌ  \\[`I] I grave                       û  \\[^u] u circumflex\nÍ  \\['I] I acute                       ü  \\[:u] u dieresis\nÎ  \\[^I] I circumflex                  ý  \\['y] y acute\nÏ  \\[:I] I dieresis                    þ  \\[Tp] lowercase thorn\nÐ  \\[-D] uppercase eth                 ÿ  \\[:y] y dieresis\n"
                },
                {
                    "name": "Special character escape forms",
                    "content": "Glyphs that lack a character code in the basic Latin repertoire to  directly  represent  them\nare  entered  by one of several special character escape forms.  Such glyphs can be simple or\ncomposite, and accessed either by name or numerically by code point.  Code points and combin‐\ning properties are determined by character encoding standards, whereas glyph  names  as  used\nhere originated in AT&T troff special character escape sequences.  Predefined glyph names use\nonly characters in the basic Latin repertoire.\n\n\\(gl   is  a  special character escape sequence for the glyph with the two-character name gl.\nThis is the original syntax form supported by AT&T troff.  The acute accent, \\(aa,  is\nan example.\n\n\\C'glyph-name'\nis  a  special  character  escape  sequence  for glyph-name, which can be of arbitrary\nlength.  The delimiter, shown here as a neutral apostrophe, can be any  character  not\noccurring  in  glyph-name.   This syntax form was introduced in later versions of AT&T\ndevice-independent troff.  The foregoing acute accent  example  can  be  expressed  as\n\\C'aa'.\n\n\\[glyph-name]\nis  a  special  character  escape  sequence  for glyph-name, which can be of arbitrary\nlength but must not contain a closing square bracket “]”.  (No glyph names  predefined\nby groff employ “]”.)  The foregoing acute accent example can be expressed in groff as\n\\[aa].\n\n\\C'c' and \\[c] are not synonyms for the ordinary character “c”, but request the special char‐\nacter  named  “\\c”.   For example, “\\[a]” is not “a”, but rather a special character with the\ninternal glyph name (used in font description files and diagnostic  messages)  \\a,  which  is\ntypically  undefined.  The only such glyph name groff predefines is the minus sign, which can\ntherefore be accessed as \\C'-' or \\[-].\n\n\\[base-char composite-1 composite-2 ... composite-n]\nis a composite glyph.  Glyphs like a lowercase “e” with an acute  accent,  as  in  the\nword  “café”, can be expressed as \\[e aa].  See subsection “Accents” below for a table\nof combining glyph names.\n\nUnicode encodes far more characters than groff has glyph names for; special character  escape\nforms based on numerical code points enable access to any of them.  Frequently used glyphs or\nglyph  combinations  can be stored in strings, and new glyph names can be created ad hoc with\nthe char request; see groff(7).\n\n\\[unnnn[n[n]]]\nis a Unicode numeric special character escape sequence.  Any Unicode code point can be\naccessed with four to six hexadecimal digits, with hexadecimal letters accepted in up‐\npercase form only.  Thus, \\[u02DA] accesses the (spacing) ring accent, producing “˚”.\n\nUnicode code points can be composed as well; when they are, GNU troff requires  NFD  (Normal‐\nization  Form D), where all Unicode glyphs are maximally decomposed.  (Exception: precomposed\ncharacters in the Latin-1 supplement described above are also accepted.  Do not count on this\nexception remaining in a future GNU troff that accepts  UTF-8  input  directly.)   Thus,  GNU\ntroff  accepts  “caf\\['e]”,  “caf\\[e  aa]”,  and “caf\\[u00650301]”, as ways to input “café”.\n(Due to its legacy 8-bit encoding compatibility, at present it also accepts “caf\\[u00E9]”  on\nISO Latin-1 systems.)\n\n\\[ubase-char[combining-component]...]\nconstructs  a composite glyph from Unicode numeric special character escape sequences.\nThe code points of the base glyph and the combining components are each  expressed  in\nhexadecimal,  with  an  underscore () separating each component.  Thus, \\[u006E0303]\nproduces “ñ”.\n\n\\[charnnn]\nexpresses an eight-bit code point where nnn is the code point of the character, a dec‐\nimal number between 0 and 255 without leading zeroes.   This  legacy  numeric  special\ncharacter  escape  sequence is used to map characters onto glyphs via the trin request\nin macro files loaded by grotty(1).\n"
                }
            ]
        },
        "Glyph tables": {
            "content": "In this section, groff's glyph name repertoire is presented in tabular form.  The meanings of\nthe columns are as follows.\n\nOutput  shows the glyph as it appears on the device used to render this document; although it\ncan have a notably different shape on other devices (and is subject to  user-directed\ntranslation and replacement), groff attempts reasonable equivalency on all output de‐\nvices.\n\nInput   shows  the  groff  character  (ordinary or special) that normally produces the glyph.\nSome code points have multiple glyph names.\n\nUnicode is the code point notation for the glyph or combining glyph sequence as described  in\nsubsection  “Special  character  escape forms” above.  It corresponds to the standard\nnotation for Unicode short identifiers such that groff's unnnn is equivalent to  Uni‐\ncode's U+nnnn.\n\nNotes   describes the glyph, elucidating the mnemonic value of the glyph name where possible.\n\nA  plus  sign “+” indicates that the glyph name appears in the AT&T troff user's man‐\nual, CSTR #54 (1992 revision).  When using the AT&T special  character  syntax  \\(xx,\nwidespread portability can be expected from such names.\n\nEntries  marked with “*” denote glyphs used for mathematical purposes.  On typeset‐\nting  devices,  such  glyphs  are  typically  drawn  from   a   special   font   (see\ngrofffont(5)).   Often,  such glyphs lack bold or italic style forms or have metrics\nthat look incongruous in ordinary prose.  A few which are  not  uncommon  in  running\ntext  have  “text variants”, which should work better in that context.  Conversely, a\nhandful of glyphs that are normally drawn from a text font may be required in  mathe‐\nmatical equations.  Both sets of exceptions are noted in the tables where they appear\n(“Logical symbols” and “Mathematical symbols”).\n",
            "subsections": [
                {
                    "name": "Basic Latin",
                    "content": "Apart from basic Latin characters with special mappings, described in subsection “Fundamental\ncharacter  set”  above, a few others in that range have special character glyph names.  These\nwere defined for ease of input on non-U.S. keyboards lacking keycaps for them, or for  symme‐\ntry with other special character glyph names serving a similar purpose.\n\nThe  vertical bar is overloaded; the \\[ba] and \\[or] escape sequences may render differently.\nSee subsection “Mathematical symbols” below for special variants  of  the  plus,  minus,  and\nequals signs normally drawn from this range.\n\nOutput   Input   Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n\"        \\[dq]   u0022     neutral double quote\n#        \\[sh]   u0023     number sign\n$        \\[Do]   u0024     dollar sign\n'        \\[aq]   u0027     apostrophe, neutral single quote\n/        \\[sl]   u002F     slash, solidus +\n@        \\[at]   u0040     at sign\n[        \\[lB]   u005B     left square bracket\n\\        \\[rs]   u005C     reverse solidus\n]        \\[rB]   u005D     right square bracket\n^        \\[ha]   u005E     circumflex, caret, “hat”\n{        \\[lC]   u007B     left brace\n|        |       u007C     bar\n|        \\[ba]   u007C     bar\n|        \\[or]   u007C     bitwise or +\n}        \\[rC]   u007D     right brace\n~        \\[ti]   u007E     tilde\n"
                },
                {
                    "name": "Supplementary Latin letters",
                    "content": "Historically,  \\[ss]  could be considered a ligature of “sz”.  An uppercase form is available\nas \\[u1E9E], but in the German language it is of specialized use; ß does not normally  upper‐\ncase-transform to it, but rather to “SS”.  “Lowercase f with hook” is also used as a function\nsymbol; see subsection “Mathematical symbols” below.\n\nOutput   Input   Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\nÐ        \\[-D]   u00D0     uppercase eth\nð        \\[Sd]   u00F0     lowercase eth\nÞ        \\[TP]   u00DE     uppercase thorn\nþ        \\[Tp]   u00FE     lowercase thorn\nß        \\[ss]   u00DF     lowercase sharp s\nı        \\[.i]   u0131     i without tittle\nȷ        \\[.j]   u0237     j without tittle\nƒ        \\[Fn]   u0192     lowercase f with hook, function\nŁ        \\[/L]   u0141     L with stroke\nł        \\[/l]   u0142     l with stroke\nØ        \\[/O]   u00D8     O with stroke\nø        \\[/o]   u00F8     o with stroke\n"
                },
                {
                    "name": "Ligatures and digraphs",
                    "content": "Output   Input   Unicode           Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\nff       \\[ff]   u00660066        ff ligature +\nfi       \\[fi]   u00660069        fi ligature +\nfl       \\[fl]   u0066006C        fl ligature +\nffi      \\[Fi]   u006600660069   ffi ligature +\nffl      \\[Fl]   u00660066006C   ffl ligature +\nÆ        \\[AE]   u00C6             AE ligature\næ        \\[ae]   u00E6             ae ligature\nŒ        \\[OE]   u0152             OE ligature\nœ        \\[oe]   u0153             oe ligature\nIJ        \\[IJ]   u0132             IJ digraph\nij        \\[ij]   u0133             ij digraph\n"
                },
                {
                    "name": "Accents",
                    "content": "Normally,  the formatting of a special character advances the drawing position as an ordinary\ncharacter does.  groff's composite request designates a special character as combining.   The\ncomposite.tmac  macro  file,  loaded automatically by the default troffrc, maps the following\nspecial characters to the combining characters shown below.  The non-combining code point  in\nparentheses  is used when the special character occurs in isolation (compare “caf\\[e aa]” and\n“caf\\[aa]e”).\n\nOutput   Input   Unicode         Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n˝        \\[a\"]   u030B (u02DD)   double acute accent\n¯        \\[a-]   u0304 (u00AF)   macron accent\n˙        \\[a.]   u0307 (u02D9)   dot accent\n^        \\[a^]   u0302 (u005E)   circumflex accent\n´        \\[aa]   u0301 (u00B4)   acute accent +\n`        \\[ga]   u0300 (u0060)   grave accent +\n˘        \\[ab]   u0306 (u02D8)   breve accent\n¸        \\[ac]   u0327 (u00B8)   cedilla accent\n¨        \\[ad]   u0308 (u00A8)   dieresis accent\nˇ        \\[ah]   u030C (u02C7)   caron accent\n˚        \\[ao]   u030A (u02DA)   ring accent\n~        \\[a~]   u0303 (u007E)   tilde accent\n˛        \\[ho]   u0328 (u02DB)   hook accent\n"
                },
                {
                    "name": "Accented characters",
                    "content": "All of these glyphs can be composed using combining glyph names as  described  in  subsection\n“Special character escape forms” above; the names below are short aliases for convenience.\n\nOutput   Input   Unicode      Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\nÁ        \\['A]   u00410301   A acute\nĆ        \\['C]   u00430301   C acute\nÉ        \\['E]   u00450301   E acute\nÍ        \\['I]   u00490301   I acute\nÓ        \\['O]   u004F0301   O acute\nÚ        \\['U]   u00550301   U acute\nÝ        \\['Y]   u00590301   Y acute\ná        \\['a]   u00610301   a acute\nć        \\['c]   u00630301   c acute\né        \\['e]   u00650301   e acute\ní        \\['i]   u00690301   i acute\nó        \\['o]   u006F0301   o acute\nú        \\['u]   u00750301   u acute\ný        \\['y]   u00790301   y acute\n\nÄ        \\[:A]   u00410308   A dieresis\nË        \\[:E]   u00450308   E dieresis\nÏ        \\[:I]   u00490308   I dieresis\nÖ        \\[:O]   u004F0308   O dieresis\nÜ        \\[:U]   u00550308   U dieresis\nŸ        \\[:Y]   u00590308   Y dieresis\nä        \\[:a]   u00610308   a dieresis\në        \\[:e]   u00650308   e dieresis\nï        \\[:i]   u00690308   i dieresis\nö        \\[:o]   u006F0308   o dieresis\nü        \\[:u]   u00750308   u dieresis\nÿ        \\[:y]   u00790308   y dieresis\n\n        \\[^A]   u00410302   A circumflex\nÊ        \\[^E]   u00450302   E circumflex\nÎ        \\[^I]   u00490302   I circumflex\nÔ        \\[^O]   u004F0302   O circumflex\nÛ        \\[^U]   u00550302   U circumflex\nâ        \\[^a]   u00610302   a circumflex\nê        \\[^e]   u00650302   e circumflex\nî        \\[^i]   u00690302   i circumflex\nô        \\[^o]   u006F0302   o circumflex\nû        \\[^u]   u00750302   u circumflex\n\nÀ        \\[`A]   u00410300   A grave\nÈ        \\[`E]   u00450300   E grave\nÌ        \\[`I]   u00490300   I grave\nÒ        \\[`O]   u004F0300   O grave\nÙ        \\[`U]   u00550300   U grave\nà        \\[`a]   u00610300   a grave\nè        \\[`e]   u00650300   e grave\nì        \\[`i]   u00690300   i grave\nò        \\[`o]   u006F0300   o grave\nù        \\[`u]   u00750300   u grave\n\nà        \\[~A]   u00410303   A tilde\nÑ        \\[~N]   u004E0303   N tilde\nÕ        \\[~O]   u004F0303   O tilde\nã        \\[~a]   u00610303   a tilde\nñ        \\[~n]   u006E0303   n tilde\nõ        \\[~o]   u006F0303   o tilde\n\nŠ        \\[vS]   u0053030C   S caron\nš        \\[vs]   u0073030C   s caron\nŽ        \\[vZ]   u005A030C   Z caron\nž        \\[vz]   u007A030C   z caron\n\nÇ        \\[,C]   u00430327   C cedilla\nç        \\[,c]   u00630327   c cedilla\n\nÅ        \\[oA]   u0041030A   A ring\nå        \\[oa]   u0061030A   a ring\n"
                },
                {
                    "name": "Quotation marks",
                    "content": "The neutral double quote, often useful when documenting programming languages, is also avail‐\nable as a special character for convenient embedding in macro arguments; see subsection “Fun‐\ndamental character set” above.\n\nOutput   Input   Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n„        \\[Bq]   u201E     low double comma quote\n‚        \\[bq]   u201A     low single comma quote\n“        \\[lq]   u201C     left double quote\n”        \\[rq]   u201D     right double quote\n‘        \\[oq]   u2018     single opening (left) quote\n’        \\[cq]   u2019     single closing (right) quote\n'        \\[aq]   u0027     apostrophe, neutral single quote\n\"        \"       u0022     neutral double quote\n\"        \\[dq]   u0022     neutral double quote\n«        \\[Fo]   u00AB     left double chevron\n»        \\[Fc]   u00BB     right double chevron\n‹        \\[fo]   u2039     left single chevron\n›        \\[fc]   u203A     right single chevron\n"
                },
                {
                    "name": "Punctuation",
                    "content": "The Unicode name for U+00B7 is “middle dot”, which is unfortunately confusable with the groff\nmnemonic  for  the visually similar but semantically distinct multiplication dot; see subsec‐\ntion “Mathematical symbols” below.\n\nOutput   Input   Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n¡        \\[r!]   u00A1     inverted exclamation mark\n¿        \\[r?]   u00BF     inverted question mark\n·        \\[pc]   u00B7     centered period\n—        \\[em]   u2014     em-dash +\n–        \\[en]   u2013     en-dash\n‐        \\[hy]   u2010     hyphen +\n"
                },
                {
                    "name": "Brackets",
                    "content": "On typesetting devices, the bracket extensions are font-invariant glyphs; that is,  they  are\nrendered  the  same  way  regardless of font (with a drawing escape sequence).  On terminals,\nthey are not font-invariant; groff maps them rather arbitrarily to U+23AA (“curly bracket ex‐\ntension”).  In AT&T troff, only one  glyph  was  available  to  vertically  extend  brackets,\nbraces, and parentheses: \\(bv.\n\nNot all devices supply bracket pieces that can be piled up with \\b due to the restrictions of\nthe  escape's  piling  algorithm.   A general solution to build brackets out of pieces is the\nfollowing macro:\n.\\\" Make a pile centered vertically 0.5em above the baseline.\n.\\\" The first argument is placed at the top.\n.\\\" The pile is returned in string 'pile'.\n.eo\n.de pile-make\n.  nr pile-wd 0\n.  nr pile-ht 0\n.  ds pile-args\n.\n.  nr pile-# \\n[.$]\n.  while \\n[pile-#] \\{\\\n.    nr pile-wd (\\n[pile-wd] >? \\w'\\$[\\n[pile-#]]')\n.    nr pile-ht +(\\n[rst] - \\n[rsb])\n.    as pile-args \\v'\\n[rsb]u'\\\"\n.    as pile-args \\Z'\\$[\\n[pile-#]]'\\\"\n.    as pile-args \\v'-\\n[rst]u'\\\"\n.    nr pile-# -1\n.  \\}\n.\n.  ds pile \\v'(-0.5m + (\\n[pile-ht]u / 2u))'\\\"\n.  as pile \\*[pile-args]\\\"\n.  as pile \\v'((\\n[pile-ht]u / 2u) + 0.5m)'\\\"\n.  as pile \\h'\\n[pile-wd]u'\\\"\n..\n.ec\n\nAnother complication is the fact that some glyphs which  represent  bracket  pieces  in  AT&T\ntroff  can  be  used for other mathematical symbols as well, for example \\(lf and \\(rf, which\nprovide the floor operator.  Some output devices, such as dvi, don't unify such glyphs.   For\nthis  reason,  the glyphs \\[lf], \\[rf], \\[lc], and \\[rc] are not unified with similar-looking\nbracket pieces.  In groff, only glyphs with long names are guaranteed to  pile  up  correctly\nfor all devices—provided those glyphs are available.\n\nOutput   Input               Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n[        [                   u005B     left square bracket\n[        \\[lB]               u005B     left square bracket\n]        ]                   u005D     right square bracket\n]        \\[rB]               u005D     right square bracket\n{        {                   u007B     left brace\n{        \\[lC]               u007B     left brace\n}        }                   u007D     right brace\n}        \\[rC]               u007D     right brace\n⟨        \\[la]               u27E8     left angle bracket\n⟩        \\[ra]               u27E9     right angle bracket\n⎪        \\[bv]               u23AA     brace vertical extension + *\n⎪        \\[braceex]          u23AA     brace vertical extension\n\n⎡        \\[bracketlefttp]    u23A1     left square bracket top\n⎢        \\[bracketleftex]    u23A2     left square bracket extension\n⎣        \\[bracketleftbt]    u23A3     left square bracket bottom\n\n⎤        \\[bracketrighttp]   u23A4     right square bracket top\n⎥        \\[bracketrightex]   u23A5     right square bracket extension\n⎦        \\[bracketrightbt]   u23A6     right square bracket bottom\n\n⎧        \\[lt]               u23A7     left brace top +\n⎨        \\[lk]               u23A8     left brace middle +\n⎩        \\[lb]               u23A9     left brace bottom +\n⎧        \\[bracelefttp]      u23A7     left brace top\n⎨        \\[braceleftmid]     u23A8     left brace middle\n⎩        \\[braceleftbt]      u23A9     left brace bottom\n⎪        \\[braceleftex]      u23AA     left brace extension\n\n⎫        \\[rt]               u23AB     right brace top +\n⎬        \\[rk]               u23AC     right brace middle +\n⎭        \\[rb]               u23AD     right brace bottom +\n⎫        \\[bracerighttp]     u23AB     right brace top\n⎬        \\[bracerightmid]    u23AC     right brace middle\n⎭        \\[bracerightbt]     u23AD     right brace bottom\n⎪        \\[bracerightex]     u23AA     right brace extension\n\n⎛        \\[parenlefttp]      u239B     left parenthesis top\n⎜        \\[parenleftex]      u239C     left parenthesis extension\n⎝        \\[parenleftbt]      u239D     left parenthesis bottom\n⎞        \\[parenrighttp]     u239E     right parenthesis top\n⎟        \\[parenrightex]     u239F     right parenthesis extension\n⎠        \\[parenrightbt]     u23A0     right parenthesis bottom\n"
                },
                {
                    "name": "Arrows",
                    "content": "Output   Input   Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n←        \\[<-]   u2190     horizontal arrow left +\n→        \\[->]   u2192     horizontal arrow right +\n↔        \\[<>]   u2194     bidirectional horizontal arrow\n↓        \\[da]   u2193     vertical arrow down +\n↑        \\[ua]   u2191     vertical arrow up +\n↕        \\[va]   u2195     bidirectional vertical arrow\n⇐        \\[lA]   u21D0     horizontal double arrow left\n⇒        \\[rA]   u21D2     horizontal double arrow right\n⇔        \\[hA]   u21D4     bidirectional horizontal double arrow\n⇓        \\[dA]   u21D3     vertical double arrow down\n⇑        \\[uA]   u21D1     vertical double arrow up\n⇕        \\[vA]   u21D5     bidirectional vertical double arrow\n⎯        \\[an]   u23AF     horizontal arrow extension\n"
                },
                {
                    "name": "Rules and lines",
                    "content": "On  typesetting  devices,  the font-invariant glyphs (see subsection “Brackets” above) \\[br],\n\\[ul], and \\[rn] form corners when adjacent; they can be used to build  boxes.   On  terminal\ndevices,  they  are  mapped  as shown in the table.  The Unicode-derived names of these three\nglyphs are approximations.\n\nThe input character  always accesses the underscore glyph in a font; \\[ul], by contrast, may\nbe font-invariant on typesetting devices.\n\nThe baseline rule \\[ru] is a font-invariant glyph, namely a rule of one-half em.\n\nIn AT&T troff, \\[rn] also served as a one en extension of the square root symbol.  groff  fa‐\nvors \\[radicalex] for this purpose; see subsection “Mathematical symbols” below.\n\nOutput   Input   Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n|        |       u007C     bar\n|        \\[ba]   u007C     bar\n│        \\[br]   u2502     box rule +\nu005F     underscore, low line +\n\\[ul]   ---       underrule +\n‾        \\[rn]   u203E     overline +\n\\[ru]   ---       baseline rule +\n¦        \\[bb]   u00A6     broken bar\n/        /       u002F     slash, solidus +\n/        \\[sl]   u002F     slash, solidus +\n\\        \\[rs]   u005C     reverse solidus\n"
                },
                {
                    "name": "Text markers",
                    "content": "Output   Input   Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n○        \\[ci]   u25CB     circle +\n•        \\[bu]   u2022     bullet +\n†        \\[dg]   u2020     dagger +\n‡        \\[dd]   u2021     double dagger +\n◊        \\[lz]   u25CA     lozenge, diamond\n□        \\[sq]   u25A1     square +\n¶        \\[ps]   u00B6     pilcrow sign\n§        \\[sc]   u00A7     section sign +\n☜        \\[lh]   u261C     hand pointing left +\n☞        \\[rh]   u261E     hand pointing right +\n@        @       u0040     at sign\n@        \\[at]   u0040     at sign\n#        #       u0023     number sign\n#        \\[sh]   u0023     number sign\n↵        \\[CR]   u21B5     carriage return\n✓        \\[OK]   u2713     check mark\n"
                },
                {
                    "name": "Legal symbols",
                    "content": "The Bell System logo is not supported in groff.\n\nOutput   Input   Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n©        \\[co]   u00A9     copyright sign +\n®        \\[rg]   u00AE     registered sign +\n™        \\[tm]   u2122     trade mark sign\n\\[bs]   ---       Bell System logo +\n"
                },
                {
                    "name": "Currency symbols",
                    "content": "Output   Input   Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n$        $       u0024     dollar sign\n$        \\[Do]   u0024     dollar sign\n¢        \\[ct]   u00A2     cent sign +\n€        \\[eu]   u20AC     Euro sign\n€        \\[Eu]   u20AC     variant Euro sign\n¥        \\[Ye]   u00A5     yen sign\n£        \\[Po]   u00A3     pound sign\n¤        \\[Cs]   u00A4     currency sign\n"
                },
                {
                    "name": "Units",
                    "content": "Output   Input   Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n°        \\[de]   u00B0     degree sign +\n‰        \\[%0]   u2030     per thousand, per mille sign\n′        \\[fm]   u2032     arc minute sign, foot mark +\n″        \\[sd]   u2033     arc second sign\nµ        \\[mc]   u00B5     micro sign\nª        \\[Of]   u00AA     feminine ordinal indicator\nº        \\[Om]   u00BA     masculine ordinal indicator\n"
                },
                {
                    "name": "Logical symbols",
                    "content": "The  variants of the not sign may differ in appearance or spacing depending on the device and\nfont selected.  Unicode does not encode a discrete “bitwise or” sign: on typesetting devices,\nit is drawn shorter than the bar, about the same height as a capital  letter.   Terminal  de‐\nvices unify \\[ba] and \\[or].\n\nOutput   Input    Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n∧        \\[AN]    u2227     logical and\n∨        \\[OR]    u2228     logical or\n¬        \\[no]    u00AC     logical not + *\n¬        \\[tno]   u00AC     text variant of \\[no]\n∃        \\[te]    u2203     there exists\n∀        \\[fa]    u2200     for all\n∋        \\[st]    u220B     such that\n∴        \\[3d]    u2234     therefore\n∴        \\[tf]    u2234     therefore\n|        |        u007C     bar\n|        \\[or]    u007C     bitwise or +\n"
                },
                {
                    "name": "Mathematical symbols",
                    "content": "\\[Fn]  also appears in subsection “Supplementary Latin letters” above.  Observe the two vari‐\neties of the plus-minus, multiplication, and division signs; \\[+-], \\[mu], and \\[di] are nor‐\nmally drawn from the special font, but have text font  variants.   Also  be  aware  of  three\nglyphs  available in special font variants that are normally drawn from text fonts: the plus,\nminus, and equals signs.  These variants may differ in appearance or spacing depending on the\ndevice and font selected.\n\nIn AT&T troff, \\(rn (“root en extender”) served as the horizontal extension  of  the  radical\n(square root) sign, \\(sr, and was drawn at the maximum height of the typeface's bounding box;\nthis enabled the special character to double as an overline (see subsection “Rules and lines”\nabove).   A  contemporary font's radical sign might not ascend to such an extreme.  In groff,\nyou can instead use \\[radicalex] to continue the radical sign \\[sr]; these special characters\nare intended for use with text fonts.  \\[sqrt] and  \\[sqrtex]  are  their  counterparts  with\nmathematical spacing.\n\nOutput   Input          Unicode      Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n½        \\[12]          u00BD        one half symbol +\n¼        \\[14]          u00BC        one quarter symbol +\n¾        \\[34]          u00BE        three quarters symbol +\n⅛        \\[18]          u215B        one eighth symbol\n⅜        \\[38]          u215C        three eighths symbol\n⅝        \\[58]          u215D        five eighths symbol\n⅞        \\[78]          u215E        seven eighths symbol\n¹        \\[S1]          u00B9        superscript one\n²        \\[S2]          u00B2        superscript two\n³        \\[S3]          u00B3        superscript three\n\n+        +              u002B        plus\n+        \\[pl]          u002B        special variant of plus + *\n-        \\[-]           u002D        minus\n−        \\[mi]          u2212        special variant of minus + *\n∓        \\[-+]          u2213        minus-plus\n±        \\[+-]          u00B1        plus-minus + *\n±        \\[t+-]         u00B1        text variant of \\[+-]\n⋅        \\[md]          u22C5        multiplication dot\n×        \\[mu]          u00D7        multiplication sign + *\n×        \\[tmu]         u00D7        text variant of \\[mu]\n⊗        \\[c*]          u2297        circled times\n⊕        \\[c+]          u2295        circled plus\n÷        \\[di]          u00F7        division sign + *\n÷        \\[tdi]         u00F7        text variant of \\[di]\n⁄        \\[f/]          u2044        fraction slash\n*        *              u002A        asterisk\n∗        \\[]          u2217        mathematical asterisk +\n\n≤        \\[<=]          u2264        less than or equal to +\n≥        \\[>=]          u2265        greater than or equal to +\n≪        \\[<<]          u226A        much less than\n≫        \\[>>]          u226B        much greater than\n=        =              u003D        equals\n=        \\[eq]          u003D        special variant of equals + *\n≠        \\[!=]          u003D0338   not equals +\n≡        \\[==]          u2261        equivalent +\n≢        \\[ne]          u22610338   not equivalent\n≅        \\[=~]          u2245        approximately equal to\n≃        \\[|=]          u2243        asymptotically equal to +\n~        \\[ti]          u007E        tilde +\n∼        \\[ap]          u223C        similar to, tilde operator +\n≈        \\[~~]          u2248        almost equal to\n≈        \\[~=]          u2248        almost equal to\n∝        \\[pt]          u221D        proportional to +\n\n∅        \\[es]          u2205        empty set +\n∈        \\[mo]          u2208        element of a set +\n∉        \\[nm]          u22080338   not element of set\n⊂        \\[sb]          u2282        proper subset +\n⊄        \\[nb]          u22820338   not subset\n⊃        \\[sp]          u2283        proper superset +\n⊅        \\[nc]          u22830338   not superset\n⊆        \\[ib]          u2286        subset or equal +\n⊇        \\[ip]          u2287        superset or equal +\n∩        \\[ca]          u2229        intersection, cap +\n∪        \\[cu]          u222A        union, cup +\n\n∠        \\[/]          u2220        angle\n⊥        \\[pp]          u22A5        perpendicular\n∫        \\[is]          u222B        integral +\n∫        \\[integral]    u222B        integral *\n∑        \\[sum]         u2211        summation *\n∏        \\[product]     u220F        product *\n∐        \\[coproduct]   u2210        coproduct *\n∇        \\[gr]          u2207        gradient +\n√        \\[sr]          u221A        radical sign, square root +\n‾        \\[rn]          u203E        overline +\n‾        \\[radicalex]   ---          radical extension\n√        \\[sqrt]        u221A        radical sign, square root *\n‾        \\[sqrtex]      ---          radical extension *\n\n⌈        \\[lc]          u2308        left ceiling +\n⌉        \\[rc]          u2309        right ceiling +\n⌊        \\[lf]          u230A        left floor +\n⌋        \\[rf]          u230B        right floor +\n\n∞        \\[if]          u221E        infinity +\nℵ        \\[Ah]          u2135        aleph symbol\nƒ        \\[Fn]          u0192        lowercase f with hook, function\nℑ        \\[Im]          u2111        blackletter I, imaginary part\nℜ        \\[Re]          u211C        blackletter R, real part\n℘        \\[wp]          u2118        Weierstrass p\n∂        \\[pd]          u2202        partial differential\nℏ        \\[-h]          u210F        h bar\nℏ        \\[hbar]        u210F        h bar\n"
                },
                {
                    "name": "Greek glyphs",
                    "content": "These  glyphs  are  intended for technical use, not for typesetting Greek language text; nor‐\nmally, the uppercase letters have upright shape, and the lowercase ones are slanted.\n\nOutput   Input   Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\nΑ        \\[*A]   u0391     uppercase alpha +\nΒ        \\[*B]   u0392     uppercase beta +\nΓ        \\[*G]   u0393     uppercase gamma +\nΔ        \\[*D]   u0394     uppercase delta +\nΕ        \\[*E]   u0395     uppercase epsilon +\nΖ        \\[*Z]   u0396     uppercase zeta +\nΗ        \\[*Y]   u0397     uppercase eta +\nΘ        \\[*H]   u0398     uppercase theta +\nΙ        \\[*I]   u0399     uppercase iota +\nΚ        \\[*K]   u039A     uppercase kappa +\nΛ        \\[*L]   u039B     uppercase lambda +\nΜ        \\[*M]   u039C     uppercase mu +\nΝ        \\[*N]   u039D     uppercase nu +\nΞ        \\[*C]   u039E     uppercase xi +\nΟ        \\[*O]   u039F     uppercase omicron +\nΠ        \\[*P]   u03A0     uppercase pi +\nΡ        \\[*R]   u03A1     uppercase rho +\nΣ        \\[*S]   u03A3     uppercase sigma +\nΤ        \\[*T]   u03A4     uppercase tau +\nΥ        \\[*U]   u03A5     uppercase upsilon +\nΦ        \\[*F]   u03A6     uppercase phi +\nΧ        \\[*X]   u03A7     uppercase chi +\nΨ        \\[*Q]   u03A8     uppercase psi +\nΩ        \\[*W]   u03A9     uppercase omega +\n\nα        \\[*a]   u03B1     lowercase alpha +\nβ        \\[*b]   u03B2     lowercase beta +\nγ        \\[*g]   u03B3     lowercase gamma +\nδ        \\[*d]   u03B4     lowercase delta +\nε        \\[*e]   u03B5     lowercase epsilon +\nζ        \\[*z]   u03B6     lowercase zeta +\nη        \\[*y]   u03B7     lowercase eta +\nθ        \\[*h]   u03B8     lowercase theta +\nι        \\[*i]   u03B9     lowercase iota +\nκ        \\[*k]   u03BA     lowercase kappa +\nλ        \\[*l]   u03BB     lowercase lambda +\nμ        \\[*m]   u03BC     lowercase mu +\nν        \\[*n]   u03BD     lowercase nu +\nξ        \\[*c]   u03BE     lowercase xi +\nο        \\[*o]   u03BF     lowercase omicron +\nπ        \\[*p]   u03C0     lowercase pi +\nρ        \\[*r]   u03C1     lowercase rho +\nσ        \\[*s]   u03C3     lowercase sigma +\nτ        \\[*t]   u03C4     lowercase tau +\nυ        \\[*u]   u03C5     lowercase upsilon +\nϕ        \\[*f]   u03D5     lowercase phi +\nχ        \\[*x]   u03C7     lowercase chi +\nψ        \\[*q]   u03C8     lowercase psi +\nω        \\[*w]   u03C9     lowercase omega +\n\nϵ        \\[+e]   u03F5     variant epsilon (lunate)\nϑ        \\[+h]   u03D1     variant theta (cursive form)\nϖ        \\[+p]   u03D6     variant pi (similar to omega)\nφ        \\[+f]   u03C6     variant phi (curly shape)\nς        \\[ts]   u03C2     terminal lowercase sigma +\n"
                },
                {
                    "name": "Playing card symbols",
                    "content": "Output   Input   Unicode   Notes\n──────────────────────────────────────────────────────────────────────────────────────────────\n♣        \\[CL]   u2663     solid club suit\n♠        \\[SP]   u2660     solid spade suit\n♥        \\[HE]   u2665     solid heart suit\n♦        \\[DI]   u2666     solid diamond suit\n"
                }
            ]
        },
        "History": {
            "content": "A consideration of the typefaces originally available to AT&T  nroff  and  troff  illuminates\nmany  conventions that one might regard as idiosyncratic fifty years afterward.  (See section\n“History” of roff(7) for more context.)  The face used by the Teletype Model 37 terminals  of\nthe  Murray Hill Unix Room was based on ASCII, but assigned multiple meanings to several code\npoints, as suggested by that standard.  Decimal 34 (\") served as a dieresis accent  and  neu‐\ntral  double  quotation  mark;  decimal  39  (')  as an acute accent, apostrophe, and closing\n(right) single quotation mark; decimal 45 (-) as a hyphen and a minus sign; decimal 94 (^) as\na circumflex accent and caret; decimal 96 (`) as a grave accent  and  opening  (left)  single\nquotation  mark;  and  decimal  126 (~) as a tilde accent and (with a half-line motion) swung\ndash.  The Model 37 bore an optional extended character set offering  upright  Greek  letters\nand  several mathematical symbols; these were documented as early as the kbd(VII) man page of\nthe (First Edition) Unix Programmer's Manual.\n\nAt the time Graphic Systems delivered the C/A/T phototypesetter to AT&T, the ASCII  character\nset  was  not considered a standard basis for a glyph repertoire by traditional typographers.\nIn the stock Times roman, italic, and bold styles available, several  ASCII  characters  were\nnot present at all, nor was most of the Teletype's extended character set.  AT&T commissioned\na “special” font to ensure no loss of repertoire.\n\nA  representation of the coverage of the C/A/T's text fonts follows.  The glyph resembling an\nunderscore is a baseline rule, and that resembling a vertical line is a box rule.   In  ital‐\nics,  the  box rule was not slanted.  We also observe that the hyphen and minus sign were al‐\nready “de-unified” by the fonts provided; a decision whither to map an  input  “-”  therefore\nhad to be taken.\n\n┌─────────────────────────────────────────────────────┐\n│ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z │\n│ a b c d e f g h i j k l m n o p q r s t u v w x y z │\n│ 0 1 2 3 4 5 6 7 8 9 fi fl ffi ffl                   │\n│ ! $ % & ( ) ‘ ’ * + - . , / : ; = ? [ ] │           │\n│ • □ — ‐  ¼ ½ ¾ ° † ′ ¢ ® ©                         │\n└─────────────────────────────────────────────────────┘\n\nThe  special font supplied the missing ASCII and Teletype extended glyphs, among several oth‐\ners.  The plus, minus, and equals signs appeared in the special font despite availability  in\ntext  fonts “to insulate the appearance of equations from the choice of standard [read: text]\nfonts”—a priority since troff was turned to the task of mathematical typesetting as  soon  as\nit was developed.\n\nWe note that AT&T took the opportunity to de-unify the apostrophe/right single quotation mark\nfrom  the  acute  accent  (a choice ISO later duplicated in its 8859 series of standards).  A\nslash intended to be mirror-symmetric with the backslash was also included, as was  the  Bell\nSystem logo; we do not attempt to depict the latter.\n\n┌───────────────────────────────────────────────────────────┐\n│ α β γ δ ε ζ η θ ι κ λ μ ν ξ ο π ρ σ ς τ υ ϕ χ ψ ω         │\n│ Γ Δ Θ Λ Ξ Π Σ Υ Φ Ψ Ω                                     │\n│ \" ´ \\ ^  ` ~ / < > { } # @ + − = ∗                       │\n│ ≥ ≤ ≡ ≈ ∼ ≠ ↑ ↓ ← → × ÷ ± ∞ ∂ ∇ ¬ ∫ ∝ √ ‾ ∪ ∩ ⊂ ⊃ ⊆ ⊇ ∅ ∈ │\n│ § ‡ ☜ ☞ | ○ ⎧ ⎩ ⎫ ⎭ ⎨ ⎬ ⎪ ⌊ ⌋ ⌈ ⌉                         │\n└───────────────────────────────────────────────────────────┘\n\nOne  ASCII  character  as  rendered  by  the  Model 37 was apparently abandoned.  That device\nprinted decimal 124 (|) as a broken vertical line, like Unicode U+00A6  (¦).   No  equivalent\nwas  available on the C/A/T; the box rule \\[br], brace vertical extension \\[bv], and “or” op‐\nerator \\[or] were used as contextually appropriate.\n\nDevices supported by AT&T device-independent troff exhibited some differences  in  glyph  de‐\ntail.   For example, on the Autologic APS-5 phototypesetter, the square \\(sq became filled in\nthe Times bold face.\n",
            "subsections": []
        },
        "Files": {
            "content": "The files below are loaded automatically by the default troffrc.\n\n/usr/share/groff/1.23.0/tmac/composite.tmac\nassigns alternate mappings for identifiers after the  first  in  a  composite  special\ncharacter escape sequence.  See subsection “Accents” above.\n\n/usr/share/groff/1.23.0/tmac/fallbacks.tmac\ndefines  fallback mappings for Unicode code points such as the increment sign (U+2206)\nand upper- and lowercase Roman numerals.\n",
            "subsections": []
        },
        "Authors": {
            "content": "This document was written by James Clark, with additions by Werner Lemberg and  Bernd Warken,\nrevised to use tbl(1) by Eric S. Raymond, and largely rewritten by G. Branden Robinson.\n\nSee also\nGroff: The GNU Implementation of troff, by Trent A. Fisher and Werner Lemberg, is the primary\ngroff manual.  Section “Using Symbols” may be of particular note.  You can browse it interac‐\ntively with “info '(groff) Using Symbols'”.\n\n“An  extension  to the troff character set for Europe”, E.G. Keizer, K.J. Simonsen, J. Akker‐\nhuis; EUUG Newsletter, Volume 9, No. 2, Summer 1989\n\nThe Unicode Standard\n\n“7-bit Character Sets” by Tuomas Salste documents the  inherent  ambiguity  and  configurable\ncode points of the ASCII encoding standard.\n\n“Nroff/Troff User's Manual” by Joseph F. Ossanna, 1976, AT&T Bell Laboratories Computing Sci‐\nence  Technical  Report  No. 54, features two tables that throw light on the glyph repertoire\navailable to “typesetter roff” when it was first written.  Be careful of re-typeset  versions\nof  this  document  that  can be found on the Internet.  Some do not accurately represent the\noriginal document: several glyphs are obviously missing.  More subtly, lowercase  Greek  let‐\nters  are  rendered  upright, not slanted as they appeared in the C/A/T's special font and as\nexpected by troff users.\n\ngroffrfc1345(7) describes an alternative set of special character glyph names, which extends\nand in some cases overrides the definitions listed above.\n\ngroff(1), troff(1), groff(7)\n\ngroff 1.23.0                                31 March 2024                              groffchar(7)",
            "subsections": []
        }
    },
    "flags": [],
    "examples": [],
    "see_also": []
}