From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [RFC] New "kbd" macro? Date: Fri, 15 Sep 2017 09:36:40 +0200 Message-ID: <87mv5w8lbr.fsf@gmx.us> References: <87377qpwc7.fsf@nicolasgoaziou.fr> <87a81xn1oh.fsf@gmx.us> <87lglhj5vj.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48653) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dslBF-0004s3-Pk for emacs-orgmode@gnu.org; Fri, 15 Sep 2017 03:36:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dslBB-0003H2-Fb for emacs-orgmode@gnu.org; Fri, 15 Sep 2017 03:36:53 -0400 Received: from [195.159.176.226] (port=45159 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dslBB-0003Ga-8K for emacs-orgmode@gnu.org; Fri, 15 Sep 2017 03:36:49 -0400 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dslB0-0003in-H3 for emacs-orgmode@gnu.org; Fri, 15 Sep 2017 09:36:38 +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: emacs-orgmode@gnu.org Nicolas Goaziou writes: > 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’s 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’s a >> standard it would be risky. Since fonts aren’t (typically?) embedded 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. I quite like the fbox look, but it would — perhaps – be rather heavy inline! How about making it a format-string for LaTeX and a separate style for ODT? Then you could change it on a document-basis if needed. Rasmus -- Dung makes an excellent fertilizer