From: Eduardo Mercovich <eduardo@mercovich.net>
To: Philip Hudson <phil.hudson@iname.com>
Cc: Nick Dokos <ndokos@gmail.com>,
emacs orgmode-mailinglist <emacs-orgmode@gnu.org>
Subject: Re: PDF font
Date: Tue, 11 Oct 2016 17:55:31 -0300 [thread overview]
Message-ID: <874m4ivc58.fsf@biologica.mercovich.net> (raw)
In-Reply-To: <CAJ1MqVFq6=8BAp9DUn9C+rMKAtP42=LkKrQemcJCesVyZ2qpoA@mail.gmail.com>
Hi Philip.
[...]
>>> What *do* you need exactly?
>> Cantarell for the sans-serif, FreeSerif for the serif, don't care
>> about the mono.
> Oh yes, and #cccccc for the title background.
HTML is easier to style, yes. Does that format, exported to pdf, has
what you need? Because latex may take more effort, but it's only once.
Then, you have pdfs with the index, pages of the size you'd like,
everything packaged in 1 file (or not), metadata, and so on.
I tried a bit of HTML as documents, but the un-packaged nature of it
(document + images + css + etc.) always gave me problems with other
people. Self contained pdfs, on the other hand, just work in every OS.
If the only specs you'd like to change are just those fonts, and
something like Memoir starts with a decent general layout (depending on
your needs), then it makes sense to tweak it a bit and from then on,
just use the latex export.
Best...
--
eduardo mercovich
Donde se cruzan tus talentos
con las necesidades del mundo,
ahí está tu vocación.
next prev parent reply other threads:[~2016-10-11 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 21:35 PDF font Philip Hudson
2016-10-07 22:14 ` Nick Dokos
2016-10-07 23:22 ` Philip Hudson
2016-10-08 2:31 ` Nick Dokos
2016-10-08 8:19 ` Philip Hudson
2016-10-08 8:22 ` Philip Hudson
2016-10-11 20:55 ` Eduardo Mercovich [this message]
2016-10-12 9:18 ` Philip Hudson
2016-10-12 21:09 ` Eduardo Mercovich
[not found] <3733d20cae0c43aca58cb6a26352777b@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-12 7:14 ` Eric S Fraga
2016-10-12 9:06 ` Philip Hudson
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=874m4ivc58.fsf@biologica.mercovich.net \
--to=eduardo@mercovich.net \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.com \
--cc=phil.hudson@iname.com \
/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).