[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Eli Zaretskii
Subject: Re: Using Org as the source format to generate org.texi
Date: Mon, 12 Mar 2018 19:32:56 +0200

> From: Nicolas Goaziou <address@hidden>
> Cc: address@hidden,  address@hidden,  address@hidden
> Date: Mon, 12 Mar 2018 17:42:16 +0100
> > As I wrote elsewhere, we need to be able to use @key without losing
> > it, at least outside @kbd.
> I may have missed the "elsewhere".

In my first message in this thread.

> Is there any difference between @address@hidden and @key{...}?

I meant @key alone (that's why above I said "outside @kbd").  What
should happen with @address@hidden is under debate, and I don't think
it's anywhere as important as supporting @key conveniently.  AFAIK,
currently Org doesn't support @key, or at least all of its instances
in the Org's Texinfo manual were dropped when converting to Org.

> > @dfn produces slanted typeface in printed output and “quoted” string
> > in Info output.  I'd suggest that Org produces something similar.
> Slated typeface is /.../ markup in Org, which becomes @emph{...} when
> exported to Texinfo. I'm suggesting to use _..._ markup because it is
> free and fall-backs somewhat gracefully when exported to something else
> than Texinfo.

It's up to you, but IMO underlining is not really appropriate.  New
terminology should stand out like it does in other typesetting
systems, and slanted typeface does a good job in this case.

> Org -> LaTeX and Org -> Texinfo -> LaTeX are going to produce different
> results and there is little hope they can converge at some point.
> I suggest to not bother too much about this.

That's not what bothers me.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]