From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Using Org as the source format to generate org.texi Date: Mon, 12 Mar 2018 22:16:29 +0200 Message-ID: <83efkprqw2.fsf@gnu.org> References: <878tb5axms.fsf@bzg.fr> <87371762r3.fsf@nicolasgoaziou.fr> <87zi3dcrq1.fsf@nicolasgoaziou.fr> <83po49s36j.fsf@gnu.org> <876061ckk7.fsf@nicolasgoaziou.fr> <83h8plrygn.fsf@gnu.org> <87tvtlb2j4.fsf@nicolasgoaziou.fr> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1520886014 4917 195.159.176.226 (12 Mar 2018 20:20:14 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 12 Mar 2018 20:20:14 +0000 (UTC) Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca To: Nicolas Goaziou Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 12 21:20:10 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 1evTvT-00015H-UF for ged-emacs-devel@m.gmane.org; Mon, 12 Mar 2018 21:20:08 +0100 Original-Received: from localhost ([::1]:34449 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evTxW-000220-Ud for ged-emacs-devel@m.gmane.org; Mon, 12 Mar 2018 16:22:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40450) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evTs2-0006yN-HW for emacs-devel@gnu.org; Mon, 12 Mar 2018 16:16:35 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1evTry-0000q9-Fj for emacs-devel@gnu.org; Mon, 12 Mar 2018 16:16:34 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:37600) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evTry-0000q5-C6; Mon, 12 Mar 2018 16:16:30 -0400 Original-Received: from [176.228.60.248] (port=3501 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1evTrr-0001K5-5a; Mon, 12 Mar 2018 16:16:23 -0400 In-reply-to: <87tvtlb2j4.fsf@nicolasgoaziou.fr> (message from Nicolas Goaziou on Mon, 12 Mar 2018 18:57:03 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:223657 Archived-At: > From: Nicolas Goaziou > Cc: rms@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org > Date: Mon, 12 Mar 2018 18:57:03 +0100 > > {{{kbd(...)}}} is both @kbd{...} and @key{...}. It can't be both, because then you cannot distinguish between @kbd{FOO}, which means type the 3 characters F O O, and @key{FOO}, which means press the key labeled "FOO". > Anyway, it seems you did not answer to any of my questions. Sorry about that. I thought I did. Maybe what I say above clarifies the issue. > 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? Yes, something else: we need a separate {{{key(...)}}} construct, or something else that will produce @key{...} in 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. > > > > 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{...}. I wouldn't recommend having an underline in Org to be translated into something entirely different in Texinfo. This is a mental burden on the authors we'd better avoid. > In any case, let's forget about this, it was just an idea. One can still > define and use {{{dfn(...)}}} when needed. Fine with me, thanks.