summaryrefslogtreecommitdiffstats
path: root/regress/roff/de/factorial.out_ascii
diff options
context:
space:
mode:
authorIngo Schwarze <schwarze@openbsd.org>2022-06-03 12:15:55 +0000
committerIngo Schwarze <schwarze@openbsd.org>2022-06-03 12:15:55 +0000
commitf1a1415f2ac83d7454ab33bab918fe77f90664bd (patch)
treecca4619f0ecb728de9a8697ed509838d8c4186bd /regress/roff/de/factorial.out_ascii
parent4de2134e6e8bcf00651ea443b38238baef53467e (diff)
downloadmandoc-f1a1415f2ac83d7454ab33bab918fe77f90664bd.tar.gz
During identifier parsing, handle undefined escape sequences
in the same way as groff: * \\ is always reduced to \ * \. is always reduced to . * other undefined escape sequences are usually reduced to the escape name, for example \G to G, except during the expansion of expanding escape sequences having the standard argument form (in particular \* and \n), in which case the backslash is preserved literally. Yes, this is confusing indeed. For example, the following have the same meaning: * .ds \. and .ds . which is not the same as .ds \\. * \*[\.] and \*[.] which is not the same as \*[\\.] * .ds \G and .ds G which is not the same as .ds \\G * \*[\G] and \*[\\G] which is not the same as \*[G] <- sic! To feel less dirty, have a leaning toothpick, if you are so inclined. This patch also slightly improves the string shown by the "escaped character not allowed in a name" error message.
Diffstat (limited to 'regress/roff/de/factorial.out_ascii')
0 files changed, 0 insertions, 0 deletions