From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Best practices for dual HTML/LaTeX export for scientific papers
Date: Thu, 2 Apr 2015 15:01:59 -0700 [thread overview]
Message-ID: <alpine.OSX.2.00.1504021438140.1024@charles-berrys-macbook.local> (raw)
In-Reply-To: <871tk25ygq.fsf@gmx.us>
On Thu, 2 Apr 2015, Rasmus wrote:
> Hi,
>
> David Dynerman <david@block-party.net> writes:
>
[snip]
>
>> 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.
>
You can get part way just by using a table.
#+NAME: as-org
#+BEGIN_SRC org
#+ATTR_LATEX: :environment figure
| [[file:./testa.png]] | [[file:./testb.png]] |
#+END_SRC
#+BEGIN_SRC emacs-lisp :var y=as-org() :wrap latex
(org-export-string-as y 'latex t)
#+END_SRC
#+BEGIN_SRC emacs-lisp :var y=as-org() :wrap html
(org-export-string-as y 'html t)
#+END_SRC
With ob-org.el loaded, the two elisp blocks will produce tables of images
in the latex and html backends.
Some further work is needed to adjust the `width=...' of the latex result
and to put captions in the right places in both latex and html.
Using the babel blocks makes it easy to see what might be needed.
In the end, I expect a filter would be used rather than babel blocks.
HTH,
Chuck
next prev parent reply other threads:[~2015-04-02 22:02 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
2015-04-02 22:01 ` Charles C. Berry [this message]
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=alpine.OSX.2.00.1504021438140.1024@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).