# STM publishing: tools, technologies and changeA WordPress site for STM Publishing

10Nov/13Off

## Xpost: New open source PostScript interpreter being developed

#### Posted by Graham Douglas

Just a brief post to note that a new PostScript interpreter, called Xpost, is being developed. For details see announcement on Google Groups. Definitely one I shall be following.

29Oct/13Off

## Quick tip: Decompressing PDFs for Debugging

#### Posted by Graham Douglas

If you are creating special effects in PDFs (e.g., using pdfTeX's \pdfliteral{...} or via \special{...}) it can be extremely helpful to see the raw PDF code being output by your code/macros etc – especially when debugging! Often, by default, PDF content streams are compressed/encoded into binary data which makes it extremely difficult to access the raw PDF data/content. However, you can use the recently released free community version of Coherent's excellent command-line PDF manipulation software to decompress the binary data into plain text. It's as simple as:

cpdf -decompress compressedfile.pdf -o decompressedfile.pdf

cpdf has a wealth of other interesting command-line options too.

17Oct/13Off

## Unicode Version 6.3 is Published

#### Posted by Graham Douglas

Title of the post says it all really. Perhaps the most interesting change is the improved Unicode Bidirectional Algorithm together with a new reference implementation in C.

5Sep/13Off

## Commercial tools to manipulate PDF files now made “free”

#### Posted by Graham Douglas

Just read a newsgroup posting about a set of commercial PDF manipulation tools that have been made free-to-use for non-commercial activities. If you need to process PDFs, especially in a batch/scripted environment, then these could be well worth checking out.

Coherent PDF Command Line Tools Community Release

2Sep/13Off

## Small but significant bug-fix for DVIPS

#### Posted by Graham Douglas

A small but important bug-fix for DVIPS has been reported on the tex-k mailing list --- see this thread. If you use DVIPS and GhostScript to produce PDFs for commercial printing you may well want to read the thread and consider upgrading your DVIPS executable to contain this fix (by Akira Kakuto).

24Feb/12Off

## A few recollections from my freelance days

#### Posted by Graham Douglas

A slight departure from the usual posts on this blog

In the early 1990s, before large-scale offshoring came into play, I started working freelance, editing and typesetting technical books using Windows-based software (FrameMaker, before Adobe bought it) and certainly prior to PDF as the only way to transfer files to printers and "film bureaux". Film, remember that? Positive/negative, right/wrong reading emulsion side down... Printers and bureaux were dominated by the Macintosh (maybe they still are) so without the common use of PDF, transferring Windows-generated typeset material/files to commercial printers was, at times, a bit of a nightmare. I was working for a number of big book publishers who all used different printers, each with their own requirements for accepting electronic files which inevitably meant PostScript if you were working on a PC.

I still have vivid memories of generating and shipping hundreds of megabytes of raw PostScript code using SyQuest drives: then the only "high capacity" removable media accepted by printers. Ubiquitous, low cost, high-speed electronic transfer of huge amounts of data was still in the future, unless you had ISDN, which I didn't and couldn't afford. My first forays into the online world was the Bulletin Board and CompuServe and I was the proud owner of a US Robotics Sportster 14,400 Fax modem. I remember the joys of the Hayes command set, 7 or 8 bit data, odd or even parity and all the weird arcania of comms technology of the time. Enough already, too many memories!

Incidentally, a single 88 MB SyQuest disk cost (from memory) around £60 in the early to mid 1990s! I confess that I hated using SyQuest drives because you could never be sure that a disk formatted for the PC could be mounted (i.e., opened) on a Macintosh at the printers due to disk formatting issues. After generating 500MB of PostSript data and couriering it across the Atlantic to meet a deadline you don't want to hear that your disks can't be read. The introduction of the Iomega ZIP drive was a blessing and wiped out SyQuest's market, virtually overnight. Whenever I recall SyQuest drives I cannot help but think of the Trabant. Yes I should have used a Mac, maybe, but the vast majority of Word files (for technical books) I received from publishers were generated on a PC: in an era when transferring Word files between Mac to Windows was not always a "joy" and cleaning up the "converted" Word files could be a lot of work.

Generating reliable PostScript code via the Windows 3.1 PostScript printer driver was an excercise in the darkest arts and the main reason I had to become, at the time, expert in PostScript programming: to understand what was going on and how all those bizarre options in the print dialog box affected the PostScript code. Page independence, VM memory in the printer and a host of other settings which made the difference in getting the PostScript to RIP successfully, or not. I recall the "font wars" of TrueType vs Adobe Type 1 font file formats: "Type 1 rules, TrueType sucks" was an oft-quoted mantra of the times and certainly the conversion of TrueType fonts for inclusion in the PostScript data stream was not always without hassles...

Anyway, enough of this. Monty Python Yorkshire Man sketch, anybody?