From: Nick Dokos <nicholas.dokos@hp.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: biblatex citation
Date: Sat, 27 Aug 2011 04:52:15 -0400 [thread overview]
Message-ID: <10180.1314435135@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Nick Dokos <nicholas.dokos@hp.com> of "Sat, 27 Aug 2011 04:16:41 EDT." <9866.1314433001@alphaville.dokosmarshall.org>
Nick Dokos <nicholas.dokos@hp.com> wrote:
> Thomas S. Dye <tsd@tsdye.com> 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
next prev parent reply other threads:[~2011-08-27 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 7:10 biblatex citation Thomas S. Dye
2011-08-27 8:16 ` Nick Dokos
2011-08-27 8:52 ` Nick Dokos [this message]
2011-08-27 9:38 ` Nicolas Goaziou
2011-08-27 21:12 ` Thomas S. Dye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10180.1314435135@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).