From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: biblatex citation Date: Sat, 27 Aug 2011 11:38:42 +0200 Message-ID: <87ei07mbx9.fsf@gmail.com> References: <9866.1314433001@alphaville.dokosmarshall.org> <10180.1314435135@alphaville.dokosmarshall.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:52804) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QxFMJ-0006xK-31 for emacs-orgmode@gnu.org; Sat, 27 Aug 2011 05:39:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QxFMH-0004Ad-Vf for emacs-orgmode@gnu.org; Sat, 27 Aug 2011 05:39:23 -0400 Received: from mail-ww0-f49.google.com ([74.125.82.49]:52780) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QxFMH-0004AZ-NC for emacs-orgmode@gnu.org; Sat, 27 Aug 2011 05:39:21 -0400 Received: by wwf10 with SMTP id 10so3391571wwf.30 for ; Sat, 27 Aug 2011 02:39:20 -0700 (PDT) In-Reply-To: <10180.1314435135@alphaville.dokosmarshall.org> (Nick Dokos's message of "Sat, 27 Aug 2011 04:52:15 -0400") 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: nicholas.dokos@hp.com Cc: emacs-orgmode@gnu.org Hello, Nick Dokos writes: > 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. Note that Org core already recognizes such latex commands, as confirmed by using `org-inside-latex-macro-p' anywhere inside it. In this case, it's just an exporter failure. Regards, -- Nicolas Goaziou