From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric S Fraga Subject: Re: Citations, continued Date: Tue, 3 Feb 2015 12:00:06 +0000 Message-ID: <87fvandx2x.fsf@pinto.chemeng.ucl.ac.uk> References: <87vbjmn6wy.fsf@berkeley.edu> <87sieokx8e.fsf@berkeley.edu> <87iofkdr6o.fsf@pank.eu> <87oapblpvc.fsf@berkeley.edu> <87iofjffkk.fsf@gmx.us> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56202) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YIc9T-0004Pv-F4 for emacs-orgmode@gnu.org; Tue, 03 Feb 2015 07:00:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YIc9Q-0007OU-AC for emacs-orgmode@gnu.org; Tue, 03 Feb 2015 07:00:19 -0500 Received: from mail-db3on0112.outbound.protection.outlook.com ([157.55.234.112]:39312 helo=emea01-db3-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YIc9Q-0007NX-2r for emacs-orgmode@gnu.org; Tue, 03 Feb 2015 07:00:16 -0500 In-Reply-To: <87iofjffkk.fsf@gmx.us> (rasmus@gmx.us's message of "Tue, 3 Feb 2015 11:35:23 +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: Rasmus Cc: emacs-orgmode@gnu.org On Tuesday, 3 Feb 2015 at 11:35, Rasmus wrote: [...] I'm enjoying following this thread. I look forward to the community converging on some solution. For me, any solution will likely do just fine as my use of citations is quite straightforward. I seldom, if ever, have pre or post text but I do use a couple of alternative citation types (author, year; year only). I have only one suggestion to keep in mind: >>> What happens when a field is undefined? >> >> I guess I would suggest the same thing as happens in LaTeX: you get a >> nice, bold "??" in the output where the missing data should be. > > Or better, throw an error. A *warning* would be better than an error, i.e. something that does indicate a problem but that doesn't stop the export completing. LaTeX does this (as noted above). When writing long articles, I often have dangling references which I don't resolve until later. I don't want to interrupt the writing part (i.e. the creative process) by getting caught up in bookkeeping. It's sometimes hard enough to just get started... ;-) Interestingly, I have just had a paper accepted for publication which was written *entirely* in org. I used the [[cite:fraga-etal-2014]] approach for handling citations. The paper made significant use of babel to have everything in one place (data, code, results). Very pleasing and painless experience. I did have to resort to LaTeX specific commands a few times but mostly for the preamble (title, authors, etc.). I would share the org file except that it has proprietary data. thanks, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.1, Org release_8.3beta-727-ga1cdc6.dirty