<qt>

## Color management with Scribus, an Introduction

#### Activating Color Management

For color management to function properly you need the following to be installed to be active and usable:

- Littlecms libraries installed and Scribus compiled with lcms support. You can tell by looking at Help > About Scribus and looking for C-C-T. The first C means Scribus is compiled with littlecms support. This is standard with MacOSX and Windows.
- You need a minimum of 1 RGB and 1 CMYK profile. Scribus provides two basic profiles to ensure CMS can be enabled immediately. In practical terms, you need more. One sRGB for most RGB colors and one for each color device. One for your monitor which is created with monitor profiling tools. Several CMYK profiles for printing. Some CMYK profiles are known as "press-standards", in that they represent common commercial print standards used in North America and Europe. The best bet is to download the "Windows" version of the Adobe ICC profile package and unzip it into a directory like $home/.colors/icc. Linux users can also download freely distributable profiles from the ICC downloads section on www.scribus.net
- Scribus, by default on Linux, will look in:

      $home/.color/icc

  and

      /usr/share/color/icc/

  for both personal icc profiles or system wide ones. There is a small, but growing collection of freely available icc profiles for download on www.scribus.net. Look in the Downloads > ICC section. Scribus on Windows or MacOSX will look in the default system directories. Earlier versions of Scribus will look in the directory specified in preferences.
- If you are new to color management, please look over the links and documentation on color management listed on www.scribus.net. These explain the theory and concepts far better than I could here.

#### Overview

The objective of a color management system is to reduce the differences between the on-screen colors and final printing, as well as showing colors which are out of gamut, beyond the color range of your selected printer. The caveat is you need to provide a profile of the printer and one for your monitor which is reasonably accurate. For users of other applications, the default settings and descriptions can be quite confusing to new users. Without prior knowledge of the terminology, it is very easy to choose the wrong settings. This can often makes images look worse on screen or print. Then, the first time user simply says enough and disables color management.

In a word don't. Once you understand some basic concepts and know your final print destination, you will be able to predict - and - control more reliably how your document will look when printed. This is especially helpful when you will be sending files for later reproduction with four color printing or sending hi-resolution PDFs. The type of color management support within Scribus, I believe, is the first for an open source program. Future enhancements will bring even more exact control over color reproduction. The latest CUPS versions since 1.1.15+ now have support for true CMYK color printing. The newest version of little cms 1.15 has many new features which enhance the capabilities of Scribus to more accurately display color, along with much better performance. .

The steps to making color management work reliably (what you see on screen is what you print) :

1. Learn a little bit about color management concepts and terminology. See below for links.
2. Get the profiles setup properly. Below is a listing of color tools available for Linux. The most important is getting a good accurate monitor profile. The prof profilers do an excellent job at creating monitor profiles. Here is a how to for creating ICC profiles for your monitor with the lprof profile tools. Without a properly created monitor profile, enabling color management will give you unsatisfactory results in printing and inaccurate previews on screen.
3. Embed the image profiles properly in image editing applications where possible.

The color management system within Scribus is designed foremost for enabling color managed "soft proofs" of the images within the document. Scribus can also show "out of gamut" warnings for colors which might not be accurately reproduced by printing. (Most printers, have a narrower range of colors which can be printed, when compared to most monitors.) It does not embed or alter the profiles within your images. Some image files, png and Tiff, helpfully, can have an embedded ICM or ICC profile within the file header - also known as tagged, with a color profile. Later on, we will describe how and when it might be appropriate to use littlecms or Photopaint to apply a tag or embed a profile. If a file is tagged, Scribus will work with littlecms to read that profile within the image and use that profile to more accurately display the colors within an image. If an image does not have a tag but you know the device profile which should be assigned to the image, you can still use the CMS settings to preview with the profile temporarily assigned within the document. Caution is advised not to assign the wrong profile unless you are absolutely sure of the image source.

The littlecms package has developed into a stable mature library. Independent tests vouch for its accuracy and littlecms is used within the printer firmware of some the most exotic and high end printers available. Given that this has come from a very small group of folks is really remarkably accurate considering the amount of development work done by large companies such as Kodak, Adobe, Agfa and others.

What are color or device profiles?

ICC or ICM profiles are a special type of file which describes the color characteristic of a device like a scanner, monitor or printer - basically any device which can create or display manipulate the color of a digital image. There are also color profiles which are known as device independent or working space profiles. These special files can be thought of as translators which are used to convert from one type of color profile to another. An icc or icm file is a set of tables which describes the mathematical values by which devices measure and describe color. Fortunately, these are set by open international standards and work the same way on a Mac, Windows PC, Linux or Solaris.

Device Profiles - are separate files which describe the way a device creates (scanner or digital camera), displays (monitor) or outputs (printer) colors. Users of of Photoshop will be familiar with the choice of Working Profiles or Working Space - which are color profiles not related to a particular device, but to assist in the conversion of color from one device to another. Well known RGB "working spaces" Include sRGB, Adobe® RGB 1998, Colormatch,Bruce RGB or CIERGB. Users of Photoshop or other color may be wondering if this is a missing feature, but littlecms uses its own internal color conversion process to make the transformation between color spaces. One less setting to worry about!

Why "soft proofing" ? With the proper setup of device profiles, littlecms can adjust the colors of your monitor to more accurately represent how your document will actually look when finally printed., This can be doubly helpful if you are sending it to be printed commercially or for service bureau output. Moreover, each image can be individually modified by Scribus to assign profiles in an image, ( Select image > right click > Modify ) so that it can be properly color managed in document production, such as preparing film, a PDF/X-3 or direct to plate technologies. This does not however, alter the image file internally. Preview profiles assigned to an image are part of the setting retained in a Scribus document or in the creation of a PDF. There is also are command line tools in littlecms to embed profiles with tifficc and jpegicc. See the littlecms docs for exact options. You can also embed ICC profiles using Cinepaint, Imagemagick,Krita along with Adobe Photoshop.

</qt>