From mboxrd@z Thu Jan  1 00:00:00 1970
From: Aaron Ecay <aaronecay@gmail.com>
Subject: Re: Extending the Org syntax by a custom exporter - how to do it?
Date: Sun, 16 Mar 2014 12:05:22 -0400
Message-ID: <87bnx6ceub.fsf@gmail.com>
References: <20140315111059.00d3b8e0@aga-netbook>
	<20140315222244.5eee2361@aga-netbook> <874n2ysb30.fsf@gmail.com>
	<20140316121832.2bc543c1@aga-netbook> <87zjkqqrsy.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48523)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <aaronecay@gmail.com>) id 1WPDZ6-0000Y4-QS
	for emacs-orgmode@gnu.org; Sun, 16 Mar 2014 12:05:38 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <aaronecay@gmail.com>) id 1WPDZ0-0002fp-1Q
	for emacs-orgmode@gnu.org; Sun, 16 Mar 2014 12:05:32 -0400
Received: from mail-qa0-x231.google.com ([2607:f8b0:400d:c00::231]:62963)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <aaronecay@gmail.com>) id 1WPDYz-0002fh-TF
	for emacs-orgmode@gnu.org; Sun, 16 Mar 2014 12:05:25 -0400
Received: by mail-qa0-f49.google.com with SMTP id j7so4366533qaq.36
	for <emacs-orgmode@gnu.org>; Sun, 16 Mar 2014 09:05:25 -0700 (PDT)
In-Reply-To: <87zjkqqrsy.fsf@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: Nicolas Goaziou <n.goaziou@gmail.com>, Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: Org-mode mailing list <emacs-orgmode@gnu.org>

Hi Marcin and Nicolas,

2014ko martxoak 16an, Nicolas Goaziou-ek idatzi zuen:
>
> Marcin Borkowski <mbork@wmi.amu.edu.pl> writes:
>
>> I thought about it.  But, as I said, I'm going to have two backends,
>> one for LaTeX, one for HTML.  WOuld it be possible to have e.g.
>>
>> #+ATTR_TEST
>>
>> working for both?
>
> Of course. You decide, at the backend level, what attributes are read.
> For example, "ox-beamer.el" reads both "ATTR_LATEX" and "ATTR_BEAMER",
> when it makes sense.
>
>> (Anyway, options after #+BEGIN_MYBLOCK would be a bit nicer, since the
>> user would not have to type /that/ much.)
>
> This is backend specific data. It would not be nice to hide that fact.

I haven=E2=80=99t followed the thread closely, but it sounds like Marcin ma=
y be
considering both LaTeX and HTML output, which makes this not exactly
specific to a single backend.

>
> Options on the same line as the block opening string should be reserved
> for backend agnostic data. There is none for special blocks at the
> moment.

There is indeed no support for options on the #+begin_foo line.  But
special blocks, and indeed any other element, can take a #+header: line.
It can fulfill the same functions as an #+attr_foo: line, but is seen by
all backends.

HTH,

--
Aaron Ecay