allendowney / thinkjava

LaTeX source for Think Java, 1st edition, by Allen Downey and Chris Mayfield.

ThinkJava

LaTeX source for Think Java, 1st edition. Copyright (c) 2016 Allen Downey and Chris Mayfield.

NOTE: This repository is no longer actively maintained. See https://github.com/ChrisMayfield/ThinkJava2 for the 2nd edition of Think Java.

Permission is granted to copy, distribute, and/or modify this work under the terms of the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License, which is available at http://creativecommons.org/licenses/by-nc-sa/3.0/.

The original form of this book is the LaTeX source code available from http://greenteapress.com/wp/think-java/ and https://github.com/AllenDowney/ThinkJava.

The illustrations were drawn using xfig (http://www.xfig.org/) and dia (https://wiki.gnome.org/Apps/Dia/). These tools are free and open-source.

Compiling the LaTeX source has the effect of generating a device-independent representation of the book, which can be converted to other formats and printed.

To compile the PDF version from source:

pdflatex thinkjava
makeindex thinkjava
pdflatex thinkjava
pdflatex thinkjava

The source code includes a Makefile that automates this process. On Linux, you will need to install texlive-latex-extra and hevea.

thinkjava's Issues

Images for O'Reilly version need to be grayscale-friendly

On page xvi, can we make a version of this with a lighter background color?

In general, we need to check what the images look like in grayscale.

Sizing information for figures is ignored

Currently we have to scale the figures by hand in production. It would be nice if Atlas would accept size information.

Figure 10.1 is broken

We don't know why. This has been an intermittent issue for a while: it was broken, then it worked for a while, now it is broken again.

Email address in the preface gets hyphenated

[email protected] gets hyphenated. Can we avoid that?

We need a way to refer to the code instructions in the preface

There is a section in the preface about how to work with the code. We want to refer to it in the exercise section at the end of the book. The current reference is not working, but we don't know why.

Code blocks should be syntax highlighted

We are working on updating our DocBook translator to generate

<programlisting language="java">

Tables need lines

We need lines between cells on all tables, especially the one that's a blank table for the reader to fill in (Exercise 9.1). If there's a way to do this in DocBook, please let me know.

Exercises should be labeled as exercises, not examples

This is a recurring issue. It would be nice if we could add this feature to Atlas rather than fixing it by hand in all of my books.

Appendices should be labeled as appendices

They are currently chapters 15-17. If there is something I can do in the DocBook to make this happen, let me know.

Style of figures is not consistent

Most of the figures were done in xfig; a few were done in dia. We are waiting for guidance about whether they will be redone in production, or whether we should make them consistent.

Issues building in Windows (MikTex)

Trying to build from latex source, on windows, using miktex-portable-2.9.6753 (selfcontained supposedly).
First I was getting errors about hevea.sty being missing, so I downloaded it from http://hevea.inria.fr/ into the book's top level folder (er, plus a few copies in the miktex tree, shotgun approach, having forgotten most of what I ever knew about LaTeX). That seems to have fixed the hevea issue.

Now I'm seeing this:

! LaTeX Error: File `latexonly.tex' not found.

I'm guessing you need to commit/push this and possibly other supporting files from your own local build tree ?

Or, if there is an obvious mistake I'm making, I'd appreciate anyone pointing that out. A cursory search in the web didn't help.

TIA, Fazl

Inline code should be syntax highlighted

What DocBook should we generate for inline code?

http://chimera.labs.oreilly.com/books/1234000000058/ch02.html#syntax_highlighting