LaTeX for Linux

Author: Bernice Sacks Lipkin
Publisher: Springer Verlag
Price: $49.95 US
ISBN: 0-3879-8708-8
Reviewer: Ben Crowder
Anyone who has worked with Donald Knuth's TeX (pronounced “teck”) or Leslie Lamport's LaTeX (“lay-teck”) can tell you that both are extremely powerful but rather intimidating. LaTeX makes things easier but it's still hard for a beginner to grasp the connection between the marked-up text and the final, printed output. Enter Bernice Sacks Lipkin's LaTeX for Linux.
For those of you scratching your heads wondering what all this TeX and LaTeX stuff is, read on. Donald Knuth wrote TeX so he would be able to format his book, The Art of Computer Science, the way he wanted to. Rather than focusing on the aesthetics of the printed output, Knuth wanted authors to concentrate on the content of the material. As such, TeX is not a word processor where you say, “The section heading should be larger than the other text, so I want font Becker at 14pt, and I want it centered.” Instead, you tell TeX you want a section heading, and it automatically formats and numbers it for you. TeX is still low-level, so Leslie Lamport wrote LaTeX, a collection of higher-level TeX macros, to group some of the more common TeX commands together.
Lipkin's book is a well-written guide to the narrow, twisting path of learning LaTeX. First, I must say that the entire book was typeset using LaTeX, and as such, it provides an excellent real-life example of the various techniques within. This is a definite boon when you're trying to figure out exactly what a certain command does.
The first part of the book covers reading and understanding LaTeX. As with most programming languages, to be able to write, you must first be able to read. LaTeX is no exception. Chapter 1 covers what a LaTeX command does—the meaning of all those backslashes and curly braces. The second chapter defines concepts that TeX (and thus LaTeX) uses, such as commands, declarations, environments and scope. Chapter 3 explains LaTeX's document classes—letters, slides, articles, reports, books and so on—and how to use them.
Part II goes over things you'll need to prepare before you can start writing serious LaTeX. The fourth chapter gives you a practice template file to start working with. For die-hard Emacs fans, Chapter 5 helps you assign key bindings in Emacs to common LaTeX constructions. Since the whole point of LaTeX is to get your text into a printed (or otherwise viewable) form, the sixth chapter covers viewing and printing LaTeX files. You can convert LaTeX to HTML, text, PostScript, PDF, etc. When the inevitable errors happen, Chapter 7 will be there to help you deal with them.
The third part gets into the real meat of LaTeX. Chapter 8 covers the reserved single-character commands (such as the backslash). In the ninth chapter, we move up to single-word commands. Eventually, you'll get sick of typing the same instructions over and over again. Chapter 10 explains how to use macros and new commands to eliminate excess typing and frustration.
Part IV covers formatting text. While the default Computer Modern font LaTeX uses is nice, most people will want to use something different at times. Chapter 11 gives the nitty-gritty on everything you wanted to know about TeX's font system. When the time comes to write something in another language, you can learn from Chapter 12 how to place accents over and under characters. Like HTML, TeX and LaTeX manage spaces for you—no matter how many spaces you put between two words, LaTeX will always put in the same amount of white space. While in most cases this is a good thing, at times you'll need to tweak the amount of space, and the thirteenth chapter explains how. Chapter 14 covers lists, and Chapter 15 explains how to align and indent text.
Figures, tables and marginal notes are called “floating objects” in TeX, since you don't specify an exact location for them. Instead, you tell LaTeX about where you want it to be (i.e., the top of the page), and it takes care of the rest. Chapter 16 explains how this possibly confusing feature works. Most academic writings are littered with footnotes, so the seventeenth chapter covers those. Chapter 18 describes the cross-referencing system, and Chapter 19 explains how to add comments (text that LaTeX will ignore, used mostly for writing notes to yourself) in your LaTeX code.
LaTeX is commonly used for typesetting math equations, and that's what Part V is all about. Chapter 20 goes over the math symbols and the grammar for getting into and out of math mode. Chapter 21 covers single-line math modes, and Chapter 22 explains arrays (the multiline math mode).
The next few sections of the book consist of only one or two chapters each. Part VI covers formatting in box mode; Part VII explains how to insert pictures and graphics into your text; and Part VIII shows you how to put the finishing touches (bibliographies, tables of contents and indices) on your document. Part IX describes how to design style sheets. The book ends with two appendices—one on the construction of a root file, and the other detailing how to convert from LaTeX to HTML and vice versa.
While visual tools like LyX are available to make writing in LaTeX less painful, many times you'll need at least a basic understanding of the language in order to get the desired result. This book will give you that understanding. It is well-written, concise, informative, and laced with the occasional bit of humor. Not many books are this thorough.

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- New Products
- Linux Systems Administrator
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Web & UI Developer (JavaScript & j Query)
- Designing Electronics with Linux
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?




1 hour 47 min ago
2 hours 3 min ago
3 hours 54 min ago
9 hours 46 min ago
14 hours 18 min ago
14 hours 18 min ago
16 hours 18 min ago
1 day 1 hour ago
1 day 1 hour ago
1 day 2 hours ago