emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: "Liste-emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: best suited latex document class for html export ?
Date: Tue, 29 Jan 2019 16:19:18 +0100	[thread overview]
Message-ID: <CAD-VTcFZgUwDdJ4FSGzY7AfgRb7duGZ5OT393jWpo-HJiTJT8A@mail.gmail.com> (raw)
In-Reply-To: <m2fttba768.fsf@andrew.cmu.edu>

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

Many thanks John, your reply is helpful. Precisely, I used recently pandoc
and tried also to export to html an org file. That explains my question.

Best wishes,

Jo.

Le mar. 29 janv. 2019 à 15:07, John Kitchin <jkitchin@andrew.cmu.edu> a
écrit :

> unless you are going to html/odt/etc. through latex (e.g. pandoc or
> latex2html)
> you don't need a latex class to for the other backends.
>
> Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> writes:
>
> > Hello,
> >
> > A question that I had maybe asked (I apologize): is there a best suited
> > style (document class for latex) for org-export in html, odt, etc. ? I
> > would be happy to get the more convient setup in org-mode for multiple
> > exports.
> >
> > If my question does not make sense, please, forget it.
> >
> > Best wishes,
> >
> > Jo.
>
>
> --
> Professor John Kitchin
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>

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

      reply	other threads:[~2019-01-29 15:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29  8:08 best suited latex document class for html export ? Joseph Vidal-Rosset
2019-01-29 14:07 ` John Kitchin
2019-01-29 15:19   ` Joseph Vidal-Rosset [this message]

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=CAD-VTcFZgUwDdJ4FSGzY7AfgRb7duGZ5OT393jWpo-HJiTJT8A@mail.gmail.com \
    --to=joseph.vidal.rosset@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).