emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Standardize #+BIBLIOGRAPHY line
Date: Mon, 22 Jul 2013 12:55:25 +0530	[thread overview]
Message-ID: <87k3kjyr37.fsf@gmail.com> (raw)


(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

             reply	other threads:[~2013-07-22  7:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22  7:25 Jambunathan K [this message]
2013-07-22  9:03 ` Standardize #+BIBLIOGRAPHY line Nicolas Goaziou
2013-07-22 13:16   ` Jambunathan K
2013-07-22 13:19     ` Jambunathan K
2013-07-22 13:31     ` Nicolas Goaziou
2013-07-22 13:47       ` Jambunathan K
2013-07-22 13:58         ` Nicolas Goaziou
2013-07-22 16:09           ` Jambunathan K
2013-07-22 19:33           ` Jambunathan K
2013-07-22 14:15       ` Rasmus
2013-07-22 16:29         ` Jambunathan K
2013-07-22 21:51           ` Rasmus
2013-07-25  8:47             ` Jambunathan K
2013-07-22 17:01         ` Jambunathan K
2013-07-22 19:34           ` Jambunathan K

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=87k3kjyr37.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    /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).