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.
John Feld <johnfeld -at- ARTNET -dot- NET> recommends:
>I recomend TIF always, and of course GIF/JPEG for web uses.
This got me thinking. I tend to choose a graphic format mostly by what my
platform supports. Then I balance image quality with disk storage. This is
not always easy.
--When I wrote paper manuals, our manuals became increasingly
graphics-heavy as the products evolved from text-only to GUI.
Our manuals did not increase significantly in length, but they
devoured increasingly large amounts of disk. We used UNIX's
XWD format by default -- it was the only format we could
figure out how to generate on our X/Mosaic/AIX system. XWD
screen captures, even of small windows, took up ridiculous
amounts of space. Compressing the manuals helped, of
course -- but even when compressed, a 100-page manual with
XWD screen shots was larger than an uncompressed 100-page
manual with the old Mac PICT screen shots of character screens.
--When I edited computer books, I submitted final manuscript
and graphics to Production on floppy disks. Production
accepted PICT, PCX, TIF, and BMP. I always converted to PCX
because it created the most compact files -- and the smallest
number of floppies per project. (It's a major pain to make
the darned floppies; you want to spend as little time at it
as possible. Or shove the job off on an assistant! :->)
--My Internet service provider includes Web page space as part
of its basic service, with a 10MB storage limit. I'm working
with another guy to create an Indiana radio and TV dial site,
a history of Indiana broadcasting by station. We want to
include station logos when we can, but neither of us wants
to pay the high rates for storage beyond 10MB. I'm using
GIF; it gives me the files even more compact than JPG at
greatest compression (supported by LView Pro, my graphics
massager of choice).
--I'm writing online help for Windows at this company.
Confoundingly, the Help engine seems to support only BMP
graphics, which aren't exactly compact. We compile with
compression, which makes our HLP file compact -- but the
source directories still get huge. I wish the help
compiler supported PCX.
jim grey |"Ain't nothin' better in the world, you know
jimgrey -at- iquest -dot- net|Than lyin' in the sun, listenin' to the radio!"
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-