From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca
Subject: Re: Using Org as the source format to generate org.texi
Date: Mon, 12 Mar 2018 18:57:03 +0100 [thread overview]
Message-ID: <87tvtlb2j4.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <83h8plrygn.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Mar 2018 19:32:56 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> I meant @key alone (that's why above I said "outside @kbd"). What
> should happen with @kbd{@key{...}} 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.
{{{kbd(...)}}} is both @kbd{...} and @key{...}.
Anyway, it seems you did not answer to any of my questions. Or I may be
misunderstanding, of course. Currently, {{{kbd(TAB)}}} is translated as
@kbd{@key{TAB}}. Would it be better if it became @key{TAB} instead? Or
is "supporting @key conveniently" something else?
> 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.
Well, it seems to be, really. _text_ underlines "text" in other export
back-ends than Texinfo. In Texinfo, it would become @dfn{...}. So, what
apparently bothers you is the "Org -> LaTeX" or "Org -> HTML" both
underline text when Texinfo makes it a definition. However _..._ is
a definition only in Texinfo. Therefore, e.g., "Org -> LaTeX" is going
to be different than "Org -> Texinfo -> LaTeX".
In any case, let's forget about this, it was just an idea. One can still
define and use {{{dfn(...)}}} when needed.
next prev parent reply other threads:[~2018-03-12 17:57 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 18:04 Using Org as the source format to generate org.texi Bastien
2018-03-06 20:20 ` Stefan Monnier
2018-03-06 20:24 ` Kaushal Modi
2018-03-06 21:54 ` Achim Gratz
2018-03-07 0:22 ` Bastien
2018-03-07 17:43 ` Eli Zaretskii
2018-03-07 17:52 ` Kaushal Modi
2018-03-08 10:04 ` Bastien Guerry
2018-03-08 7:28 ` Michael Albinus
2018-03-08 10:06 ` Bastien Guerry
2018-03-08 10:13 ` Bastien Guerry
2018-03-07 17:39 ` Glenn Morris
2018-03-07 22:57 ` Richard Stallman
2018-03-09 11:30 ` Bastien
2018-03-10 21:26 ` Nicolas Goaziou
2018-03-11 3:40 ` Eli Zaretskii
2018-03-11 14:59 ` Michael Albinus
2018-03-11 18:13 ` Nicolas Goaziou
2018-03-11 23:26 ` Richard Stallman
2018-03-12 14:07 ` Nicolas Goaziou
2018-03-12 15:51 ` Eli Zaretskii
2018-03-12 16:42 ` Nicolas Goaziou
2018-03-12 17:32 ` Eli Zaretskii
2018-03-12 17:57 ` Nicolas Goaziou [this message]
2018-03-12 20:16 ` Eli Zaretskii
2018-03-12 21:37 ` Nicolas Goaziou
2018-03-13 15:55 ` Eli Zaretskii
2018-03-13 17:24 ` Nicolas Goaziou
2018-03-13 17:43 ` Eli Zaretskii
2018-03-13 21:37 ` Nicolas Goaziou
2018-04-14 17:10 ` @key{...} mis-use (was: Using Org as the source format to generate org.texi) Nicolas Goaziou
2018-04-19 9:22 ` Eli Zaretskii
2018-03-06 21:30 ` Using Org as the source format to generate org.texi Paul Eggert
2018-03-07 0:19 ` Bastien
2018-03-07 1:08 ` Paul Eggert
2018-03-07 7:33 ` Achim Gratz
2018-03-09 17:52 ` Achim Gratz
2018-03-09 18:02 ` Paul Eggert
2018-03-09 18:23 ` Achim Gratz
2018-03-07 17:41 ` Glenn Morris
2018-03-09 11:19 ` Phillip Lord
2018-03-12 17:12 ` Glenn Morris
2018-03-09 17:39 ` Achim Gratz
2018-03-10 20:07 ` Phillip Lord
2018-03-11 3:00 ` Paul Eggert
2018-03-11 3:55 ` Stefan Monnier
2018-03-11 21:46 ` Phillip Lord
2018-03-12 21:04 ` Radon Rosborough
2018-03-13 9:10 ` Phillip Lord
2018-03-13 12:29 ` Stefan Monnier
2018-03-13 16:47 ` Phillip Lord
2018-04-14 19:15 ` Joshua Branson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvtlb2j4.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.