public inbox for gentoo-doc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Behzat Erte" <b3hzat@gmail.com>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] Handbook,Devbook,etc to PDF conversation
Date: Fri, 28 Nov 2008 11:07:54 +0200	[thread overview]
Message-ID: <c83f72c70811280107o12e4d1a1n74c1d61e5bc5cdb9@mail.gmail.com> (raw)
In-Reply-To: <492FB3A2.1010705@gentoo.org>

Hello again,

I want to printing all related gentoo books and reduce to -really-
book. At this juncture PDF type is a example. May be it should be djvu
or something else type.

Regards,
Behzat.

2008/11/28 Jan Kundrát <jkt@gentoo.org>:
> 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
>
>



  reply	other threads:[~2008-11-28  9:07 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 [this message]
2008-11-28  9:10       ` Douglas Anderson
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=c83f72c70811280107o12e4d1a1n74c1d61e5bc5cdb9@mail.gmail.com \
    --to=b3hzat@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