From mboxrd@z Thu Jan  1 00:00:00 1970
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Subject: Re: [Feature Request] - Furigana - Yomigana - Ruby
Date: Tue, 28 May 2013 17:01:56 +0200
Message-ID: <20130528150156.GA19186@kuru.dyndns-at-home.com>
References: <51A3E117.3000900@gmail.com>
	<CAPaq-gNKWgMPFrbuzR21TkDhs4fAbQCWpoZ4kidO3UcS=8g+qQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:34237)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <fatkasuvayu+linux@gmail.com>) id 1UhLPe-0000KD-Qo
	for emacs-orgmode@gnu.org; Tue, 28 May 2013 11:02:17 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <fatkasuvayu+linux@gmail.com>) id 1UhLPW-0005sI-BT
	for emacs-orgmode@gnu.org; Tue, 28 May 2013 11:02:10 -0400
Received: from mail-wg0-x231.google.com ([2a00:1450:400c:c00::231]:46576)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <fatkasuvayu+linux@gmail.com>) id 1UhLPW-0005s9-5T
	for emacs-orgmode@gnu.org; Tue, 28 May 2013 11:02:02 -0400
Received: by mail-wg0-f49.google.com with SMTP id y10so5341911wgg.4
	for <emacs-orgmode@gnu.org>; Tue, 28 May 2013 08:02:00 -0700 (PDT)
Received: from kuru.dyndns-at-home.com
	([2001:610:120:3000:f2de:f1ff:fe37:c76c])
	by mx.google.com with ESMTPSA id x13sm24930033wib.3.2013.05.28.08.01.58
	for <emacs-orgmode@gnu.org>
	(version=TLSv1.2 cipher=RC4-SHA bits=128/128);
	Tue, 28 May 2013 08:01:59 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <CAPaq-gNKWgMPFrbuzR21TkDhs4fAbQCWpoZ4kidO3UcS=8g+qQ@mail.gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

On Tue, May 28, 2013 at 03:00:40PM +0200, Torsten Wagner wrote:
> 
> However, I believe that for many users, the special cases are not very
> frequent and complex. Might it be possible to create a very simple syntax
> for exporting rules which could be either in those above modules or
> directly within the file written by the user themself?
> 
> #+HTML_USER_RULE   \ruby{$1}{$2}, <ruby> $1 <rp>(</rp><rt>$2</rt><rp>)</rp> <\ruby>

Isn't this very similar to a #+MACRO definition but with a different
syntax and only for the HTML backend?

Maybe we could allow backend specific macro expansion definitions.
Something like:

  #+HTML_MACRO: ruby <ruby> $1 <rp>(</rp><rt>$2</rt><rp>)</rp> <\ruby>
  #+LATEX_MACRO: ruby \ruby{$1}{$2}

  Then {{{ruby(東,ひがし)}}} will be expanded appropriately for
  different backends.

What do you think?

Cheers,

PS: Actually on second thought it is probably possible to handle this
    with filters although I failed to find the appropriate filter.

    So you could try:

      #+MACRO: ruby <cookie><$1><$2></cookie>

    And the filter can translate the cookie to the appropriate backend
    specific expansion.

-- 
Suvayu

Open source is the future. It sets us free.