Hi,

thanks of all your tremendous work.

Unfortunately I can't build the 'layout-basic' branch, I get

--- Using incorrect driver for hyperref! ---
Using pdflatex: specify pdftex in the hyperref options (or leave it blank).

And I don't know how to fix it. The generated .tex file already has
\usepackage[pdftex]{hyperref} in it, and changing that doesn't make the
error go away, so I suspect it's somewhere else.

Luc St-Louis wrote:
>     . Uses a lot of Nikolai Prokoschenko's general design (from the
>     "latex-tweaking" branch). One thing I did not use was the syntax
>     highlighting, as there is currently no way to correctly do it for
>     Perl6 code. 

Right, we should only include syntax highlighting if we get it right for
all the examples.

>     Also, I have not (yet) reintroduced the page
>     headers/footers he had, as these caused a bunch of "overfull
>     hboxes" that I found really annoying and could not fix (yet). The
>     .sty file also feels a less cargo-culted. Sorry Nikolai! :)
> 
>     . Incorporates Dean Serenevy's sidebar proposition ("ng" branch).
> 
>     . Can build the book in both a4 and letter paper sizes, but with
>     essentially indentical layout and with page breaks occurring in
>     the same places.
> 
>     . Uses a (modified to use the xetex engine) makefile designed for
>     LaTeX (by Chris Monson); it takes care of rerunning latex when it
>     needs to (for indexes, etc.), has easier to read error messages,
>     etc.
> 
>     . Introduces a 'test' book, to see how things look (still needs
>     work).

All of these are good news.

> At least some of the remaining problems:
> 
>     . 'programlisting', 'screen', indented: line numbers, indent, by
>     how much?

IMHO we don't need a basic indenting at all, it's just that
Pod::PseudoPod::LaTeX wants at least one leading space to properly
handle code blocks.
And we should make sure that if we quote parts of some code, it has the
same indention as where we take it from, so automatic unindenting
doesn't seem like a good idea, unless it can be really smart.

>     . Font choices: could be explored some more.
> 
>     . Some verbatim things are still broken (e.g., tildes (~) are not
>     printed, as they are interpreted as non-breaking spaces).
> 
>     . There are some LaTeX errors/warnings that I don't understand.
> 
>     . Sections and table of contents: how much numbering?

At least two levels

>     . Do we want smart quotes in the main text? (plain quotes
>     currently, I think).

I don't really care about the quotes in the main text, as long as C<...>
produces plain quotes.

> So to build the PDF book:
> 
>     . Checkout the "layout-basic" branch.
> 
>     . Invoke one of the following:
> 
>         make TEST=1
>         make
>         make TEST=1 PAPER=letter
>         make PAPER=letter
> 
> Comments welcome.

Cheers,
Moritz

Reply via email to