TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
RE: PageMaker 6.52 to HP 8550--problems? solutions?
Subject:RE: PageMaker 6.52 to HP 8550--problems? solutions? From:"Dick Margulis" <margulis -at- mail -dot- fiam -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 29 Jan 2001 09:23:07 -0500
Marguerite (and all),
Well, yes, it's Monday morning, and I've sort of solved the problem. Would you believe I solved it by READING THE README FILE?!?!?!?!? (And whatever happened to the interrobang, anyway?)
Turns out that the driver HP furnishes doesn't work. The readme file instructs you to go to the Adobe site and download the latest Adobe PS driver and install that, instead.
There are still some font anomalies I've chasing down, but I was able to work around them, after a fashion, and get some production done over the weekend.
The machine is choking on symbol fonts (sometimes, not always) and throwing PostScript errors; but at least I'm no longer tearing out what little remains of my hair.
Thanks, everyone, for your well-meaning suggestions. Some of them sent me looking in the right direction.
Dick
Marguerite Krupp wrote:
>Dick,
>
>It's Monday, so you've probably solved your problem by now, but that's
>exactly what happened to me. The font seemed OK on screen, and in print, it
>was OK in some places but not in others. It turned out that in the history
>of the book, someone had made changes to the text in the graphics and had
>used a font that LOOKED LIKE, but was not the same as, the font that the
>printer liked. The solution was to go through each piece of text in the
>graphic and verify that the font was something for which the printer had the
>appropriate font loaded. Tedious, but it eventually worked. I hope your
>situation yields to a simpler solution!
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-Based Help with Macromedia Dreamweaver 4 ($100 STC Discount)
**WEST COAST LOCATIONS** San Jose (Mar 1-2), San Francisco (Apr 16-17) http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by DigiPub Solutions Corp, producers of PDF 2001
Conference East, June 4-5, Baltimore/Washington D.C. area. http://www.pdfconference.com or toll-free 877/278-2131.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
