From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [RFC] New "kbd" macro? Date: Fri, 15 Sep 2017 00:02:40 +0200 Message-ID: <87lglhj5vj.fsf@nicolasgoaziou.fr> References: <87377qpwc7.fsf@nicolasgoaziou.fr> <87a81xn1oh.fsf@gmx.us> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44202) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dscDc-0008Vz-S2 for emacs-orgmode@gnu.org; Thu, 14 Sep 2017 18:02:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dscDb-0007pJ-Pj for emacs-orgmode@gnu.org; Thu, 14 Sep 2017 18:02:44 -0400 Received: from relay2-d.mail.gandi.net ([2001:4b98:c:538::194]:34720) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dscDb-0007oq-J7 for emacs-orgmode@gnu.org; Thu, 14 Sep 2017 18:02:43 -0400 In-Reply-To: <87a81xn1oh.fsf@gmx.us> (rasmus@gmx.us's message of "Thu, 14 Sep 2017 10:07:26 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Rasmus Cc: emacs-orgmode@gnu.org Hello, Rasmus writes: > I am not sure where it makes sense to print in "plain" text as opposed to > code or verbatim by default. Anyway, I think it makes sense to add > specific export mechanisms for several backends, which might make it > possible to remove that argument. Plain text allows user to define its own environment. I'm not against forcing ~...~ on keybindings when no specific syntax is required. > - HTML, MD :: as Kaushal points out, please use .. This is (almost) already the case. > > - LaTeX :: it=E2=80=99s complicated, as e.g. keys needs to be translated = in a specific > way, depending on the package that is being used, e.g. "libertinekey", > "menukeys" or whatnot. We should not add new default packages IMO. We > could always support a couple of different packages, but default to > something like "\fbox{\ttfamily %s}". Adding support for other packages > reduces to mapping specific sequences, like "SPC" to something like > "\LKeySpace". > > - ODT :: it should be possible to use something like Biolinium or > Libertinus keyboard fonts if we just have an alist mapping sequences > like CTRL to the right unicode symbol (E.g. U+E173 here), but the place > in the font would probably depend on the font. So unless there=E2=80=99= s a > standard it would be risky. Since fonts aren=E2=80=99t (typically?) em= bedded in > ODT it might be better to add a new odt style that prints the words in > the mono font inside a box, i.e. the equivalent of "\fbox{\ttfamily %s}= ". For those back-ends, I think, e.g., ~M-~ is a good default. It is very close to what Texinfo can produce. The "fbox" thing seems a bit heavy. WDYT? Regards, --=20 Nicolas Goaziou