[lxml-dev] Generating PDF documentation

[Marcin Kasperski]

"Stefan Behnel" <stefan_ml at behnel.de> writes:

> Marcin Kasperski schrieb:
>>> That means we're at 435 pages now. :)
>>
>> I'd strongly consider publishing two separate PDFs. 435 is a bit too
>> much to print and API refs are less useful in print than tutorials and
>> design docs.
>
> True. What about just moving the generated stuff to the end of the PDF?
> That way, you can print the file up to page X (somewhere around 200) if
> you want to print it, but you'd still have everything in one file to carry
> around and do a text search.

Table of contents will still be polluted, plus ... partial printing is
amazingly error-prone (the fact that printed page numbers mismatch with
PDF-browser page numbers is one of the factors).

IMO it would be nice to have two PDF - lxml Developer Guide (or so)
and lxml Reference.

As a sidenote: I am not sure whether 'Changes' chapter is at all needed
in PDF, this is 30 pages of information nobody is likely to read.

-- 
----------------------------------------------------------------------
| Marcin Kasperski   | Communication takes place between people,
| http://mekk.waw.pl |      documents are secondary. (Booch)
|                    |
----------------------------------------------------------------------