Re: [RFC] [PATCH] [parser] org-element.el: Handle block parameters

[Nicolas Goaziou <n.goaziou@gmail.com>]

Hello,

Aaron Ecay <aaronecay@gmail.com> writes:

> I have several export filters which translate special blocks into latex
> code (doing some tedious string munging in elisp, such that a simple
> latex block is not warranted; I also have the eventual goal of making
> them cross-backend, which will involve a different bit of tedious
> munging).  These filters take arguments in the #+begin_foo line.

IIRC, I already suggested a solution with Babel for this problem.
There's no need to complicate core Org syntax for such a specific case.

> I also think it would be nice for the org code following this paragraph
> to be translated to output that makes sense for each backend, with the
> quote’s author formatted nicely (on a new line preceded by a dash,
> aligned to the right margin in text/html, using the csquotes package in
> latex, etc.).  This patch would enable such a functionality.
>
> #+begin_quote Chico Marx
> Why a duck?
> #+end_quote

Well actually, this kind of syntax is confusing at best. Something like
the following could be used instead:

  #+begin_quote :author Chico Marx

Actually, there are two points to consider:

  1. Providing something like :author implies that all back-ends in core
     and contrib and the manual have to be updated accordingly.

  2. "parameters" is too vague to be useful. It needs to be parsed
     further, which means that we must define explicitly use cases and
     keywords. Thus, I don't think adding "parameters" to every block is
     a good move if we don't know beforehand how they will be used.

     Though, it is possible to extend the syntax to well-defined
     specific cases. :author may be one of them, there are certainly
     others.


Regards,

-- 
Nicolas Goaziou