unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 17:42:16 +0100	[thread overview]
Message-ID: <876061ckk7.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <83po49s36j.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Mar 2018 17:51:00 +0200")

Hello,

Eli Zaretskii <eliz@gnu.org> writes:

> 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".

Is there any difference between @kbd{@key{...}} and @key{...}? If so, is
there any use of the former? If any question has a negative answer, then
all is good. Org can produce the former but could has well generate the
latter in this special case.

If both have a positive answer, we can generate automatically the most
common one and let users write a macro for the other case. This
situation is probably sufficiently rare it isn't much of a problem
anyway.

>> 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?

My TeX is a bit rusty, but, AFAIU, it defines yet another way to handle
@kbd+@key. This is fine, but LaTeX also provides at least two packages
dealing with keys. I have no preference, but users may disagree about
which way is better as a default. Even if we stick with the
"texinfo.tex" way, we probably need to allow tweaking the LaTeX output
somehow.

> @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.

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.

Regards,

-- 
Nicolas Goaziou                                                0x80A93738



  reply	other threads:[~2018-03-12 16:42 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 [this message]
2018-03-12 17:32               ` Eli Zaretskii
2018-03-12 17:57                 ` Nicolas Goaziou
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=876061ckk7.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).