From: "Douglas Anderson" <douglasjanderson@gmail.com>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] Handbook,Devbook,etc to PDF conversation
Date: Fri, 28 Nov 2008 18:10:03 +0900 [thread overview]
Message-ID: <4511e6e80811280110habee5c6t43647ad471ffe946@mail.gmail.com> (raw)
In-Reply-To: <492FB3A2.1010705@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
On Fri, Nov 28, 2008 at 6:02 PM, Jan Kundrát <jkt@gentoo.org> wrote:
> Douglas Anderson wrote:
>
>> But there should be plenty of ways to go html > pdf
>>
>
> We don't want to provide a PDF just "so that we have a PDF", so printing a
> web page to PDF is not really an option.
>
> If you want to improve your XSLT-FO skills, feel free to write the
> stylesheets; if you manage to use only the technologies that are already
> available on our web nodes (nope, we won't open HTML in OpenOffice, thank
> you), we can give it a try.
>
> But there's no point in generating "a PDF" without all fancy features like
> a book-like layout, inter-document links etc.
>
> Why do you *need* the PDF at all?
>
>
> Cheers,
> -jkt
>
> --
> cd /local/pub && more beer > /dev/mouth
>
> Jan, sorry I kind of overquoted in my last mail, I wasn't really replying
to you. Obviously gentoo isn't going to open pages in oo! I was saying to
Behzat that, for whatever reason, if he needs a one-off copy of the handbook
in PDF, there *are* a few ways to make it by going off the html version
instead of straight from guidexml to pdf.
-Doug
[-- Attachment #2: Type: text/html, Size: 1690 bytes --]
next prev parent reply other threads:[~2008-11-28 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 8:43 [gentoo-doc] Handbook,Devbook,etc to PDF conversation Behzat Erte
2008-11-28 8:55 ` Jan Kundrát
2008-11-28 8:57 ` Douglas Anderson
2008-11-28 9:02 ` Jan Kundrát
2008-11-28 9:07 ` Behzat Erte
2008-11-28 9:10 ` Douglas Anderson [this message]
2008-11-28 9:12 ` Behzat Erte
2008-11-30 10:21 ` Josh Saddler
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=4511e6e80811280110habee5c6t43647ad471ffe946@mail.gmail.com \
--to=douglasjanderson@gmail.com \
--cc=gentoo-doc@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox