From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: biblatex citation Date: Sat, 27 Aug 2011 04:52:15 -0400 Message-ID: <10180.1314435135@alphaville.dokosmarshall.org> References: <9866.1314433001@alphaville.dokosmarshall.org> Reply-To: nicholas.dokos@hp.com Return-path: Received: from eggs.gnu.org ([140.186.70.92]:44584) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QxEcn-0001Tv-Vw for emacs-orgmode@gnu.org; Sat, 27 Aug 2011 04:52:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QxEcm-0004Ag-Ov for emacs-orgmode@gnu.org; Sat, 27 Aug 2011 04:52:21 -0400 Received: from g1t0028.austin.hp.com ([15.216.28.35]:24928) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QxEcm-0004AO-J3 for emacs-orgmode@gnu.org; Sat, 27 Aug 2011 04:52:20 -0400 In-Reply-To: Message from Nick Dokos of "Sat, 27 Aug 2011 04:16:41 EDT." <9866.1314433001@alphaville.dokosmarshall.org> 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: "Thomas S. Dye" Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org Nick Dokos wrote: > Thomas S. Dye wrote: > > > Aloha all, > > > > This biblatex construct: > > \parencites[234]{kirch85}[185]{kirch84} > > > > is output like this: > > \parencites[234]{kirch85}[185]\{kirch84\} > > > > The biblatex syntax is unusual (to me) in LaTeX. I wonder if it is > > possible to support it in Org-mode? > > > > So is the syntax \parencites followed by an arbitrary number of pairs > [page#]{ref}? > > latex export knows to do the right thing for a command with optional and > mandatory arguments: \command[opt]{mand} is properly protected, but the > above case stretches it to beyond its breaking point. > > After a quick look, all I could come up with as a possibility was yet > another special case in org-export-latex-preprocess - and one more scan > of the whole file to add to the many (roughly 20!) that this function > does. > Well, maybe another scan is not necessary: the existing command handler could perhaps be extended to deal with this case. But the regexp in that case is horrendous enough as it is - if it gets any hairier, it will become Medusa: mortals looking at it will drop dead. However it might be that a loop that eats multiple pairs of [...]{...} occurrences would be simple enough to implement. My preferred solution would be for \parencites to change its syntax :-) If it were implemented like this e.g. \parencites{234|kirch85|185|kirch84} it would be easier to type *and* org would be able to handle it out of the box: a win-win for everybody except for the parencites author. Nick