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 19:32:56 +0200 Message-ID: <83h8plrygn.fsf@gnu.org> References: <878tb5axms.fsf@bzg.fr> <87371762r3.fsf@nicolasgoaziou.fr> <87zi3dcrq1.fsf@nicolasgoaziou.fr> <83po49s36j.fsf@gnu.org> <876061ckk7.fsf@nicolasgoaziou.fr> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1520876998 12111 195.159.176.226 (12 Mar 2018 17:49:58 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 12 Mar 2018 17:49:58 +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 18:49:54 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 1evRa5-00033f-Vw for ged-emacs-devel@m.gmane.org; Mon, 12 Mar 2018 18:49:54 +0100 Original-Received: from localhost ([::1]:33571 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evRc8-0000d5-IB for ged-emacs-devel@m.gmane.org; Mon, 12 Mar 2018 13:52:00 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56008) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evRJk-0001YS-OM for emacs-devel@gnu.org; Mon, 12 Mar 2018 13:33:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1evRJh-00064i-M7 for emacs-devel@gnu.org; Mon, 12 Mar 2018 13:33:00 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:34389) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evRJh-00064a-Iu; Mon, 12 Mar 2018 13:32:57 -0400 Original-Received: from [176.228.60.248] (port=2928 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1evRJa-0006Sz-Br; Mon, 12 Mar 2018 13:32:50 -0400 In-reply-to: <876061ckk7.fsf@nicolasgoaziou.fr> (message from Nicolas Goaziou on Mon, 12 Mar 2018 17:42:16 +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:223648 Archived-At: > From: Nicolas Goaziou > Cc: rms@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org > 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 @kbd{@key{...}} and @key{...}? 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. > > @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.