emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Marcelo de Moraes Serpa <celoserpa@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Org HTML->PDF publishing
Date: Tue, 18 Sep 2012 13:12:14 -0500	[thread overview]
Message-ID: <CA+M2ft_uw63tCnE1KWQQH935opL3Lcu_aNer2_Nq1LvnA-1mjA@mail.gmail.com> (raw)
In-Reply-To: <CACHMzOHgJTUxGi43v9wQgL3g14Ap2rMd3CrmmXxbOrsaN3SU4w@mail.gmail.com>

If you have the html, there seem to be some things around to convert to PDF:
- http://code.google.com/p/wkhtmltopdf/
- http://pypi.python.org/pypi/xhtml2pdf/
- http://www.winnovative-software.com/download.aspx
- http://www.html2pdf.fr/en

Good luck!
John

On Tue, Sep 18, 2012 at 12:58 PM, Marcelo de Moraes Serpa
<celoserpa@gmail.com> wrote:
> Hey guys,
>
> Is it feasible to publish something (say an ebook) to html and then convert
> it to pdf?
>
> I know *TeX is the most powerful framework for creating PDFs, but given that
> I'm more familiar with CSS, I'm sure I could come up with a better style for
> the document in much less time than if, say, using LaTeX, as of now.
>
> My thought is, publish to HTML via org using a custom CSS, and then convert
> this HTML+CSS to PDF somehow - I'm still not sure how exactly - printing to
> PDF from the browser might be an option, however, I'm afraid that the final
> PDF quality will not be enough for the given publication.
>
> Has anyone tried this workflow?
>
> Cheers,
>
> - Marcelo.

  parent reply	other threads:[~2012-09-18 18:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 17:58 Org HTML->PDF publishing Marcelo de Moraes Serpa
2012-09-18 18:09 ` Eduardo Ochs
2012-09-18 18:12 ` John Hendy [this message]
2012-09-18 18:30 ` Luis Anaya
2012-09-19 15:31   ` Srinivas
2012-09-21  4:28     ` Marcelo de Moraes Serpa
2012-09-23  2:28       ` Srinivas
2012-09-25  4:26         ` Marcelo de Moraes Serpa

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=CA+M2ft_uw63tCnE1KWQQH935opL3Lcu_aNer2_Nq1LvnA-1mjA@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=celoserpa@gmail.com \
    --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).