From: Nicolas Goaziou <n.goaziou@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: inconsistency in backend export functions?
Date: Thu, 12 Dec 2013 17:44:14 +0100 [thread overview]
Message-ID: <871u1ixbmp.fsf@gmail.com> (raw)
In-Reply-To: <CAJ51ETpJx2AyQaFoOBHynJv3-NFegvZNc6-hsEHuvCCA3xGZvA@mail.gmail.com> (John Kitchin's message of "Thu, 12 Dec 2013 09:27:54 -0500")
Hello,
John Kitchin <jkitchin@andrew.cmu.edu> writes:
> I was playing around with creating a new backend to convert an org-file to
> a json representation, and I came across this apparent inconsistency in the
> backend function signatures.
>
> at http://orgmode.org/worg/dev/org-export-reference.html it suggests the
> backend transcoding functions should have this signature:
>
> (defun org-backend-xxx (element contents info)
> code that converts element to a string)
>
> but, that does not work for a plain-text element. Even in ox-latex.el it is
> defined with only two arguments, with no contents.
>
> (defun org-latex-plain-text (text info)
>
> My exporter works when I define it this way too, but it seemed like an odd
> inconsistency to me. Am I missing something in the docs somewhere?
This is documented in `org-export-define-backend' docstring.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-12-12 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 14:27 inconsistency in backend export functions? John Kitchin
2013-12-12 16:44 ` Nicolas Goaziou [this message]
2013-12-12 17:01 ` John Kitchin
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=871u1ixbmp.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).