Making TeX Work
Author: Norman Walsh
Publisher: O'Reilly & Associates, Inc.
Reviewer: Vince Skahan
I'm an O'Reilly & Associates fan; a big fan. I went through my bookcases at home and at work and counted 19 different O'Reilly books that I've purchased with my own hard-earned cash. I refer to them almost daily.
I have one of the major commercial technical publishing packages available to me at work. I have a copy of Microsoft Word for Windows at home. I like their WYSIWYG look and feel and I like their intrinsic (to me at least) ease of use.
I'm admittedly not a big TeX fan at all; and I even participate quite a bit in the Linux DOC Project, which uses LaTeX as its document mark-up language of choice.
OK, call me a Linux heretic.
I was looking at this book as an opportunity to learn about all the little gotchas that just aren't made visible except by oral tradition from guru to wanna-be. Maybe after reading the book and trying some things, I'll be less TeX challenged. Naaaaahhhh...
Making TeX Work is a book that somehow disappoints me. The book follows the normal exceptionally high quality O'Reilly & Associates standards for organization, format, binding, and appearance. There's 469 pages simply chock-full of information regarding TeX and associated utilities. I just never figured out why a generic Linux user needs to buy it.
The Summer 1994 'ora.com' catalog/magazine from O'Reilly & Associates has an article on this book that describes it as “a complete reference to this complex typesetting system”. It also states:
“We didn't want to do the same kind of book so many other people had written; describing the TeX language itself and how you can use it to write your documents in one of the many flavors of TeX macro languages... instead of writing a book on TeX, the text processor, we'd write a book on the entire TeX system.”
Cool—a book on how to put all the pieces together and make a document happen...
Later in the article, they mention that:
“In addition to the basic TeX program itself, you need many other tools to write even a moderately complete TeX document. You need to understand how TeX uses macro packages and format files, fonts, pictures, figures, and a host of utilities... ”
Hey wait a minute. I'm getting this feeling it won't have hands-on examples...
“Making TeX Work guides you through this maze of tools and tells you how you can obtain them...”
Danger Will Robinson! Sounds like a how to find TeX sources FAQ...
The Big Picture describes what TeX is and what its goals are. It describes a little about how TeX formats pages to look nice, about the differences between text formatting, word processing and desktop publishing, and describes the underlying guts of how TeX does its magic. It's ugly in there, kiddies...
Editing briefly describes some of the usual editors that have varying abilities to provide a good environment for writing TeX documents.
This chapter disappointed me somewhat as I was looking for more information regarding exactly how to do something in typical editors. I was hoping that they'd pick an editor (even [ugh...] Emacs) and give some real details regarding how to hook in and use the editor to efficiently write TeX documents.
Running TeX describes how to execute the program and deal with some of the most common errors in the documents.
Macro Packages describes some of the different formats such as TeX, LaTeX, and TeXinfo as well as some of the more obscure special purpose formats such as MusicTeX. While I found them interesting, there is probably nothing here that you can't find out about elsewhere on Usenet.
There were some comments about how to do TeX in color and how to print 'em on a black and white printer that I found rather interesting.
Fonts describes in laborious detail more than any sane person would want to know about font selection and generation. While it's a nice amount of background information, it sure scared the heck out of me, and I'm probably a typical member of the book's target audience.
Pictures and Figures talks a little about the fact that if you try hard enough, you can draw pictures in TeX. It also gives a few examples about how to include external images in your document.
One nice addition is a description of some of the many image generation, viewer, editor, and manipulation programs commonly available such as xv and ImageMagick. People who plan to provide WorldWideWeb pages with embedded graphics might be interested in this chapter even if TeX and friends scare you off.
International Considerations describes the issues (and tools to deal with them) involved in writing nonEnglish documents in TeX.
Printing talks about utilities that generate the appropriate fonts to be able to print what you can preview.
Previewing describes some of the various viewers for MS-Windows, X, DOS (non-Windows), and Unix terminals.
Online Documentation talks about how to make your TeX documentation available online in some of the more common formats such as TeXinfo, HTML, or ASCII.
Introducing METAFONT describes the mechanics of building non-standard fonts. Again, I wonder whether this issue isn't far beyond the probable ability (or interest) of the book's target audience.
Bibliographies, Indexes, and Glossaries talks about how to use BibTeX to automate citations of references into a bibliography and also about many of the utilities available to automate the creation and manipulation of a bibliography database. It also describes how to construct an index and glossary by annotating your TeX documents.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide