From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: David Dynerman <david@block-party.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Best practices for dual HTML/LaTeX export for scientific papers
Date: Thu, 2 Apr 2015 16:00:17 +0100 [thread overview]
Message-ID: <87619e60e6.fsf@ucl.ac.uk> (raw)
In-Reply-To: <0D61CF76-2D92-4A9C-A90E-2F175BDDA91B@block-party.net> (David Dynerman's message of "Thu, 2 Apr 2015 09:30:15 -0500")
On Thursday, 2 Apr 2015 at 09:30, David Dynerman wrote:
> Hi all,
>
> I’m currently trying to use org mode to write a scientific paper. Here is my wishlist:
I only ever target LaTeX so cannot help with the HTML end of things.
> 1) Citations to an external bibliography
John Kitchin's org-ref package is probably the way to go. I don't use
it but use simply [[cite:blah-et-al]] which exports, in LaTeX, to
\cite{blah-et-al} and I make sure that my org-latex-pdf-process runs
bibtex on the resulting LaTeX.
> 2) Figures containing multiple side-by-side figures with subcaptions (e.g. in LaTeX I would use minipage + subcaption)
Not sure how to do this.
> 3) In-document links (i.e., cross references) to figures (e.g., “See Figure 1”)
What you currently do is what I do, labelling with
#+label: fig-label
and referring via [[fig-label]]).
> 4) LaTeX and HTML export
I don't bother with the latter although you may be able to use one of
the LaTeX to HTML converters out there to good effect (pandoc, htlatex)?
The recent developments on citation syntax for org may help resolve some
of the issues with multiple export targets for scientific papers,
however. Stay tuned!
HTH,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.1, Org release_8.3beta-921-gfd8c84
next prev parent reply other threads:[~2015-04-02 15:00 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 [this message]
2015-04-02 15:38 ` John Kitchin
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
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=87619e60e6.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=david@block-party.net \
--cc=emacs-orgmode@gnu.org \
/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).