From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: inconsistency in backend export functions? Date: Thu, 12 Dec 2013 09:27:54 -0500 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b33d5fcc5c68604ed57266d Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47919) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vr7FD-0002Ak-0C for emacs-orgmode@gnu.org; Thu, 12 Dec 2013 09:28:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vr7F7-0008Sh-3l for emacs-orgmode@gnu.org; Thu, 12 Dec 2013 09:28:02 -0500 Received: from mail-pb0-x233.google.com ([2607:f8b0:400e:c01::233]:36683) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vr7F6-0008Pj-QW for emacs-orgmode@gnu.org; Thu, 12 Dec 2013 09:27:57 -0500 Received: by mail-pb0-f51.google.com with SMTP id up15so600296pbc.38 for ; Thu, 12 Dec 2013 06:27:55 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "emacs-orgmode@gnu.org" --047d7b33d5fcc5c68604ed57266d Content-Type: text/plain; charset=ISO-8859-1 Hi All, 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? John ----------------------------------- John Kitchin Associate Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu --047d7b33d5fcc5c68604ed57266d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi All,

I was p= laying around with creating a new backend to convert an org-file to a json = representation, and I came across this apparent inconsistency in the backen= d function signatures.

at http://orgmode.org/worg/dev/org-export-reference.html it suggests t= he backend transcoding functions should have this signature:

(defun org-backend-xxx (element contents info)
=A0 code that conve= rts element to a string)

but, that does not work for a plain-t= ext element. Even in ox-latex.el it is defined with only two arguments, wit= h 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 m= e. Am I missing something in the docs somewhere?

John

---------------= --------------------
John Kitchin
Associate Professor
Doherty Hall= A207F
Department of Chemical Engineering
Carnegie Mellon University<= br> Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu

<= /div>
--047d7b33d5fcc5c68604ed57266d--