From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: Citations, continued Date: Mon, 02 Feb 2015 19:09:47 +0100 Message-ID: <87pp9smbh0.fsf@gmx.us> References: <87vbjmn6wy.fsf@berkeley.edu> <87h9v6okq7.fsf@nicolasgoaziou.fr> <87ioflmgkc.fsf@berkeley.edu> <87h9v4o1ye.fsf@gmx.us> <87wq40kyz3.fsf@berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34731) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YILRh-0000mK-N0 for emacs-orgmode@gnu.org; Mon, 02 Feb 2015 13:10:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YILRe-0002Bh-8d for emacs-orgmode@gnu.org; Mon, 02 Feb 2015 13:10:01 -0500 Received: from plane.gmane.org ([80.91.229.3]:39868) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YILRe-0002BW-1c for emacs-orgmode@gnu.org; Mon, 02 Feb 2015 13:09:58 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YILRb-0004lg-Hj for emacs-orgmode@gnu.org; Mon, 02 Feb 2015 19:09:55 +0100 Received: from 46-253-188-95.dynamic.monzoon.net ([46.253.188.95]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 02 Feb 2015 19:09:55 +0100 Received: from rasmus by 46-253-188-95.dynamic.monzoon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 02 Feb 2015 19:09:55 +0100 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: emacs-orgmode@gnu.org Hi, Richard Lawrence writes: > Hi Rasmus and all, > > Rasmus writes: > >> Richard Lawrence writes: > >>> Within a citation, each reference to an individual work needs to be >>> capable of containing: >>> 1) a database key that references the cited work >>> 2) prefix / pre-text >>> 3) suffix / post-text >>> 4) references to page/chapter/section/whatever numbers and ranges. >>> This is likely part of the prefix or suffix, but might be worth >>> parsing separately for localization or link-following behavior. >>> 5) a way of indicating backend-agnostic formatting properties. >>> Examples of some properties users might want to specify are: >> >>> - displaying only some fields (or suppressing some fields) from a >>> reference record (e.g., journal, date, author) >> >> Would this not be properties of the bibliography and not the citation? > > No, I mean things that can vary from one citation to the next -- like > what you'd write in LaTeX as > > \citet{Doe99} once thought foo, but in his \citeyear{Doe2014}, he > revises his position to bar. Okay, I misunderstood you then.q I though you wanted something like \AtEveryBibitem (of biblatex) which literally alters fields, e.g.: \AtEveryBibitem{\clearfield{month}}. >>> Citations as a whole also need: >>> 6) [@6] a way of indicating formatting properties for specific export >>> backends. >> I think the idea would be /not/ to have to consider specific backends. If >> you want special properties (say bold) for HTML could it not be solved by >> a macro or a filter? Probably I'm misunderstanding. > [...] > use a particular citation command for this citation, or the HTML backend > to use/add a particular CSS class. Maybe this could be done with macros > or filters, but I think that would prove complicated for all but the > simplest cases, since citations have argument structure that filters > might not necessarily `see'. I see. It's possible via macros. I don't have strong opinions on this. >>> 8) a reference to a citation style or style file >> >> How does this work outside of LaTeX? > > Well, Pandoc for example processes citations using the citeproc-hs It seems to use pandoc-citeproc which is based on citeproc-hs. > implementation of the Citation Style Language, which is an XML format > that allows describing how citations and bibliographies should be > formatted. Thus, for example, you could tell Pandoc to process your > citations in APA style, or any of the other styles in this repo: > > https://www.zotero.org/styles > > CSL is an XML format, and I shudder to think about implementing it in > Elisp, but that's how its done. In fact, Pandoc uses this even for > LaTeX output, rather than trying to map citations to the various \cite > commands. I wonder if Zotero can be used to format such citations. It can do something for rtf at least: https://www.zotero.org/support/rtf_scan —Rasmus -- A page of history is worth a volume of logic