From: "Clément B." <clement@inventati.org>
To: Ken Mankoff <mankoff@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: State of the art in citations
Date: Sun, 27 Apr 2014 18:05:20 +0200 [thread overview]
Message-ID: <87ha5eoj0f.fsf@gaillac.origami> (raw)
In-Reply-To: <m2oazm7pzo.fsf@gmail.com>
> I find the best way to support ODT is simply add something like this:
>
> ((eq format 'odt)
> (format "(%s)" desc))
>
> This doesn't create a bibliography section, but that section is awkward
> to export to anyway. It requires the 3rd party Org hack that isn't
> officially supported, java, jabref, is awfully slow (~2
> seconds/reference), etc. I now put the references inline as above, and
> then manually add the references by exporting to PDF and copying/paste
> that reference section.
>
> Not great, but less of a hack than ODT-supported references, and working
> with ODT/Word is a hack anyway.
I came to a similar conclusion for html export, it is very hard
to match bibtex/biblatex to produce a proper bibliography, so one
might as well use it. At one point, the thought of writing a
custom citation style that would output html code crossed my mind
(I think biblatex would allow that), but I just don't use html
export enough. Although if this is possible, it could work with
xml for odt as well.
> Still looking into "lastname (Year)" format...
I hadn't noticed that before, but now that you mention it, I
think this is related to the way you format your bib file.
For example "%A (%y)" with:
1. name = {Darwin, Charles}
year = {1859}
will yield "Darwin (1859)"
2. name = {Charles Darwin}
year = {1859}
will yield "Charles Darwin (1859)
Not very consistent. This might be something to take to the
AUCTeX guys.
next prev parent reply other threads:[~2014-04-27 16:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 14:53 State of the art in citations Clément B.
2014-04-27 15:26 ` Ken Mankoff
2014-04-27 16:05 ` Clément B. [this message]
2014-04-27 16:10 ` Ken Mankoff
-- strict thread matches above, loose matches on Subject: below --
2014-04-26 18:26 Clément B.
2014-04-28 1:53 ` Richard Lawrence
2014-04-26 16:56 Clément B.
2014-04-27 13:08 ` Leonard Randall
2014-04-27 14:14 ` Clément B.
2014-04-27 14:41 ` Ken Mankoff
2014-04-27 16:01 ` Thomas S. Dye
2014-04-27 16:16 ` Ken Mankoff
2014-04-27 16:57 ` Clément B.
2014-04-27 19:20 ` John Kitchin
2014-04-27 21:30 ` Clément B.
2014-04-28 13:57 ` Julian M. Burgos
2014-04-28 13:56 ` Julian M. Burgos
2014-04-29 9:30 ` Vikas Rawal Lists
2014-04-29 15:36 ` Richard Lawrence
2014-04-29 9:30 ` Vikas Rawal Lists
2014-04-25 12:11 Julian M. Burgos
2014-04-25 15:42 ` Grant Rettke
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=87ha5eoj0f.fsf@gaillac.origami \
--to=clement@inventati.org \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@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).