From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Standardize #+BIBLIOGRAPHY line
Date: Mon, 22 Jul 2013 15:58:14 +0200 [thread overview]
Message-ID: <87y58y4ryh.fsf@gmail.com> (raw)
In-Reply-To: <874nbmwvsy.fsf@gmail.com> (Jambunathan K.'s message of "Mon, 22 Jul 2013 19:17:41 +0530")
Jambunathan K <kjambunathan@gmail.com> writes:
>> I understand. You can still use ox-bibtex.el for now, and just ignore
>> all the "[[cite:...]]" part.
>
> Each citation processor should reside in it's own file. So ox-jabref.el
> is the right place for my changes.
LaTeX and HTML processors already reside in ox-bibtex.el. If you want to
create a new file, so be it, but try at least to require ox-bibtex and
use existing accessors and predicates to maintain compatibility.
> It seems that you are not interested in introducing ox-cite.el or a
> make-shift `citation-reference' element.
I don't know what led you to this conclusion.
I'm very much interested in supporting bibliographies from Org. I also
know it will require to implement a new citation object in the process.
I'm just pointing out two things:
- ox-bibtex will have to be implemented differently (e.g., no more
defadvices). So, it's not just about moving ox-bibtex into another
directory.
- before discussing (again) citations syntax, we must ensure that this
is a realistic goal. IOW we need a proof of concept for, at least,
every major back-end (including ASCII).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-07-22 13:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 7:25 Standardize #+BIBLIOGRAPHY line Jambunathan K
2013-07-22 9:03 ` 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 [this message]
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=87y58y4ryh.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@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).