Maybe this has been said before.

26000 PDF. It says it's version 1.0 however in looking over the errata, it seems to be 1.2. There are several interesting typos in the book (extra spaces, double commas). Specifically the "Defiance" weapon is what jumped out today. It's "Defi ance" with a space. Made it hard to find It wasn't fixed in the 1.5 errata and I haven't seen a newer one on the site yet.

Another note. For those of us who are blinder (and older), it's probably not possible to have a single column for the PDF vs matching the book exactly but it sure would make it easier to read it vs using it as a reference during games.

And I know it isn't your fault, but as an observation, the Windows adobe viewer sucks vs the Mac preview tool. Good thing I use the Mac laptop for gaming but it makes it hard to read while on the Windows box (again, nothing you can do about it but it is annoying and I'm venting a little ).

Carl

Yeah, Adobe's initial foray into the Vista realm also sucks on some rather fetid phallic images. I recommend PDF xchange viewer.
It loads fast, lets you edit and save and generally behaves much better.

Ok cool. Then I can update the PDF with the errata and be up to date. Thanks

Carl

Basically any common ligatures: fi, ff, fl, fj, th, etc. When books are laid out with modern OpenType fonts that have ligatures, in applications that support them, those dual-characters get turned into one character, and that does hork with searchability of PDFs.

There is little chance of Catalyst taking the time to re-layout books in a more screen-friendly format for PDF sale. The additional production time would probably not be made up for with additional sales, especially as we would still have to provide a print-formatted PDF as well.

I understand why people want it, and I'd like to serve those people, but I just don't know if we can do it in a way that serves both those fans and the company. I'll do some further looking into it ... in my copious free time.

Ok that makes sense thanks.

As to the layouts, I understand. I was just venting a little. It does make it a little difficult to have to jump up and down to _read_ vs using it as a resource. I do read the books but when I'm travelling or off doing something (like skiing), I don't want to have to lug around several books

Plus add in the page number change (so you can't jump around) mucking up with the TOC and index so I fully understand.

Carl

Adam, do not change the 2-column layout. That 1 column is exactly the width of an HP Pocket PC screen. It's perfect for reading on the road.

What do you think?

What about print-friendly pdf's? I've had nothing but nightmares trying to print out SR4 products, and there's been multiple other complaints on RPG.net. For example, the quickstart rules are absolutely beautiful, but 20 pages of intensive color graphics is enough to choke any printer. And Quickstart rules are *meant* to be printed out!

It wouldn't take much to do what Pinnacle does to their pdf's: they bundle two versions together, one in glorious full color, the other in a stripped-down version with no backgrounds, simplified or shrunk artwork, and less layering.

I haven't had any problems sending the files to print. If you are having issues with your specific printer, I'd recommend downsampling the images, Also, double check that the "Print as Image" box is unchecked. If the printer is reading all of the text as a 300-600 DPI image, that may choke things.

Beyond that, my professional opinion is that the problem is based on the amount of data your computer is sending in a single pass compared to the internal memory of your printer. Reconfigure your print drivers to make sure Adobe isn't doing a 75 mb data dump into a 64 mb printer.

Regarding inkjets, try setting the printer to print in grayscale or something along those lines and drop the resolution to "draft" or whatever the minimum is.

I find the spaces irritating myself, being a screen reader user (converts text to speech for people with little or no vision). My solution to that has been to convert to a text file then make corrections with find/replace, but if I can get a linux set up working I might try to set up a script to automate this with the most common errors.