[latex3-commits] [l3svn] branch master updated: Extend internal colour model [ci skip]

[noreply at latex-project.org]

This is an automated email from the git hooks/post-receive script.

joseph pushed a commit to branch master
in repository l3svn.

The following commit(s) were added to refs/heads/master by this push:
       new  026a9d6   Extend internal colour model [ci skip]
026a9d6 is described below

commit 026a9d61befcf468b4ac91c81f1e6e622b02588e
Author: Joseph Wright <joseph.wright at morningstar2.co.uk>
Date:   Mon Sep 25 21:33:13 2017 +0100

    Extend internal colour model [ci skip]
    
    This is a purely documentation change at this stage: allow for more models.
    
    The thinking here is that this will cover spot colours and mixing of such colours
    (see colorspace package for examples). It will also cover tints of spot colours:
    I have included a mandatory 'amount' of spot.
    
    I am retaining spaces as separators: this is closer to the dvips/PostScript/PDF
    approach than commas, and is arguably more readable for this rather special case.
    We can always revisit that: currently this is purely internal.
    
    The second phase of this change will take place in l3drivers: code is needed
    there.
---
 l3kernel/l3color.dtx |   26 +++++++++++++++++++-------
 1 file changed, 19 insertions(+), 7 deletions(-)

diff --git a/l3kernel/l3color.dtx b/l3kernel/l3color.dtx
index 607189e..85a4c2e 100644
--- a/l3kernel/l3color.dtx
+++ b/l3kernel/l3color.dtx
@@ -78,22 +78,34 @@
 %
 % \subsection{Internal functions}
 %
-% \begin{variable}[added = 2017-06-15]{\l__color_current_tl}
+% \begin{variable}[added = 2017-06-15, updated = 2017-09-23]
+%   {\l__color_current_tl}
 %   The color currently active for foreground (text, \emph{etc.}) material.
 %   This is stored in the form of a color model followed by one or more
-%   values in the range $[0,1]$: these determine the color. The model and
-%   applicable data format must be one of the following:
+%   values. There are four pre-defined models, three of which take numerical
+%   values in the range $[0,1]$:
 %   \begin{itemize}
 %     \item \texttt{gray \meta{gray}} Grayscale color with the \meta{gray}
 %       value running from $0$ (fully black) to $1$ (fully white)
 %     \item \texttt{cmyk \meta{cyan} \meta{magenta} \meta{yellow} \meta{black}}
 %     \item \texttt{rgb \meta{red} \meta{green} \meta{blue}}
 %   \end{itemize}
-%   Notice that the value are separated by spaces.
+%   Notice that the value are separated by spaces. There is a fourth pre-defined
+%   model using a string value and a numerical one:
+%   \begin{itemize}
+%     \item \texttt{named \meta{name} \meta{tint}}
+%   \end{itemize}
+%   where the \meta{name} should be a pre-defined string color name and the
+%   \meta{tint} should be in the range $[0,1]$.
+%
+%   Additional color models may be defined based on mixing of named colors:
+%   these will generally follow the pattern of the standard \texttt{cmyk}
+%   model but with each value representing the contribution of a named (spot)
+%   color.
 %   \begin{texnote}
-%     This format is the native one for \texttt{dvips} color specials:
-%     other drivers are expected to convert to their own format when
-%     writing color data to output.
+%     This format is based on that for \texttt{dvips} color specials, extended
+%     to cover additional types. Each driver should provide appropriate
+%     conversion to their native format at the point of output.
 %   \end{texnote}
 % \end{variable}
 %

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.