emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins <jamshark70@qq.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Comment on Org Export Reference
Date: Sat, 07 Mar 2015 11:18:08 +0800	[thread overview]
Message-ID: <14bf23d69b0.278c.0bb60a3c7e492ea180363c67eb170725@qq.com> (raw)
In-Reply-To: <87twxy8j5a.fsf@nicolasgoaziou.fr>

On March 6, 2015 7:21:50 PM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:

> James Harkins <jamshark70@qq.com> 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 should implement (besides
> template).

Should, or could.

> Anyway full list of supported elements and objects, along
> with all associated properties is in "Org Element API" document[fn:1].

Ah, OK! The connection between these and the exporter was, for whatever 
reason, not obvious to me. (I may perhaps be forgiven for this: a search of 
the export reference for "API" yielded no results.)

Maybe all the document needs is to call attention to the relationship and 
give a few examples. *That* is something I can handle. A full tutorial is 
more time than I can afford now, but might not be needed after all.

hjh

Sent with AquaMail for Android
http://www.aqua-mail.com

  reply	other threads:[~2015-03-07  3:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <14bedd41838.27cd.0bb60a3c7e492ea180363c67eb170725@qq.com>
2015-03-06  8:55 ` Comment on Org Export Reference James Harkins
2015-03-06 10:30   ` Rasmus
2015-03-06 11:22   ` Nicolas Goaziou
2015-03-07  3:18     ` James Harkins [this message]
2015-03-06 13:40   ` Marcin Borkowski
2015-03-06 17:23     ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14bf23d69b0.278c.0bb60a3c7e492ea180363c67eb170725@qq.com \
    --to=jamshark70@qq.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).