From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Nicolas Goaziou Newsgroups: gmane.emacs.devel Subject: Re: Using Org as the source format to generate org.texi Date: Mon, 12 Mar 2018 17:42:16 +0100 Message-ID: <876061ckk7.fsf@nicolasgoaziou.fr> References: <878tb5axms.fsf@bzg.fr> <87371762r3.fsf@nicolasgoaziou.fr> <87zi3dcrq1.fsf@nicolasgoaziou.fr> <83po49s36j.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1520872831 24018 195.159.176.226 (12 Mar 2018 16:40:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 12 Mar 2018 16:40:31 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 12 17:40:27 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1evQUs-00063k-KK for ged-emacs-devel@m.gmane.org; Mon, 12 Mar 2018 17:40:26 +0100 Original-Received: from localhost ([::1]:33151 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evQWt-0000DV-Rk for ged-emacs-devel@m.gmane.org; Mon, 12 Mar 2018 12:42:31 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41538) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evQWn-0000DD-Jb for emacs-devel@gnu.org; Mon, 12 Mar 2018 12:42:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1evQWm-0006um-Nh for emacs-devel@gnu.org; Mon, 12 Mar 2018 12:42:25 -0400 Original-Received: from relay5-d.mail.gandi.net ([217.70.183.197]:34329) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1evQWh-0006sA-Tt; Mon, 12 Mar 2018 12:42:20 -0400 X-Originating-IP: 185.131.40.67 Original-Received: from saiph (unknown [185.131.40.67]) (Authenticated sender: admin@nicolasgoaziou.fr) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id 25EE01C001A; Mon, 12 Mar 2018 17:42:17 +0100 (CET) Original-Received: from ngz by saiph with local (Exim 4.89) (envelope-from ) id 1evQWe-0000Wk-Lb; Mon, 12 Mar 2018 17:42:16 +0100 In-Reply-To: <83po49s36j.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Mar 2018 17:51:00 +0200") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 217.70.183.197 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:223644 Archived-At: Hello, Eli Zaretskii 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 =E2=80=9Cquoted=E2= =80=9D 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, --=20 Nicolas Goaziou 0x80A93738