emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Best practices for dual HTML/LaTeX export for scientific papers
Date: Thu, 02 Apr 2015 17:41:57 +0200	[thread overview]
Message-ID: <871tk25ygq.fsf@gmx.us> (raw)
In-Reply-To: 0D61CF76-2D92-4A9C-A90E-2F175BDDA91B@block-party.net

Hi,

David Dynerman <david@block-party.net> writes:

> 1) Citations to an external bibliography

I use a home-brewed solution.  If your requirements are modest there's
also ox-bibtex.el in addition to John's package (which I haven't tried).

In the future there may be a "official" solution.

> 2) Figures containing multiple side-by-side figures with subcaptions (e.g. in LaTeX I would use minipage + subcaption)

For LaTeX you can find solution on this list.  I would not know how to do
it in "plain" HTML.  That would be the first step to a solution.

> 3) In-document links (i.e., cross references) to figures (e.g., “See Figure 1”)

Can't you just do:

     #+NAME: fig
     #+CAPTION: caption
     [[file:fig.png]]

     See figure [[fig]]

> 4) LaTeX and HTML export

ox stands for org export.  A number of backends including LaTeX and html
are supported.  It's documented in the manual.

> Is it an issue of adding some functionality to the HTML exporter?

Patches are welcome, but you should aim to target as all relevant
backends.  For your own solution you can use filters or you can ox-publish
and change the functions that you desire to change.

Hope it helps,
Rasmus

-- 
Send from my Emacs

  parent reply	other threads:[~2015-04-02 15:42 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
2015-04-02 15:41 ` Rasmus [this message]
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=871tk25ygq.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).