LATEX2MAN(1)

📦

version 77377 · 4 versions

77377 · centos-stream 10, centos-stream 9, fedora 43, fedora 44, opensuse-leap 16.0 (latest)
2026.1 · arch rolling
2026.20260711 · ubuntu resolute, ubuntu stonking
2024.20250309 · debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing

, in centos-stream 10, centos-stream 9, fedora 43, fedora 44, opensuse-leap 16.0

🌸 hey bestie, it's `latex2man` time 🌸

okay so this little legend lives in the Documentation Tools corner of your terminal, and it's literally the tool that turns your LaTeX-flavoured man pages into actual man pages. welcome to the group chat 💅

✨ NAME ✨

latex2man is a tool that translates UNIX manual pages written with LaTeX into a format that the UNIX man(1) command actually understands. Alternatively, HTML, TexInfo, or LaTeX code can be produced too. You can also suppress chunks of the output using the conditional text feature — and for that, LaTeX generation is the one you want 🎀

🦋 SYNOPSIS 🦋

latex2man [-ttransfile] [-cCSSfile] [-HMTL] [-h] [-V] [-Cname] [-achar]
infile outfile

💖 DESCRIPTION 💖

latex2man reads the file infile and writes outfile. The input has to be a LaTeX document using the latex2man LaTeX package. Then latex2man translates that document into the troff(1) format using the -man macro package. slay 💅

With the -H option, HTML code gets produced instead of troff(1). And with that option you can optionally hand it a CSSfile as an argument. CSS (Cascading Style Sheets) is how you control how the resulting HTML page looks, and you'll find the names of the CSS classes that get baked into the HTML tags as attributes down below 👀

With the -T option, TexInfo code gets produced instead of troff(1).

With the -M option, troff(1) input gets produced.

With the -L option, LaTeX output gets produced instead of troff(1).

⭐ OPTIONS ⭐

-ttransfile — the translation for user defined LaTeX macros.
-cCSSfile — if you're using the -H you can also point it at a file that contains CSS style sheets. The link to that CSS file gets inserted into the generated HTML output using the CSSfile filename you specified. cute, right? 🎀
-M — produce output suitable for the man(1) command. this is the default, bestie, it's the main character 👑
-H — instead of producing output suitable for the man(1) command, HTML code gets produced (yes, despite the name of the command, we contain multitudes 💀).
-T — instead of producing output suitable for the man(1) command, TexInfo code gets produced (again, despite the name of the command). The generated .texi-file may be processed with makeinfo(1) (to produce an .info-file) which in turn may be installed using install-info(1). The Info tags @dircategory and @direntry are provided. iykyk 📚
-L — the LaTeX source is written to the outfile. This is useful in conjunction with the -Cname option.
-Cname — output the conditional text for name. If you want more than one name, use quotes: -C'name1 name2 ...'

The following names are defined automatically:

-H defines HTML
-T defines TEXI
-M defines MAN
-L defines LATEX

-achar — this one is used only in conjunction with -T. Here's the background lore 🧚: TexInfo ignores all blanks before the first word on a new line. In order to produce some additional space before that word (using \SP) some character has to be printed before the additional space. By default this is a . (dot). The char specifies an alternative for that first character. Giving a blank to -a suppresses the indentation of a line.

Note: only for the first \SP of a series that char is printed.

-h — show a help text.
-V — show version information.

🎀 FILES 🎀

latex2man.tex — the LaTeX file containing this Man-page.
latex2man.inc — a file read with \input{..} .
latex2man.sty — the LaTeX package defining the environments and commands.
latex2man.cfg — the configuration file for the latex2man LaTeX-package.
latex2man.css — file containing example CSS definitions.
latex2man.trans — file containing example translations of user defined LaTeX macros.
fancyheadings.sty — a LaTeX package used to typeset head- and foot lines.
fancyhdr.sty — a LaTeX package used to typeset head- and foot lines.
rcsinfo.sty — a LaTeX package used to extract and use RCS version control information in LaTeX documents.
latex2man.pdf — the PDF version of this document. 📄

👀 SEE ALSO 👀

LaTeX, TexInfo, troff(1), groff(1), makeinfo(1).

💅 LaTeX COMMANDS 💅

The LaTeX package latex2man is what you use to write your Man-pages with LaTeX. But since we're translating into other text formats too, not all LaTeX stuff can be translated — fair warning, bestie 🫶

🌈 PACKAGE OPTIONS 🌈

The latex2man package accepts the following options:

fancy — use the LaTeX package fancyheadings.
fancyhdr — use the LaTeX package fancyhdr.
nofancy — neither the LaTeX package fancyheadings nor fancyhdr are used.

The default option may be specified in the file latex2man.cfg.

🦋 PACKAGE SPECIFIC ENVIRONMENTS 🦋

The following environments are provided by the package:

\begin{Name}{chapter}{name}{author}{info}{title} — the Name environment takes five arguments:
1. the Man-page chapter,
2. the name of the Man-page,
3. the author,
4. some short info about the tool printed in the footline of the Man-page, and
5. a title text which is used as title, for HTML and LaTeX (it's ignored for output of the Man-page or TeXinfo).

The Name environment must be the first environment in the document. Processing starts with this environment. Any text before this is ignored (exception: the setVersion and setDate commands).

Note: all arguments of \begin{Name} must be written on one line.

\begin{Table}[width]{columns} — the Table environment takes two arguments: the first optional one specifies a width of the last column, the second one gives the number of columns. For example:

\begin{Table}[2cm]{3}
Here & am & I \\\hline
A 1 & A 2 & A 3 1 2 3 4 5 A 3 1 2 3 4 5 \\
B 1 & B 2 & B 3 \\
\end{Table}

will be typeset as:

Here   am    I
──────────────────────
A 1    A 2   A 3 1 2
              3 4 5 A
              3 1 2 3
              4 5
B 1    B 2   B 3

If no optional width argument is given, all entries are typeset left justified. The width is a length measured absolutely in cm. Processing with LaTeX a p{width} column is typeset as last column. The translation to troff(1) commands results in a lw(width) column specification. Translating to HTML and TexInfo ignores the width parameter.

\hline may be used.

If the Man-page is formatted with troff(1) and tables are used, the tbl(1) preprocessor should be called, usually by giving a -t to the call of troff(1). When viewing the generated manual page using man(1), tbl(1) is called automatically.

\begin{Description} — is the same as \begin{description}
\begin{Description}[label] — is similar to \begin{description}, but the item labels have at minimum the size of the (optional) word label. The difference is visible only in the DVI and PDF-output, not in the troff, TexInfo or HTML output.

a      |a \begin{description}

ab     |ab

abc    |abc

a      |a \begin{Description}

ab     |ab

abc    |abc

a      |a \begin{Description}[aa]

ab     |ab

abc    |abc

💖 ACCEPTED LaTeX ENVIRONMENTS 💖

The following environments are accepted:

description
enumerate
itemize
verbatim
center

They may be nested:

Itemize and nested center:

                              A centered line.
                           Another centered line.

Another item an nested enumerate
1. a
2. b

⭐ PACKAGE SPECIFIC MACROS ⭐

The following commands are provided:

\Opt{option} — Option: \Opt{-o} will be typeset as -o.
\Arg{argument} — Argument: \Arg{filename} will be typeset as filename.
\OptArg{option}{argument} — Option with Argument: \OptArg{-o}{filename} will be typeset as -ofilename.
\OptoArg{option}{argument} — Option with optional Argument: \OptoArg{-o}{filename} will be typeset as -o[filename].
\oOpt{option} — Optional option, e.g. \oOpt{-o} will be typeset as [-o].
\oArg{argument} — Optional argument, e.g. \oArg{filename} will be typeset as [filename].
\oOptArg{option}{argument} — Optional option with argument, e.g. \oOptArg{-o}{filename} will be typeset as [-ofilename].
\oOptoArg{option}{argument} — Optional option with optional argument, e.g. \oOptoArg{-o}{filename} will be typeset as [-o[filename]].
\File{filename} — used to typeset filenames, e.g. \File{filename} will be typeset as filename.
\Prog{prog} — used to typeset program names, e.g. \Prog{latex2man} will be typeset as latex2man.
\Cmd{command}{chapter} — used to typeset references to other commands, e.g. \Cmd{latex2man}{1} will be typeset as latex2man(1).
\Bar — is typeset as |.
\Bs — (BackSlash) is typeset as \.
\Tilde — is typeset as a ~.
\Dots — is typeset as ....
\Bullet — is typeset as *.
\setVersion{..} — set .. as version information.
\setVersionWord{..} — set .. for the word Version: in the footline. The default is \setVersionWord{Version:}.
\Version — returns the version information.
\setDate{..} — sets .. as date information.
\Date — returns the date information.
\Email{..} — use to mark an Email address: \Email{Juergen.Vollmer@informatik-vollmer.de} is typeset as: Juergen.Vollmer@informatik-vollmer.de.
\URL{..} — use to mark an URL: \URL{http://www.foo.de/\Tilde vollmer} is typeset as http://www.foo.de/~vollmer.
\LatexManEnd — the input file is read and processed until reading end-of-file or \LatexManEnd (at the beginning of a line). LaTeX ignores this command.
\Lbr, \Rbr — is typeset as [ and ] (these variants are needed only sometimes like in \item[FooBar\LBr xx \Lbr]. Usually [ ] will work.)
\LBr, \RBr — is typeset as { and } (these variants are needed when using { or } as arguments to macros).
\Circum — is typeset as ^.
\Percent — is typeset as %.
\TEXbr — If processed with LaTeX causes a linebreak (i.e. is equivalent to \\). In the output of latex2man this macro is ignored.
\TEXIbr — If TexInfo output is generated, causes a linebreak (i.e. is equivalent to \\), otherwise ignored.
\MANbr — If Man-Page output is generated, causes a linebreak (i.e. is equivalent to \\), otherwise ignored.
\HTMLbr — if you're generating HTML output, this drops a linebreak (aka it's literally the same as \\) — but if you're not doing HTML, it just ✨ does nothing ✨ and gets ignored.
\medskip — gives you one empty line, that's it, that's the whole vibe.
\SP — adds some extra space, and it also works at the beginning of lines (which is lowkey the whole point). If the code on the second line looks like this:

\SP abc \SP\SP xx\\

then you get:

abc    xx
 abc   xx
  abc  xx

heads up bestie: because of some "problems" with TexInfo, lines that start with \SP get a leading . (dot) in the TexInfo output — peep -achar if you wanna know more 👀

🧚 ACCEPTED MACROS FROM THE RCSINFO PACKAGE 🧚

\rcsInfo $Id ...$ — if the LaTeX package rcsinfo is in play, this command is what pulls out the date of the Man-page.
\rcsInfoLongDate — again, if the LaTeX package rcsinfo is used, this one typesets the date that's coded inside the $Id ..$ string.

👑 ACCEPTED LaTeX MACROS 👑

okay so these are the standard LaTeX commands that get accepted, no cap:

\section{..} — takes exactly one argument: the name of the Man-page section. Every Man-page is made up of several sections. Usually you've got these sections in a Man-page: Name (which gets special handling as an environment, c.f. above), Synopsis, Description, Options, Files, See Also, Diagnostics, Return Values, Bugs, Author, version, etc.

Synopsis has to be the first section after the Name environment. periodt.

Note: do not use LaTeX-macros in section names, fr fr.

\subsection{..} — works just as well as
\subsubsection{..} — those ones. 💅
\emph{..} — \emph{example} gets typeset as example.
\textbf{..} — \textbf{example} gets typeset as example.
\texttt{..} — \texttt{example} gets typeset as example.
\underline{..} — \underline{example} gets typeset as an example of underline.
\date{..} — uses .. as the date.
\verb+..+ — but only + is allowed as the delimiter, no other options bestie.
$<$ — gets typeset as <.
$>$ — gets typeset as >.
$<=$ — gets typeset as <=.
$>=$ — gets typeset as >=.
$=$ — gets typeset as =.
$<>$ — gets typeset as <>.
$\ge$ — gets typeset as $>=$ .
$\le$ — gets typeset as $<=$ .
$\leftarrow$ — gets typeset as $<--$ .
$\Leftarrow$ — gets typeset as $<==$ .
$\rightarrow$ — gets typeset as $-->$ .
$\Rightarrow$ — gets typeset as $==>$ .
\{ — gets typeset as {.
\} — gets typeset as }.
\$ — gets typeset as $.
\$ — gets typeset as $, and this version should be used inside macro arguments.
\_ — gets typeset as _.
\& — gets typeset as &.
\# — gets typeset as #.
\% — gets typeset as %.
\, — gets typeset as a smaller blank - - (it's between the two -).
\- — used to mark hyphenation inside a word.
\\ — gets typeset as a linebreak, or it marks the end of a column in the Table environment.
\ (a \ followed by a blank) — gets typeset as a blank, BUT it can't be used at the beginning of a line to make indentation (go see the \SP command instead).
~ — gets typeset as a blank.
\copyright — gets typeset as (C).
\noindent
\hline — used inside a Table environment.
\item — used inside an itemize, enumerate, or description environment.
\today — 25 November 2018 (also check out the rcsinfo LaTeX package).
\ss,\"a, ... — so \ss = ß, \"a = ä, \"o = ö, \"u = ü, \"A = Ä, \"O = Ö, \"U = Ü. You're allowed to surround these macros in { and } in literally all places, even inside other macros, like:

\textbf{\"a\"o\"u\"A\"O\"U\ss}
\textbf{\"a}{\"o}{\"u}{\"A}{\"O}{\"U}{\ss}}
\textbf{äöüÄÖÜß}

äöüÄÖÜß äöüÄÖÜß äöüÄÖÜß

If those letters show up in their LATIN-1 8-bit coding, they get translated into the equivalent letter of whatever output format you want. Like for example ä becomes Ä in HTML and @"A in texinfo. slay ✨

\input{..} — read and process the given filename.

Please note bestie: the name of the LaTeX-macros and its arguments have to be contained in one line. Don't be splitting them up 🙈

🌈 CONDITIONAL TEXT 🌈

latex2man preprocesses the LaTeX input so you can use text conditionally — it's giving choose-your-own-adventure. A special sort of LaTeX comment is used for this.

%@% IF condition %@%
%@% ELSE %@%
%@% END-IF %@%

A line has to contain only such a comment and nothing else. condition is a boolean expression containing "names" and operators. The names you gave with the -Cname option have the value "true", while every other name occuring in the expression is assumed to be "false". If evaluating the boolean expression comes out as "true", the text in the "then"-part is used and the text in the optional "else"-part gets skipped (and vice versa, obviously 💅). The IF/ELSE/END-IF can be nested. As boolean operators, these are allowed:

( and ) for grouping are allowed.

For example:

%@% IF abc %@%
abc set
%@%  IF xyz %@%
xyz set
%@%  ELSE %@%
xyz NOT set
%@%  END-IF %@%
%@% ELSE %@%
abc NOT set
%@%  IF xyz || !XYZ %@%
xyz OR !XYZ set
%@%  ELSE %@%
xyz OR !XYZ NOT set
%@%  END-IF %@%
%@% END-IF %@%

Run this manual page through latex2man with e.g. -C'abc XYZ' and take a lil look at the generated output. (If you simply run the LaTeX-document through LaTeX, all lines are shown in the .dvi file).

abc NOT set
xyz OR !XYZ set

To check the conditional text feature, when latex2man is called with

-CHTML — the lines 1a, 2b, 3b, and 4b;
-CTEXI — the lines 1b, 2a, 3b, and 4b;
-CMAN — the lines 1b, 2b, 3a, and 4b;
-CLATEX — the lines 1b, 2b, 3b, and 4a;
calling LaTeX without preprocessing — all lines

should be shown:

1b. The HTML conditional was not set.
2b. The TEXI conditional was not set.
3a. This text occurs only when viewing the MAN output
4b. The LATEX conditional was not set.

🎀 TRANSLATION OF USER DEFINED MACROS 🎀

The user macro translation file (the one given by the [-ttransfile]) contains Perl commands that specify the translation of LaTeX macros defined by the user. These macros may have none, one or two arguments. The following code is expected:

Comments start with a # up to the end of the line.
For a macro \foo with no arguments, the following code must be specified:

Translation to Man-Pages

$manMacro{'foo'} = '...';

Translation to HTML

$htmlMacro{'foo'} = '...';

Translation to TexInfo

$texiMacro{'foo'} = '...';

where ... is the translation.

For a macro \foo{..} with one argument, the following code must be specified:

Translation to Man-Pages

$manMacro1a{'foo'} = '...';
$manMacro1b{'foo'} = '...';

Translation to HTML

$htmlMacro1a{'foo'} = '...';
$htmlMacro1b{'foo'} = '...';

Translation to TexInfo

$texiMacro1a{'foo'} = '...';
$texiMacro1b{'foo'} = '...';

where ... is the translation. The 1a code is used before the argument, while 1b is typeset after the argument is set.

For a macro \foo{..}{..} with two arguments, the following code must be specified:

Translation to Man-Pages

$manMacro2a{'foo'} = '...';
$manMacro2b{'foo'} = '...';
$manMacro2c{'foo'} = '...';

Translation to HTML

$htmlMacro2a{'foo'} = '...';
$htmlMacro2b{'foo'} = '...';
$htmlMacro2c{'foo'} = '...';

Translation to TexInfo

$texiMacro2a{'foo'} = '...';
$texiMacro2b{'foo'} = '...';
$texiMacro2c{'foo'} = '...';

where ... is the translation. The 2a code is used before the first argument, 2b between the two arguments and 2c is typeset after the second argument is set.

The file latex2man.trans contains some example code.

🦋 VERBATIM ENVIRONMENT 🦋

This
    {is}
        \texttt{a}
                  $test$
                         _of_
verbatim
<this is no HTML tag> and no @* TexInfo command

💜 SUBSECTION WORKS 💜

This is a \subsection.

🌸 Subsubsection works 🌸

This is a \subsubsection.

⭐ Subsubsection still works ⭐

This is another \subsubsection.

🔥 GENERAL REMARKS 🔥

Empty lines are typeset as paragraph separators.
The arguments of the LaTeX commands must not be split over several lines.
Do not nest calls to macros.
Except the mentioned environment and macros, the usage of other LaTeX environments or macros are not translated. Their usage will cause garbage in the output. 💀
latex2man requires Perl version >= 5.0004_03.
If you want to install the system with the distributed Makefile, you need GNU-make. If you don't have it, you should execute the steps shown in the Makefile manually.

🎀 CSS CLASSNAMES 🎀

Okay so here's the tea, bestie: when latex2man makes HTML, it sprinkles CSS class names onto the tags as attributes. That means you can go absolutely feral in your CSS file and style every single one of these classes however your little heart desires. 💅 Here's the full roster:

body (no class name, it's just the body tag) — the body of the HTML page
h1 → class titlehead — the title at the top of the HTML page specified as an argument to the Name environment
h4 → class authorhead — the author at the top of the HTML page specified as an argument to the Name environment
h4 → class datehead — the date at the top of the HTML page
h4 → class versionhead — the man page version at the top of the HTML page specified as an argument to the setVersion macro
h2 → class sectionname — a section title specified as an argument to the section macro
h4 → class subsectionname — a subsection title specified as an argument to the subsection macro
h5 → class subsubsectionname — a subsubsection title specified as an argument to the subsubsection macro
font → class progname — a program name specified as an argument to the Prog macro
font → class filename — a file name specified as an argument to the File macro
font → class commandname — a command name specified as an argument to the Cmd macro
font → class textstyle — all text that is not an argument to some LaTeX or latex2man macro
font → class optstyle — a name of an option specified as an argument to the Opt, oOpt, OptArg, oOptArg or oOptoArg macros
font → class argstyle — a name of an argument specified as an argument to the Arg, oArg, OptArg, oOptArg or oOptoArg macros
a, font → class urlstyle — a URL specified as an argument to the URL macro
a, font → class urlstyle.link — subclass of urlstyle class
a, font → class urlstyle.visited — subclass of urlstyle class
a, font → class urlstyle.hover — subclass of urlstyle class
a, font → class emailstyle — an email specified as an argument to the Email macro
a, font → class emailstyle.link — subclass of emailstyle class
a, font → class emailstyle.visited — subclass of emailstyle class
a, font → class emailstyle.hover — subclass of emailstyle class
table → class tablestyle — a table specified as a Table environment
tr → class rowstyle — a row of a table specified as a Table environment
td → class cellstyle — a cell of a table specified as a Table environment

🐛 SOME BUG FIX TESTS 🐛

Not me showing you the receipts, but the receipts are giving. 💀

Leading `.` and `'`

So like, leading . and ' in generation troff output should work propperly now, since a \& is added. Therfore the \Dot macro has been deleted. (Yes the typos are canon, bestie, we don't fix those.)

Big thanks to Frank.Schilder@Mathematik.Tu-Ilmenau.De for this one. 🫶

Testcases, as-is:

Testcase 1:

'\n'   ...

Testcase 2:
.foobar Testcase 3:
...

abc ...  abc . efg ' 123

`%` in verbatim

A % in a \verb and verbatim-environment was not emitted correctly. Thank you to Aleksey Nogin nogin@cs.caltech.edu for the bug report and the bug fix — king behaviour, honestly. 👑

% abc

   % abc %

but ignore comments following this:

💖 REQUIREMENTS 💖

Perl — latex2man requires Perl version >= 5.0004_03.
Make — if you want to install the system with the distributed Makefile, you need GNU-make. If you don't have it, you should execute the steps shown in the Makefile manually. (Lowkey annoying but we cope. 😭)
LaTeX — LaTeX2e is required.

📝 CHANGES 📝

Please check the file latex2man-CHANGES for the list of changes and acknowledgment to people contributing bugfixes or enhancements. Give the contributors their flowers, they earned them. 🌸

✨ VERSION ✨

Version: 1.29 of 2018/11/25.

👑 LICENSE AND COPYRIGHT 👑

Copyright

The most recent version of Latex2man may be found on my homepage http://www.informatik-vollmer.de/software/latex2man.html.

License

This program can be redistributed and/or modified under the terms of the LaTeX Project Public License Distributed from CTAN archives in directory macros/latex/base/lppl.txt; either version 1 of the License, or any later version.

Misc

If you find this software useful, please send me a postcard from the place where you are living. 🏻 (No, seriously — actual postcard. Iconic request, honestly.)

🦋 AUTHOR 🦋

Dr. Jürgen Vollmer Am Rennbuckel 21 D-76185 Karlsruhe Email: Juergen.Vollmer@informatik-vollmer.de WWW: http://www.informatik-vollmer.de.

and that's a wrap bestie!! 🌈 the whole thing came from the Documentation Tools corner of the world, dated 2018/11/25, and it's the LATEX2MAN(1) page — go forth and write your man pages in LaTeX like the main character you are 💜✨

📦 where this page comes from

centos-stream 10: texlive-latex2man 13:20240311-6.el10 · LPPL-1.3c
centos-stream 9: texlive-latex2man 9:20200406-26.el9 · LPPL
fedora 43: texlive-latex2man 11:svn64477-93.fc43 · LPPL-1.3c
fedora 43: texlive-latex2man 11:svn64477-95.fc43.1 · LPPL-1.3c
fedora 44: texlive-latex2man 12:svn77377-105.fc44 · LPPL-1.3c
fedora 44: texlive-latex2man 12:svn77377-111.fc44 · LPPL-1.3c
opensuse-leap 16.0: texlive-latex2man-doc 2025.222.1.29svn64477-160000.3.1 · LPPL-1.0
💖 girlified by deepseek-ai/DeepSeek-V4.1-Flash on 2026-10-13: a language model's rewrite of the original, under its terms

LATEX2MAN(1)

🌸 hey bestie, it's latex2man time 🌸

✨ NAME ✨

🦋 SYNOPSIS 🦋

💖 DESCRIPTION 💖

⭐ OPTIONS ⭐

🎀 FILES 🎀

👀 SEE ALSO 👀

💅 LaTeX COMMANDS 💅

🌈 PACKAGE OPTIONS 🌈

🦋 PACKAGE SPECIFIC ENVIRONMENTS 🦋

💖 ACCEPTED LaTeX ENVIRONMENTS 💖

⭐ PACKAGE SPECIFIC MACROS ⭐

🧚 ACCEPTED MACROS FROM THE RCSINFO PACKAGE 🧚

👑 ACCEPTED LaTeX MACROS 👑

🌈 CONDITIONAL TEXT 🌈

🎀 TRANSLATION OF USER DEFINED MACROS 🎀

🦋 VERBATIM ENVIRONMENT 🦋

💜 SUBSECTION WORKS 💜

🌸 Subsubsection works 🌸

⭐ Subsubsection still works ⭐

🔥 GENERAL REMARKS 🔥

🎀 CSS CLASSNAMES 🎀

🐛 SOME BUG FIX TESTS 🐛

Leading . and '

% in verbatim

💖 REQUIREMENTS 💖

📝 CHANGES 📝

✨ VERSION ✨

👑 LICENSE AND COPYRIGHT 👑

Copyright

License

Misc

🦋 AUTHOR 🦋

🌸 hey bestie, it's `latex2man` time 🌸

Leading `.` and `'`

`%` in verbatim