From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Re: Standardize #+BIBLIOGRAPHY line Date: Thu, 25 Jul 2013 14:17:20 +0530 Message-ID: <87iozzhvqf.fsf@gmail.com> References: <87k3kjyr37.fsf@gmail.com> <87hafn55l0.fsf@gmail.com> <87ip02wx96.fsf@gmail.com> <874nbm67rq.fsf@gmail.com> <87hafmwuhs.fsf@gmx.us> <87hafmpnh7.fsf@gmail.com> <87txjmb6w1.fsf@gmx.us> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50949) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V2HBG-0006kE-NS for emacs-orgmode@gnu.org; Thu, 25 Jul 2013 04:45:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V2HBF-0003kp-6A for emacs-orgmode@gnu.org; Thu, 25 Jul 2013 04:45:50 -0400 Received: from mail-pb0-x229.google.com ([2607:f8b0:400e:c01::229]:38144) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V2HBE-0003ke-Oc for emacs-orgmode@gnu.org; Thu, 25 Jul 2013 04:45:49 -0400 Received: by mail-pb0-f41.google.com with SMTP id rp16so489689pbb.0 for ; Thu, 25 Jul 2013 01:45:47 -0700 (PDT) In-Reply-To: <87txjmb6w1.fsf@gmx.us> (rasmus@gmx.us's message of "Mon, 22 Jul 2013 23:51:26 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Rasmus Cc: Nicolas Goaziou , emacs-orgmode@gnu.org I am not sure how many people will read this or make sense out of it. Anyways, here I go. Rasmus writes: > - textcite k :pre x :post y =E2=86=92 K (pre, year, post) > - parencite k :p x :post y =E2=86=92 (pre, K, year post) > - cite k :pre x :post y =E2=86=92 K pre K year post > - footcite k :pre x :post y =E2=86=92 [fn::pre K Year post.] > - citeauthor k :pre x :post y =E2=86=92 pre K post > - citeyear k :pre x :post y =E2=86=92 pre year post JabRef's command line doesn't take pre and post arguments. Both JabRef and Zotero use LibreOffice application APIs to insert citations. i.e., citations are introduced manually, by hand.=20=20 But JabRef lets you "translate a key" be it k -> Author(k) or k->Date(k) or k->Author-Date(k) in a "context-free" manner. By "contex free", I mean, it wouldn't bother about whether the key occurs for the first time or whether it occurs for second time (think Ibid) etc. ---------------------------------------------------------------- Writing in Org should feel natural. It should be fuzzy but powerful. Specifically, it shouldn't read like Lisp. So having ":pre" and ":post" elements or going extra lengths to get the precise parenthesis (Is it [] or ()?) or the separators (Is it , or ;?) would be an overkill. The immediate requirement should be to create a good enough working draft that can be circulated among peers or sent to the publisher for a professional processing. Parser enhancements or introducing new syntax elements - that are heavy-weight - should be avoided all costs. What is needed is "expressivity" not "extensibility" Pre and Post are inherently positional. So, if one can identify where the middle part is - in all your examples it a Key or f(Key), for some "f" - then identifying a pre and post components should be easy provided the "cite span" is delineated by explicit markup or "natural" boundaries. ---------------------------------------------------------------- Approach 1: Delineate a "cite span" using [] Con: Parser enhancement could be non-trivial because it introduces a new Org-syntax delimiter. One can map this, \autocite[59][See also](Becker2010) =3D> See also Becker, 59 to this Org syntax: [See also [cite:Becker2010] 59] Let pre and post occur in natural order but use extra markers to indicate a "span" or a stretch. ---------------------------------------------------------------- Approach 2: Delineate using natural boundaries. Con: Parser enhancement is pretty localized just footnote elements. Less bugs and better expressivity. Another variation could be=20 #+BEGIN_SRC org [fn:Becker2010p59] and [fn:Becker2010p503] [fn:Becker2010p59] See also [cite:Becker2010] 59 [fn:Becker2010p503] See also [cite:Becker2010] 503 #+END_SRC Here Becker2010p59 and Becker2010p503 are opaque labels. They could as well be tom and harry, for example. #+BEGIN_SRC org [fn:tom] and [fn:dick] [fn:tom] See also [cite:Becker2010] 59. Some extra note, if the note is to be stored right within Org. [fn:dick] See also [cite:Becker2010] 503 #+END_SRC #+BEGIN_SRC org [fn:tom] and [fn:dick] #+ATTR_?: See also [cite:Becker2010] 59.=20=20 [fn:tom] Some extra note, if the note is to be stored right within Org. [fn:dick] See also [cite:Becker2010] 503 #+END_SRC Here "the content of an object" is specified using a combination of "label" and "element". The leading sentence/phrase or paragraph of footnote definition, if it contains [cite: ] element, can assumed to specify pre and post. The rest of the sentence or paragraph can be a "note" that augments the specific citation. The [cite:...] elements itself delineates (by virtue of it's position) the pre and post elements. ---------------------------------------------------------------- The use of object designated with label + element could be used in conjunction with Image links as well. This is just what ASCII uses to translate links but with a "ATTR_" twist attached to the "labeled paragraph" See [Orgmode Logo] #+ATTR_HTML: Put whatever here. [Orgmode Logo] http://orgmode.org/org-mode-unicorn.png ----------------------------------------------------------------