| Home | Company | Contacts | Products | Support | News | Index |
HELIOS report about known problems with applications
|
The following table contains some well-known applications that may produce problems when being used with one or the other HELIOS software.
Please note that this page is under constant construction. HELIOS does not guarantee completeness, currentness, and correctness. See also: |
| Application | EtherShare | EtherShare OPI | PDF Handshake | Print Preview | PCShare |
| FrameMaker | -- | -- | -- | X | -- |
| PageMaker | -- | X | -- | -- | -- |
| QuarkXPress | -- | X | -- | -- | -- |
| Photoshop | -- | X | -- | X | -- |
| FreeHand | -- | X | -- | X | -- |
| Illustrator | -- | -- | -- | X | -- |
EtherShare OPI/Photoshop
EtherShare OPI 2.1 does not support layer masks saved in Photoshop Native format. When using layer masks in Photoshop and saving the images as Photoshop Native, blank layout images will be generated. Please apply any layer mask to its layer and remove it before saving the image.
EtherShare OPI/QuarkXPress
We found that QuarkXPress matches spot color names found in placed EPSF files to its own ones by comparing the names of the imported colors with the built-in color tables. The program sometimes matches names which are only partial identical and then continues using its own names when editing colors and printing. This may result in missing spot color plates because the plate printed by QuarkXPress does not match the spot color name in the image. To avoid such problems, you should rename the spot colors in your images.
An example:
An image generated by Adobe Photoshop includes a channel named "PANTONE Orange 021 CVC". QuarkXPress matches it to "PANTONE Orange 021 CV" in its own table and uses this name further on. While printing, a plate named "PANTONE Orange 021 CV" will be printed but no OPI image replacement can be done because of the different name stored in the image. For PC-EPSF format DCS images in QuarkXPress, printing separations will cause problems when you include images in the print job. "Omit TIFF & EPS" must be selected. Otherwise, QuarkXPress will generate bad PostScript.
EtherShare OPI/PageMaker
PageMaker 6.x: We found that Adobe PageMaker 6.x silently removes the preview part of placed EtherShare OPI 2.1 EPSF/DCS layout files during printout. On EtherShare printer queues with OPI and Print Layout Images switched on, no previews of EtherShare OPI 2.1 layout images will be available, so that blanks will occur on the printouts. Printing high-resolution images on an OPI printer queue will work fine.
PageMaker 5.0 (PC): When placing EtherShare OPI layouts in PC-EPSF format using a LZW-compressed TIFF screen preview, the preview will be displayed distorted on the monitor. Printing will work properly – unless you choose to print Separations. In that case, PageMaker 5.0 will generate bad PostScript. When scaling a page for printing (to more or less than 100%), OPI TIFF image replacement will be done but the images will keep their size as if the page were printed 100%. This is also due to a problem in PageMaker 5.0.
EtherShare OPI/FreeHand
We found that Aldus FreeHand 3.1 may damage the binary parts of OPI 2.1 layout files placed in FreeHand 3.1 documents. This will cause partial printouts on EtherShare OPI 2.1 printer queues. The same applies to EPSF files exported from FreeHand 3.1.
Print Preview / Photoshop, FreeHand, Illustrator, InDesign
For preview generation, Print Preview must rely on the data that come from the application you have used for printing. Sometimes, if you print e.g. separations, it may happen that the application sends correct data for the separation plates, but insufficient information for the calculation of a composite impression; the composite preview in the preview file may be corrupt then. We have printed separations from FreeHand 8/9/10 on Macintosh, Photoshop 5.x/6.0 on Macintosh, and Illustrator 7/8/9 on Macintosh. We found that the separation plates in the preview file (Cyan, Magenta, Yellow, Black) were correct, but a composite preview was incorrect. However, InDesign 1.5.2 (with Adobe PS 8.7.2 printer driver) worked fine. By the way, FreeHand 8 on Windows 95 worked fine.
Again, for preview generation, Print Preview must rely on the data that come from the application you have used for printing. If you print e.g. composite, it may happen that the application sends correct data for the composite impression, but insufficient information for the calculation of the separation plates. We have printed composite from FrameMaker 5.5/6.0 on Macintosh. The composite preview is correct, but the separations are not. Some paragraphs of the black text appear on the Cyan, Magenta, and Yellow separation plates. Some paragraphs appear on the Black plate only – which is correct.
| Home | Company | Contacts | Products | Support | News | Index |