From: Yuri Khan <yuri.v.khan@gmail.com>
To: Sharon Kimble <boudiccas@skimble.plus.com>
Cc: Sam Halliday <sam.halliday@gmail.com>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: project-management
Date: Wed, 18 Feb 2015 09:09:13 +0700 [thread overview]
Message-ID: <CAP_d_8UM=tY8vip3T1g-7Hhu6+Whuy3ifWTY9b1mdq15uhJukQ@mail.gmail.com> (raw)
In-Reply-To: <871tlo9yj9.fsf@skimble.plus.com>
On Wed, Feb 18, 2015 at 12:35 AM, Sharon Kimble
<boudiccas@skimble.plus.com> wrote:
>> On Tuesday, 17 February 2015 05:54:40 UTC, Sharon Kimble wrote:
>>> I'm writing several ebooks at present, and also maintain the
>>> documentation of a couple of projects, all done in latex. I'm now
>>> finding a problem in "project management".
>>
>> But the big thing for your particular use case, assuming you haven't
>> already seen it, is org-mode[2].
>>
> Thanks, but org-mode doesn't give me the fine control that I get
> with latex. I've tried writing an ebook with org-mode, and I just
> ended up feeling very restricted. Only writing it direct into latex
> fulfils my needs and gives me the ability to fine-tune the output to
> give exceedingly good pdf's.
Please be aware that ebooks mean much more than pdfs, even if they are
fine-tuned to be exceedingly good. Many readers will prefer formats
that are readable in any font of any size, any color on any
background, in a viewport of arbitrary width, not locked into
\documentclass[10pt,a4paper]{book}.
next prev parent reply other threads:[~2015-02-18 2:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.225.1424152477.31049.help-gnu-emacs@gnu.org>
2015-02-17 18:01 ` project-management Sam Halliday
2015-02-17 18:35 ` project-management Sharon Kimble
2015-02-18 2:09 ` Yuri Khan [this message]
2015-02-17 5:54 project-management Sharon Kimble
2015-02-17 9:50 ` project-management Eric Abrahamsen
2015-02-17 14:27 ` project-management Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP_d_8UM=tY8vip3T1g-7Hhu6+Whuy3ifWTY9b1mdq15uhJukQ@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=boudiccas@skimble.plus.com \
--cc=help-gnu-emacs@gnu.org \
--cc=sam.halliday@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.