## Notes on Importing Issues with Scribus

Although Scribus imports most common page layout image formats like TIFF, EPS and more recently in Scribus PSD, over time one of the more difficult tasks in page layout is getting stuff into your layout.

In my experience, the key to this are using the right format for the right type of image. Whenever possible, import your artwork as vector via SVG, EPS PDF. The other is I am really picky about fonts. You will see this noted through the docs; when you are working with high-end DTP tools like Scribus, font quality matters. In professional pre-press and print production, it matters a lot. Experience will tell you the number one reason postscript output fails, whether to a printer or a PDF not separating properly, is a dodgy or corrupted font.

### TIFF, JPEG, PNG, PSD, GIF's what are the qualitative differences?

Hints (or) avoiding some issues which can baffle a beginner:

### If it looks good on screen it will look good on paper

Nope, sorry. One of the most common beginner mistakes is to assume a nice looking JPEG from website will print nicely on paper. 99% of the images found on the web are useless for print. Most websites use JPEGs, gifs or sadly, less commonly, PNGs. JPEGs, by their design, are lossy compression. In the process of compressing a JPEG, data is discarded and permanently lost. Every resave of a jpeg degrades quality even subtly at minimum. Moreover, there is a type of JPEG called progressive which is pure poison in a PDF/Postscript work-flow. A progressive JPEG is the type that partially displays as it is downloading in a web browser. Avoid these at all costs. Scribus will not load, nor export progressive jpegs. Lastly, remember, most web page graphics have a resolution of 72-96 DPI. Scribus can generate PDFs with 4000 dpi.

For high-level postscript printing there are three kinds of file formats that work well for images like photos and anything that is made up of pixels and have been time tested: TIFF, tif and Tiff.

No matter which way you spell it, a Tagged Image File Format is the file format for bitmap images. Period. End of story. Don't give me any arguments: I'll win.

### Why?

1. It is a "lossless" format. The compression scheme does not reduce quality.
2. For your purpose of working with Scribus, the GIMP does a fine job of exporting or saving them from the native XCF format.
3. It handles ICC profiles without problems. You can "tag" it with the little cms utility tifficc or embed an ICC profile in Photoshop, Photopaint and other bitmap editors.
4. It supports CMYK colors better than almost any other bitmap format.
5. Every high end DTP application can support them, including Scribus.
6. TIFF files, if they are prepared properly in the GIMP or Photoshop are extremely reliable when printed commercially. Rarely do postscript devices have problems with them.
7. Scribus also has good support for detecting embedded clipping paths and you can use them to allow nice effects like letting text flow around the path.

### Caveats

There are more than fifty different flavors of TIFF. Not every image editor saves them with the same fidelity to the standards. GIMP and Krita through its use of libtiff, shared with Scribus, does a fine job of supporting TIFF. The way I work with files from GIMP is to save the original file in the native GIMP xcf format and then, once edited to your satisfaction, re-save as a tiff or with screen shots meant for the web, PNG.

Now the exception to that rule is PNG, especially for application screen shots when you are making PDF for screen display for example in a training manual. PNG has a lot of advanced features, like ICC color support and real alpha transparency, which are often not supported well by some applications (a certain leading browser comes to mind). PNG also compresses very well. The only time I prefer Jpeg to PNG is for photos with high dynamic range, mostly for reasons of size on a web page. For creating PDFs with screen shots, PNG is superb and will print well, as long as you do not make any scaling adjustments which reduce the image size. So if you have a screen shot which is typically at 72-96dpi, but you need to shrink it, do so by scaling the image in the GIMP or within Scribus. Whenever you are scaling screen shots disable re-sampling in any image editor. With screen-shots you should never reduce the number of pixels or you will lose sharpness quickly.

### If it looks bad on screen, it will print terribly

EPS files or Encapsulated PostScript files. EPS files natively have no screen preview at all. EPS files are really a special subset of postscript instructions. They typically look just plain awful on screen if they have a TIFF or PICT preview embedded or are just a simple gray box. EPS have two important virtues: They print well to both high resolution printers or when creating PDFs. EPS files can be resolution independent and are the only file you can (sometimes) safely scale larger than 100% than its native size without degrading image sharpness.

The one issue you might find with EPS files is while a lot of applications can generate EPS files, not all do so with the same fidelity to high-quality printing, nor do all apps follow the EPS specs properly. One way to test an EPS for use with Scribus, is to open the EPS in GSview and look in the message box, by pressing Shift M. This will show the output messages from Ghostscript. Ghostscript is correctly quite fussy about EPS files. So, if you are trying to import EPS files and they do not work properly in Scribus and GSview/Ghostscript is spitting lots of error messages, try using a different application to generate them.

One reason for the ubiquity of EPS files in page layout is there is another page layout application which historically had poor support for TIFF and other bitmap image files, but does have good support for EPS import. So, many page layout users habitually create EPS files from bitmap images from Photoshop or others. Unfortunately, this can have the side effect of receiving image files which may need adjustment, but without the original image file - impossible. EPS is ideal for receiving vector artwork like maps, mixed with text. The caveat is the fonts should be embedded in the EPS properly to print properly from Scribus - something not all applications do well.

Fortunately for ease of use, Scribus automatically creates a low resolution preview image which is handy for placing and adjusting sizing on the page. When importing an EPS, Scribus generates a 72dpi PNG preview of the EPS, so do not be concerned if it does not look sharp right away. Printing or exporting a PDF will generate the full resolution of the file.

Skeptical about the difference between a vector and a bitmap image file ? Here is an example that you can see for yourself. Go to: http://www.isc.tamu.edu/~lewing/linux

Get the linked postscript, which is an EPS version of Tux and then right click and download one of the gifs. They are about the same in file size. Now create a new doc in Scribus with 2 regular size pages. Place the gif on one page and then the eps file on another. Export a PDF at 600+dpi. Open in Acro Reader. Zoom in 200-400 %. Now you see the difference...

Why the difference? Scribus creates and Acrobat Reader renders something called postscript operators - another fancy name for using math in drawing curves on screen and when printed. A gif, or JPEG is just a bunch of pixels, literally dots to create the image.

### My New Favorite File Formats

With the recent addition of SVG import, this gives users one more excellent way of importing artwork. SVG - Scalable Vector Graphics. Scalable is great because well it is scalable, meaning you can in theory enlarge the the graphic to the size of the side of a house and it would retain its sharpness. Vector is how it does it, vectors meaning the shapes are drawn by mathematical commands to greatly simplify. More on the next page on some neat importing tricks. While Scribus does not yet support every feature in SVG, it is improving steadily and will see further improvement in the future no doubt.

### Think About Fonts When Importing Too

A similar issue is the fonts look good on screen, but do not print well. Usually, this is the case of freeware TrueType fonts, downloaded from the web. TrueType fonts, on average will look better on screen, but may not print with the intended results. However, it takes a huge amount of time and QA to create high-quality fonts, especially correctly hinting TrueType fonts. Notice that there are very few high-quality fonts which have been developed in open source. There are a few, but sadly not with the regularity which we see new apps pop up on Freshmeat.

Conversely, the Type 1 fonts included with Ghostscript are not optimized for on-screen appearance, but they usually make excellent printer fonts. The fonts actually were made by URW++, a well regarded type foundry and were donated to the Ghostscript distribution by Artifex. The only issue is when the Nimbus fonts - their true postscript names are often aliased to Times, Helvetica and Courier. This results in a user thinking it is not necessary to embed these fonts as they come standard with Acrobat Reader. Unfortunately, if they are not embedded Acro Reader does a particularly poor job of emulating these with its built-in multi-master fonts. With Scribus, you will not have this worry, as Scribus uses the correct PostScript name embedded in the font.

The Bitstream fonts included with Xfree86 like Charter and the new Vera fonts are fine fonts for printing. I also like the Utopia family which is actually an Adobe Type 1 font donated by IBM. When creating Scribus docs in PDF form, I pretty much use this family exclusively.