From: John Kitchin <firstname.lastname@example.org>
To: David Dynerman <email@example.com>
Subject: Re: Best practices for dual HTML/LaTeX export for scientific papers
Date: Thu, 02 Apr 2015 11:38:24 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
#1 org-ref does an ok job with this. It isn't as good at html output as
for latex output (because latex has a dedicated citation processor via
bib(la)tex, and org-ref has a hackery for generating mostly ok entries
from the bibtex file, for the common types I have used.). For example,
you often need to escape things like % and & in bibtex, and there is
limited support for removing those in org-ref. Also, org-ref currently
does not support latex in the bibtex entries for html output. There is
potential for this by replacing fragments with images, but I probably
won't look into that until the summer. The output style is
user-customizable, but currently somewhat limited. I may look into
improving this over the summer to make it more flexible.
Cannot comment on #2. I solve this by manually by putting both figures
in a single image file, and using a single caption with a) and b) in the
#3 I just pushed a small enhancement to org-ref that makes the ref links
point to a #id in the html document. this works for figures at least. It
will take some post processing to change the link from the label to a
number, and maybe a custom exporter to do that. A temporary solution is to
label your figures with numbers, e.g. #+LABEL: fig:1. It isn't pretty,
but it would be functional.
David Dynerman writes:
> Hi all,
> I’m currently trying to use org mode to write a scientific paper. Here is my wishlist:
> 1) Citations to an external bibliography
> 2) Figures containing multiple side-by-side figures with subcaptions (e.g. in LaTeX I would use minipage + subcaption)
> 3) In-document links (i.e., cross references) to figures (e.g., “See Figure 1”)
> 4) LaTeX and HTML export
> This seems like a modest set of requirements, but I’ve had trouble getting it going.
> For #1, I’m currently using John Kitchin’s org-ref package. This is nice - it gives me an HTML bibliography, but it has it’s own link syntax for in-document links to figures that doesn’t export to HTML. Thus I have to use org-ref style links for citations, but regular org-style links for figure cross references.
> I haven’t figured out how to do #2. Is this currently possible? Is it an issue of adding some functionality to the HTML exporter?
> For #3, I’m currently using #+LABEL: fig:foo, followed by [[fig:foo]]. Is this the suggested way of doing it?
> The hard part seems #4: org-ref gives a workable HTML bibliography, but I run into some other issues listed above.
> Can anyone suggest some “Best practices” for the above? I’d be willing to collect these into a list, which I think would be really helpful for new users. I’d also be willing to look into adding this functionality, if someone could suggest a good way for it to fit into the codebase/framework.
> Thank you,
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
next prev parent reply other threads:[~2015-04-02 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 14:30 Best practices for dual HTML/LaTeX export for scientific papers David Dynerman
2015-04-02 15:00 ` Eric S Fraga
2015-04-02 15:38 ` John Kitchin [this message]
2015-04-02 15:41 ` Rasmus
2015-04-02 22:01 ` Charles C. Berry
2015-04-03 10:27 ` Sebastien Vauban
2015-04-03 10:39 ` Ken Mankoff
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 \
* 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).