Umm, sorry,
I just found out, I was talking about the other generic exporter :(
Robert
On 11/29/2011 07:15 AM, Robert Klein wrote:
On 11/25/2011 06:32 PM, Nicolas Goaziou wrote:
Hello,
I've pushed org-export.el to contrib. It's a general export engine,
built on top of org-elements aiming at
On 11/25/2011 06:32 PM, Nicolas Goaziou wrote:
Hello,
I've pushed org-export.el to contrib. It's a general export engine,
built on top of org-elements aiming at simplifying life of both
developers and maintainers (and, therefore, of end-users).
Hi Nicolas,
I'd like to make same remarks regar
Carsten Dominik writes:
9. Table.el tables will always use their own export back-end. In other
words, no Org syntax will be recognized in such table anymore.
A table.el is an extraneous element while the parser is meant to
parse Org syntax.
>>
>>> Maybe we should see if t
On Nov 27, 2011, at 8:54 PM, Nicolas Goaziou wrote:
> Hello,
>
> Carsten Dominik writes:
>
>>> 2. The document title cannot be obtained anymore from the first line of
>>> text. It's either explicitely defined with the =TITLE= keyword, or
>>> derived from buffer's name.
>>
>> This is actual
Hello,
Carsten Dominik writes:
>> 2. The document title cannot be obtained anymore from the first line of
>> text. It's either explicitely defined with the =TITLE= keyword, or
>> derived from buffer's name.
>
> This is actually good, I think. Much of the stuff like initial text,
> title fr
Hi Nicolas,
a few comments:
On 25.11.2011, at 19:57, Nicolas Goaziou wrote:
>
> Completing myself, I'll add a few notes about the differences between
> the current exporter and this one. While it tries to mimic most of the
> behaviours of its ancestor, some points just couldn't fit in the new
>
Hi everyone,
is there anyone who is planning to implement a texinfo
exporter based on org-elements? If not, I would write
this exporter...
- Carsten
On 25.11.2011, at 18:32, Nicolas Goaziou wrote:
> Hello,
>
> I've pushed org-export.el to contrib. It's a general export engine,
> built on top
Completing myself, I'll add a few notes about the differences between
the current exporter and this one. While it tries to mimic most of the
behaviours of its ancestor, some points just couldn't fit in the new
scheme, would it be for a technical reason or by design.
Here follows a rough list stat
Hello,
I've pushed org-export.el to contrib. It's a general export engine,
built on top of org-elements aiming at simplifying life of both
developers and maintainers (and, therefore, of end-users).
It predates org-exp.el and org-special-blocks.el. Though, keep it mind
that, as advanced as it is,
