CTAN update: xcolor 2.01

CTAN Announcements ctan-ann at dante.de
Tue Mar 15 23:18:32 CET 2005

On Tue, 15 Mar 2005 Uwe Kern submitted version 2.01 of his xcolor package
to CTAN.

Location on CTAN: macros/latex/contrib/xcolor/
Summary description: Driver-independent color extensions for LaTeX and pdfLaTeX
License type: lppl

Announcement text:
2005/03/15 v2.01
* New features:
    - `prologue' option for comprehensive `named' color support in
      conjunction with `dvips': on-the-fly generation of PostScript
      prologue files with all color definitions, ready for dvips
      inclusion and/or post-processing with device-specific parameters
      (e.g., spot colors);
    - dvips prologue file xcolor.pro to support additional `named'
    - \colorlet may now also be used to create named colors from
      arbitrary color expressions;
    - enhanced color definition syntax to allow for target-model
      specific color parameters, e.g.
      \definecolor{red}{rgb/cmyk}{1,0,0/0,1,1,0}, facilitating the
      usage of tailor-made colors both for displays and printers;
    - `deferred definition' of colors: \preparecolor and
      \definecolors enable decoupling of color specification and control
      sequence generation, especially useful (= memory saving) for large
      lists of colors, of which only a few names are actually used;
    - `dvipsnames*' and `svgnames*' options to support deferred
* Changes:
    - higher accuracy: most complement calculations are now exact for
      all 5-digit decimals;
    - \rangeRGB and similar variables may now be changed at any point
      in a document;
    - \aftergroupdef now performs only a first-level expansion of its
      code argument;
    - \XCfileversion and similar internal constants removed from .sty
      and .def files;
    - improved memory management (reduced generation of `multiletter
      control sequences' by \@ifundefined tests);
    - several internal macros improved and/or renamed.
* Bugfixes:
    - \XC at getcolor could cause unwanted spaces when \psset was used
      inside |pspicture| environments (`pstricks');
    - arithmetic overflow could happen when too many decimal digits
      were used within color parameters, e.g. as a result of `fp'

Thanks for the update.

For the CTAN Team
  Rainer Schöpf

More information about the Ctan-ann mailing list