summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/tex/context/base/colo-ext.mkiv
blob: af6c3830eccfae5221b3c55a87ba9b77672207b8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
%D \module
%D   [       file=colo-ext, % mostof thsi code used to be in colo-ini.tex
%D        version=1997.04.01,
%D          title=\CONTEXT\ Color Macros,
%D       subtitle=Extras,
%D         author=Hans Hagen,
%D           date=\currentdate,
%D      copyright={PRAGMA ADE \& \CONTEXT\ Development Team}]
%C
%C This module is part of the \CONTEXT\ macro||package and is
%C therefore copyrighted by \PRAGMA. See mreadme.pdf for
%C details.

\writestatus{loading}{ConTeXt Color Macros / Extras}

\unprotect

%D \macros
%D   {negatecolorcomponent, negativecolorbox}
%D
%D Sometimes, especially when we deal with typesetting
%D devices, we want to reverse the color scheme. Instead of
%D recalculating all those colors, we use a quick and dirty
%D approach:
%D
%D \starttyping
%D \negativecolorbox0
%D \stoptyping
%D
%D will negate the colors in box zero.

% \unexpanded\def\negatecolorbox#1%
%   {\setbox#1\hbox
%      {\startnegative % might change
%       \startcolor[\s!white]\vrule\!!height\ht#1\!!depth\dp#1\!!width\wd#1\stopcolor
%       \hskip-\wd#1%
%       \box#1%
%       \stopnegative}}

\unexpanded\def\negatecolorbox#1%
  {\setbox#1\hbox
     {\startnegative % might change
%       \startcolor[\s!white]\vrule\!!height\ht#1\!!depth\dp#1\!!width\wd#1\stopcolor
      \blackrule[\c!color=\s!white,\c!height=\ht#1,\c!depth=\dp#1,\c!width=\wd#1]%
      \hskip-\wd#1%
      \box#1%
      \stopnegative}}

%D There are in principle two ways to handle overprint: bound to colors
%D or independent. For the moment we only support independent overprint
%D handling. Here we deal with a per-document setting.

%D We can move the stack and attribute setting to the \LUA\ end.

\installcorenamespace{colorintent}

\unexpanded\def\registercolorintent#1#2%
  {\setevalue{\??colorintent#1}{\attribute\colorintentattribute\ctxcommand{registercolorintent('#2')} }}

\unexpanded\def\colo_intents_set
  {\ctxcommand{enablecolorintents()}%
   \unexpanded\gdef\colo_intents_set##1{\csname\??colorintent##1\endcsname}%
   \colo_intents_set}

\registercolorintent{knockout} {knockout}
\registercolorintent{overprint}{overprint}

\installattributestack\colorintentattribute

\setevalue{\??colorintent\v!none}{\attribute\colorintentattribute\attributeunsetvalue} % or reset? used at all?

\unexpanded\def\startcolorintent[#1]%
  {\pushattribute\colorintentattribute
   \colo_intents_set{#1}}

\unexpanded\def\stopcolorintent
  {\popattribute\colorintentattribute}

\unexpanded\def\startoverprint{\startcolorintent[\v!overprint]}
\unexpanded\def\startknockout {\startcolorintent[\v!knockout ]}

\let\stopoverprint\stopcolorintent
\let\stopknockout \stopcolorintent

\let\starttextcolorintent\relax
\let\stoptextcolorintent \relax

\appendtoks
    \colo_intents_set_text
\to \everysetupcolors

\let\p_colo_intent\empty

\def\colo_intents_set_text
  {\edef\p_colo_intent{\colorsparameter\c!intent}%
   \ifx\p_colo_intent\v!none \else
     \unexpanded\xdef\starttextcolorintent{\colo_intents_set{\p_colo_intent}}%
     \glet\colo_intents_set_text\relax
     \colo_intents_set\p_colo_intent
   \fi}

\appendtoks \starttextcolorintent \to \everystarttextproperties
\appendtoks \stoptextcolorintent  \to \everystoptextproperties

\setupcolors
  [\c!intent=\v!none]

\protect \endinput