From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: Citations, continued Date: Sun, 08 Feb 2015 10:28:14 +0100 Message-ID: <87d25kpxap.fsf@pank.eu> References: <87vbjmn6wy.fsf@berkeley.edu> <87sieokx8e.fsf@berkeley.edu> <54d04780.cb58460a.5243.2603@mx.google.com> <87h9v3li8t.fsf@berkeley.edu> <54d078ff.b044440a.06ec.3cf6@mx.google.com> <87d25rkmag.fsf@berkeley.edu> <54d1bc7b.c57d440a.3c5d.2dca@mx.google.com> <87vbjh284z.fsf@nicolasgoaziou.fr> <87mw4tk4m7.fsf@berkeley.edu> <87oap7z664.fsf@nicolasgoaziou.fr> <87fvaibr3k.fsf@berkeley.edu> <87y4o9s5qc.fsf@nicolasgoaziou.fr> 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]:46950) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YKOAI-0006Dz-Ob for emacs-orgmode@gnu.org; Sun, 08 Feb 2015 04:28:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YKOAF-00019E-JH for emacs-orgmode@gnu.org; Sun, 08 Feb 2015 04:28:30 -0500 Received: from plane.gmane.org ([80.91.229.3]:53566) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YKOAF-000190-DO for emacs-orgmode@gnu.org; Sun, 08 Feb 2015 04:28:27 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YKOA8-0008KR-Fu for emacs-orgmode@gnu.org; Sun, 08 Feb 2015 10:28:20 +0100 Received: from tsn109-201-152-245.dyn.nltelcom.net ([109.201.152.245]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 08 Feb 2015 10:28:20 +0100 Received: from rasmus by tsn109-201-152-245.dyn.nltelcom.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 08 Feb 2015 10:28:20 +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 Nicolas Goaziou writes: > Using the example from Erik Hetzner in the same thread, what about: > > 1. [cite:@item1] says blah. > 2. [cite:@item1: p. 30] says blah. Why is "p." stripped here? > 3. [cite:@item1: p. 30, with suffix] says blah. > 4. [cite:@item1: -@item2 p. 30; see also @item3] says blah. If item{1,2} have the same author biblatex[-chicago?] is smart enough to compress it to "author (year1, year2)". So this example seems like a downgrade if "-" is required to get the suggested output. > 5. A citation group [cite:: see @item1 p. 34-35; also @item3 chap. 3]. Why is chap. *not* stripped here? > 6. Another one [cite::see @item1 p. 34-35]. > 7. Citation with a suffix and locator [cite:: @item1 pp. 33, 35-37, and nowhere else]. Where does suffix and locator end here. E.g. what is the output of [cite:: @item1 33, pp. 35-37, and nowhere else]. > 9. Citation with suffix only [cite:: @item1 and nowhere else]. How do I know this is a suffix? Is locator a regexp like \`[p\.0-9 ]+? What is [cite:@K s. 12] or [cite:@K side.? 12]? > 10. Like a citation without author: [cite:: -@item1], and now Doe > with a locator [cite:: -@item2 p. 44]. > 2. Doe (2005, 30) says blah. > 5. A citation group (see Doe 2005, 34–35; also Doe and Roe 2007, chap. 3). > 7. Citation with a suffix and locator (Doe 2005, 33, 35–37, and nowhere else). > Note that space after the second colon is not mandatory. More > explicitly, syntax would be either > > [cite:IN-TEXT-KEY] > > or > > [cite:IN-TEXT-KEY?:SPACE* CITATIONS] > > where CITATIONS is any number of > > PREFIX? KEY SUFFIX? > > separated with semi-colons. What if I need several text cite keys. Say @K{1,2} is the same author A, and @K3 is B. Then [cite:@K1,@K2,@K3] should/could be something like A (Y1, Y2), and B (Y3). How do I express this? Some comments. 1. Am I supposed to distinguish between a text citations and parenthesis citation based on a single ":"? That's hard. Why not distinguish based on the initial label? E.g. {textcite, parentcite} or {citet, citep}. 2. The idea of locator /and/ suffix is confusing. The fact that your examples suggest seemingly random dropping of data from locator makes me want to avoid it even more. It's a 'can of worms' to use a frequently emerging expression from this list. 3. This is almost full circle. The proposal above seems no better (and IMO worse) than e.g. the generalized links that Tom suggested, e.g. [TYPE: KEY :pre PRE :post SUF] or [TYPE: PRE @KEY POST]. Or [[TYPE: KEY :pre PRE :post SUF]] or [[TYPE: PRE @KEY POST]]. 4. The reason for suggested syntax seems to be support some benchmark like A1 (Y1, Y2 also A2, Y3). I have never come across a nested citation like this. I have seen either (A1 Y1, Y2 and A2, Y3) or A1 (Y1, Y2) and A2 (Y3). . . 5. . . . Yet I still don't know how to get A1 (PRE Y2) with the above. Is the benchmark correct? If parsing speed is key here I think that [citet: pre1 @k1 post1; pre2 @k2 post2] and [citep: pre1 @k1 post1; pre2 @k2 post2] are clearer solutions. But this is clearly closer to a LaTeX than pandoc. —Rasmus -- Dung makes an excellent fertilizer