emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Rüdiger Sonderfeld" <ruediger@c-plusplus.de>
To: emacs-orgmode@gnu.org
Subject: Re: [RFC] BibELTeX: native bibtex support in org-mode
Date: Wed, 12 Jun 2013 10:48:33 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130612T124707-331@post.gmane.org> (raw)
In-Reply-To: 87y5agcjbm.fsf@pank.home

Rasmus <rasmus <at> gmx.us> writes:

> 
> Rüdiger Sonderfeld <ruediger <at> c-plusplus.de> writes:
> 
> > I've started writing BibELTeX as an alternative to =ox-bibtex.el=. 
> >
> > https://github.com/ruediger/bibeltex
> 
> Would you consider providing a test file showing off its features?

I added a file test/example.org.  Put bibeltex.el somewhere in your load-path 
and require it.  This should be enough to make it work (use unload-feature to 
remove it again).

You can then export the document to any format you like.  Good test case is 
using org-mode export (ox-org.el).

> I'm skeptical but probably it is 'cause I've misunderstood something!
> Someone put a lot of thought into writing e.g. biblatex or
> odt-bibliographies.  Surely(?) we would want to leverage upon those
> and only have org-support insofar as serving some backend-specific
> parser enough information to do its work?

Certainly.  BibELTeX is designed to do this.  For LaTeX export it just 
generates the corresponding LaTeX instructions (can be adopted even for 
biblatex).

But except for LaTeX there doesn't seem to be a real support for bibliography.  
It can be simulated for html using bibtex2html (ox-bibtex.el).  But even that 
is not compatible with biber/biblatex.  That's the reason behind BibELTeX.

Regards

  reply	other threads:[~2013-06-12 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 19:25 [RFC] BibELTeX: native bibtex support in org-mode Rüdiger Sonderfeld
2013-06-11 23:35 ` Rasmus
2013-06-12 10:48   ` Rüdiger Sonderfeld [this message]
2013-06-12 13:31     ` Ista Zahn

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=loom.20130612T124707-331@post.gmane.org \
    --to=ruediger@c-plusplus.de \
    --cc=emacs-orgmode@gnu.org \
    /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).