emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Feng Shu <tumashu@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: ox-bibtex.el -- how to join sequential citations
Date: Tue, 26 Nov 2013 06:16:08 -0700	[thread overview]
Message-ID: <8738mjmhfh.fsf@gmail.com> (raw)
In-Reply-To: 8761ri6sr9.fsf@gmail.com

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
> Feng Shu <tumashu@gmail.com> writes:
>> Eric Schulte <schulte.eric@gmail.com> writes:
>>> When exporting multiple sequential citations e.g., cite:foo cite:bar
>>> etc... I would like to see something like the following (latex used for
>>> this example) "\cite{foo, bar}", but instead I'm getting "\cite{foo}
>>> \cite{bar}", which leads to poorly formed PDFs (a similar thing happens
>>> for HTML export).
>> May be you should use \cite{foo, bar} directly in org file.
> That was, indeed, the original way to handle citations in the former
> org-export-bibtex.el. It is still supported in both LaTeX, obviously,
> and HTML (which will split the above among two anchors).
> "cite" link support was added later, and is lacking in this area.
>>> My question is how best to fix this, should I write a filter function,
>>> or does the export engine already have processes in place to handle
>>> these sorts of export context issues?
> At the user level, a filter is definitely the way to go.

Thanks, the following seems to be working.  Perhaps the filter function
should be added to ox-bibtex.el?

    (defun org-bibtex-group-citations (text backend info)
      "Convert begin/end{verbatim} to begin/end{Verbatim}.
      Allows use of the fancyvrb latex package."
        (insert text) (goto-char (point-min))
         ((org-export-derived-backend-p backend 'latex)
          (while (re-search-forward
                  nil t)
            (replace-match "\\\\cite{\\1,")
            (goto-char (point-min))))
         ((org-export-derived-backend-p backend 'html)
          (while (re-search-forward
                  "\\(#[[:alnum:]]+\">[0-9]+<\/a>\\)\\][[:space:]\n\r]*\\[\\(<a href=\"#[[:alnum:]]+\">[0-9]+<\/a>\\)"
                  nil t)
            (replace-match "\\1,\\2")
            (goto-char (point-min)))))

    (add-to-list 'org-export-filter-final-output-functions


> Though, it is an interesting feature to implement in ox-bibtex.el. One
> idea would be to write another parse-tree filter function which would
> change cite links into \cite{...} commands and consecutive cite links
> into \cite{..., ...} commands.
> This would also allow us to get rid of both `org-html-link' and
> `org-latex-link' advices, as no more cite link would be left in the
> parse tree anyway.
> What do you think?
> Regards,

Eric Schulte
PGP: 0x614CA05D

  reply	other threads:[~2013-11-26 13:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23 16:23 ox-bibtex.el -- how to join sequential citations Eric Schulte
2013-11-24  2:59 ` Feng Shu
2013-11-24  9:42   ` Nicolas Goaziou
2013-11-26 13:16     ` Eric Schulte [this message]
2013-11-26 17:03       ` Nicolas Goaziou
2013-12-01 16:08         ` Nicolas Goaziou

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:

  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=8738mjmhfh.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=tumashu@gmail.com \


* 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


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).