emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Daniel Fleischer <danflscr@gmail.com>,
	 Alessandro Bertulli <alessandro.bertulli96@gmail.com>,
	org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: Org-ref not working when exporting to LaTeX
Date: Wed, 11 May 2022 14:59:01 -0400	[thread overview]
Message-ID: <CAF-FPGPTfQuk10Q5pQaPq4BF-ucPCMBCtYPVDJ9-fZHX4kUBsg@mail.gmail.com> (raw)
In-Reply-To: <CAJ51ETrbpPLj3jSUr_D9fjauKG7PU6jp_m4QgsKqF_7UxOoNRQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]

This is an aside, but I recently learned about citeproc-lua, which adds CSL
processing directly to tex and latex.

https://github.com/zepinglee/citeproc-lua

Now included in texlive 2022.

As that evolves more (there are still missing features), it could be
another viable alternative.

On Wed, May 11, 2022 at 2:19 PM John Kitchin <jkitchin@andrew.cmu.edu>
wrote:
>
> The regular export is preferred for LaTeX (C-c C-e l o) is preferred for
LaTeX export as it generates the LaTeX cite commands. The version in C-c
C-e r p uses CSL for the formatting, not LaTeX, and it allows you to get
nicely formatted results without using bibtex/biblatex as the citation
processor.
>
> John
>
> -----------------------------------
> Professor John Kitchin (he/him/his)
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>
>
>
> On Wed, May 11, 2022 at 2:15 PM Daniel Fleischer <danflscr@gmail.com>
wrote:
>>
>> Alessandro Bertulli [2022-05-11 Wed 19:41] wrote:
>>
>> > I'm going to post my setup in a minute. The
>> > point is: when exporting the org file to LaTeX (C-c C-e l o), a PDF
file
>> > gets produced, but it doesn't process the citation keys. For example,
in
>> > my file (see below), I got the key "acm:code" literally printed on the
>> > PDF file, in a bold font.
>>
>> Hi, org-ref uses its own export engine which you call via (C-c C-e r p).
>> Please try that and report back if there are still issues.
>>
>> --
>>
>> Daniel Fleischer
>>

[-- Attachment #2: Type: text/html, Size: 2343 bytes --]

  parent reply	other threads:[~2022-05-11 18:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 17:41 Org-ref not working when exporting to LaTeX Alessandro Bertulli
2022-05-11 18:14 ` Daniel Fleischer
2022-05-11 18:17   ` John Kitchin
2022-05-11 18:48     ` Daniel Fleischer
2022-05-11 18:59     ` Bruce D'Arcus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-12 14:40 Alessandro Bertulli

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=CAF-FPGPTfQuk10Q5pQaPq4BF-ucPCMBCtYPVDJ9-fZHX4kUBsg@mail.gmail.com \
    --to=bdarcus@gmail.com \
    --cc=alessandro.bertulli96@gmail.com \
    --cc=danflscr@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    /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).