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.
> The norm we use here requires .jpeg at 300 dpi and cgm
> files for the illustrations.
What seems to have been ignored in this thread thusfar is the fact that CGM is a metafile format that can handle both vector graphics and raster images, and that it can be used for print publications as well as for Web (HTML) distribution. As with the XML-standard SVG format mentioned by another poster, there are good free browser plug-ins available for end users to be able to render CGM inside their Web browser (e.g. ActiveCGM from Corel - formerly from Micrografx).
If Solena's illustrations start out as vector graphics (e.g. a CAD drawing of a Big Truck), this means that the whole discussion about resolution can be avoided altogether, since they will then automatically render at the native resolution of the display device, be it a 96dpi screen or a 1200 dpi printer. Should they be raster image (e.g. a photo of a Big Truck), then embedding it in a CGM shell means that the image will be scaled by the browser plug-in to fit within the window defined by the HTML page.
> When we generate a HTML output from our files, the .jpegs blow the whole
> thing up. We have normal text, and then the corner of a HUGE PICTURE way too
> big to display on the screen.
I would think that HTML enables you to have a JPEG images scaled on-the-fly to fit within a certain pixel space, so displaying at something else than 100% of its natural size.
In any case, it seems that it's impossible to calculate one optimal resolution for screen rendering, since the target audience is likely to use different screens with different resolutions. 72dpi, 81dpi, 96dpi, 150dpi... That also leads me to believe that you can have your HTML code fit raster images in your template. Having the browser scale down your 300dpi JPEG image will degrade the quality of on-screen rendering, but that's a fact of life with raster images.
Have you tried the latest in Help Authoring from RoboHelp?
Try ROBOHELP X5 for Free - Now with Word 2003 support, Content
Management, Multi-Author support, PDF and XML support and much more!
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -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.
