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:31:21 +0200 [thread overview]
Message-ID: <874nbm67rq.fsf@gmail.com> (raw)
In-Reply-To: <87ip02wx96.fsf@gmail.com> (Jambunathan K.'s message of "Mon, 22 Jul 2013 18:46:21 +0530")
Jambunathan K <kjambunathan@gmail.com> writes:
> Getting Citation right to cater to general needs is going to be complex.
> This is mainly because
>
> 1. Org's object syntax is very rudimentary and not "extensible"
> 2. "real-world" citations may need some annotations page number etc.
>
> I think it is good to *atleast make a move* in standardizing the cite
> elements. My gut feeling is that cite objects - for now - should be
> coded as \cite { } latex objects. This specifically means that link
> syntax for cite should NOT BE ENCOURAGED (or STRONGLY DISCOURAGED).
I understand. You can still use ox-bibtex.el for now, and just ignore
all the "[[cite:...]]" part.
> As an aside, I am inclined to think of cite objects as "special class"
> of "footnote" elements.
I tend to agree. There was a discussion on the ML about a possible
syntax. I think it is a bit early to set it in stone anyway. As you
said, the point here is to make a move towards standardization, even if
it means using \cite{...} and `defadvice' for now.
> Does the author have copyright assignments for contributing to Emacs?
>
> Taru Karttunen <taruti@taruti.net>
>
> As a personal policy, I don't want to touch a file which wouldn't end up
> in Emacs proper.
>
> Any changes that I make to Emacs - that includes Org-mode - is
> *guaranteed* to end up in Emacs proper. It's going to happen in it's
> own time.
Nobody can guarantee that code relative to bibliographies will become
mainstream. What if normalization fails, for one reason or another?
Anyway, I don't think assignment is a problem. If we decide to handle
bibliographies in Org core, ox-bibtex will have to be rewritten anyway
(and will become ox-bibliography or something like that). Though, it
would obviously be best if original "org-bibtex.el" author (Cc'ed) had
already signed FSF papers.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-07-22 13:31 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 [this message]
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=874nbm67rq.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).