From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Standardize #+BIBLIOGRAPHY line Date: Mon, 22 Jul 2013 12:55:25 +0530 Message-ID: <87k3kjyr37.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43259) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1Ant-0004Mg-Ng for emacs-orgmode@gnu.org; Mon, 22 Jul 2013 03:45:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V1Anq-00038b-Rq for emacs-orgmode@gnu.org; Mon, 22 Jul 2013 03:45:09 -0400 Received: from mail-pb0-x230.google.com ([2607:f8b0:400e:c01::230]:36252) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1Anq-00038D-Lg for emacs-orgmode@gnu.org; Mon, 22 Jul 2013 03:45:06 -0400 Received: by mail-pb0-f48.google.com with SMTP id ma3so6684229pbc.7 for ; Mon, 22 Jul 2013 00:45:05 -0700 (PDT) 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org (Fixed up the subject and CC line.) As for #+ATTR_BACKEND lines, they *must* be prefixed with the citation processor's name. It is unlikely that there will be a convergence of what Org-wide ':citation-style' values are. In that case, they can be converted to citation-processor specific style. #+ATTR_LATEX: :bib-style plain #+ATTR_HTML: :bib2html-style apa #+ATTR_ODT: :jabref-style chicago-author-date ---------------------------------------------------------------- In ODT case, I translate (latex-frag ...) to (citation-reference ....) I have the following defcustom to choose JabRef as the "citation processor" for ODT backend. If we standardize on this convention, one can for example choose JabRef or Zotero as the citation processor for various backends. (defcustom org-odt-citation-transcoders '(ox-jabref-citation-reference . ox-jabref-bibliography) "Transcoders to handle citations." :type '(choice (const :tag "Don't process citations" nil) (cons :tag "Citation transcoders" (function :tag "For \\cite{} fragments" :value ox-jabref-citation-reference) (function :tag "For BIBLIOGRAPHY " :value ox-jabref-bibliography))) :group 'org-export-odt :version "24.1") You *may* want to wrap this aspect in to a tool. ---------------------------------------------------------------- <- The following part is same as earlier message -> Nicolas I am finalizing JabRef support for ODT. At *some* future point in time, I will include ox-jabref.el (and all other patches) in official Emacs distribution. ---------------------------------------------------------------- Meanwhile, could you standardize the syntax for some `keyword' elements so that they can be parse with `org-export-read-attribute'. Currently, I am interested in BIBLIOGRAPHY. You may also want to do the same for #+toc: lines. #+ATTR_ODT: :jabref-intext-filter chicago.ODF.text :jabref-reference-filter chicago.ODF.reference #+ATTR_HTML: :bib2html-options "-a b -c -d" #+BIBLIOGRAPHY: :bib-file MyLibrary.bib :citation-style "chicago-note" :limit t :bib-file will be mandatory. (It is basically the input database, need not *necessarily* be a .bib file.) :citation-style will be advisory. Backends may choose to ignore or honor the style. :limit t can be supported by ODT via jabref. You may also want to review the #+TOC settings, more for consistency than anything else. Instead of #+toc: headlines 4 we can have #+toc: headlines :levels 4 or #+toc: :type headlines :levels 4