On March 6, 2015 7:21:50 PM Nicolas Goaziou wrote:
James Harkins writes:
> The page covers a lot of details, but less in the way of context. For
> instance, the toolbox is documented extensively, but I didn't see
> a comprehensive list of the transcoding functions that a backend
> should impl
Marcin Borkowski writes:
> What I find especially missing is: documenting the underlying data
> structures (and overall architecture – in fact, I was thinking today
> about writing a blog post about the main entry points to the exporter,
> but this will probably have to wait a week or two), and a
On 2015-03-06, at 09:55, James Harkins wrote:
> I've been working on an export backend for personal use, and I find the
> documentation on worg to be... not quite what I need. In the spirit of
In fact, studying the sources for existing exporters seems to be the
best way to learn that stuff.
Hello,
James Harkins writes:
> The page covers a lot of details, but less in the way of context. For
> instance, the toolbox is documented extensively, but I didn't see
> a comprehensive list of the transcoding functions that a backend
> should implement
There is no rule about what a back-end s
Hi James,
James Harkins writes:
> I've been working on an export backend for personal use, and I find
> the documentation on worg to be... not quite what I need. In the
> spirit of suggesting an avenue for improvement, then:
I'm happy you found of ox and org-element useful. Nicolas' work is in
I've been working on an export backend for personal use, and I find the
documentation on worg to be... not quite what I need. In the spirit of
suggesting an avenue for improvement, then:
The page covers a lot of details, but less in the way of context. For
instance, the toolbox is documented e
