Re: Using Org as the source format to generate org.texi

[Eli Zaretskii <eliz@gnu.org>]

> From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
> Date: Mon, 12 Mar 2018 15:07:34 +0100
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> 
> @var, @kbd and @key are defined, in "org-manual.org", through
> a one-liner mechanism called a macro. There, @var{foo} becomes
> {{{var(foo)}}} and @kbd{M-@key{RET}} becomes {{{kbd(M-RET)}}} (the
> "@key" part is automatically deduced from the contents of the macro).

As I wrote elsewhere, we need to be able to use @key without losing
it, at least outside @kbd.

> At one point, I suggested to make the "kbd" macro readily available for
> every export back-end. As such, the would be no need to define it in
> each document making use of it. However there was little interest in the
> Org ML. Also, there are some decisions to make. For example, the macro
> needs to be useful in every format supported by Org, and there are
> multiple ways to transcribe @kbd+@key in LaTeX parlance. It is not clear
> which one we should use and how configurable it should be.

How about using what texinfo.tex does?

> I'm not sure about @dfn. Org has a lightweight markup, i.e., _this_,
> which mean "underline" by default. Since it is ignored in the Texinfo
> export back-end, we might use it for @dfn. It probably would not be
> shocking if the term appeared as underlined in other formats.

@dfn produces slanted typeface in printed output and “quoted” string
in Info output.  I'd suggest that Org produces something similar.