From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: [RFC] New "kbd" macro? Date: Fri, 15 Sep 2017 13:08:57 +0000 Message-ID: References: <87377qpwc7.fsf@nicolasgoaziou.fr> <87a81xn1oh.fsf@gmx.us> <87lglhj5vj.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a114fa8a6245ee605593a19f6" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40126) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dsqMo-0007cq-3H for emacs-orgmode@gnu.org; Fri, 15 Sep 2017 09:09:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dsqMn-0007f4-5N for emacs-orgmode@gnu.org; Fri, 15 Sep 2017 09:09:10 -0400 Received: from mail-yw0-x234.google.com ([2607:f8b0:4002:c05::234]:50235) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dsqMn-0007ey-0T for emacs-orgmode@gnu.org; Fri, 15 Sep 2017 09:09:09 -0400 Received: by mail-yw0-x234.google.com with SMTP id u11so792236ywh.7 for ; Fri, 15 Sep 2017 06:09:09 -0700 (PDT) In-Reply-To: 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: Nicolas Goaziou , Rasmus Cc: emacs-org list --001a114fa8a6245ee605593a19f6 Content-Type: text/plain; charset="UTF-8" On Fri, Sep 15, 2017, 8:54 AM Kaushal Modi wrote: > On Thu, Sep 14, 2017 at 6:03 PM Nicolas Goaziou > wrote: > >> >> > - HTML, MD :: as Kaushal points out, please use .. >> >> This is (almost) already the case. >> > > Thanks. I tried the second version of the patch and it works great. About > the /almost/, the same .. export worked for MD exports too.. as > ox-md is derived from ox-html, and also as all Markdown renderers allow > inline HTML. > Makes me think.. instead of hard-codng the kbd export forms in the macro, wouldn't it be better to define those in the respective exporter backends? That way I can easily override the behavior I want using :translate-alist in my custom backend. Can a mechanism be put in place so that we can have a 'kbd' element behavior that can be defined in the :translate-alist? -- Kaushal Modi --001a114fa8a6245ee605593a19f6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Sep 15, 2017, 8:54 AM K= aushal Modi <kaushal.modi@gmai= l.com> wrote:
On Thu, Sep 14, 2017 at 6:03= PM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:

> - HTML, MD :: as Kaushal points out, please use <kbd>.</kbd&g= t;.

This is (almost) already the case.

Thanks. I tried the sec= ond version of the patch and it works great. About the /almost/, the same &= lt;kbd>..</kbd> export worked for MD exports too.. as ox-md is der= ived from ox-html, and also as all Markdown renderers allow inline HTML.

Makes me think.. inst= ead of hard-codng the kbd export forms in the macro, wouldn't it be bet= ter to define those in the respective exporter backends?

That way I can easily override the behavior I want using :translate-= alist in my custom backend.=C2=A0

Can a mechanism = be put in place so that we can have a 'kbd' element behavior that c= an be defined in the :translate-alist?
--

Kaushal Modi

--001a114fa8a6245ee605593a19f6--