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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
|
<?xml version="1.0" encoding="utf-8"?>
<!--
This file is part of groff, the GNU roff type-setting system.
Copyright (C) 2004, 2005, 2006, 2009, 2010 Free Software Foundation, Inc.
Written by Peter Schaffter.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with the
Invariant Sections being this comment section, with no Front-Cover
Texts, and with no Back-Cover Texts.
A copy of the Free Documentation License is included as a file called
FDL in the main directory of the groff source package.
-->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html;charset=utf-8"/>
<title>Mom -- Colour</title>
<link rel="stylesheet" type="text/css" href="stylesheet.css" />
</head>
<body style="background-color: #f5faff;">
<!-- ==================================================================== -->
<div id="top" class="page">
<!-- Navigation links -->
<table style="width: 100%;">
<tr>
<td><a href="toc.html">Back to Table of Contents</a></td>
<td style="text-align: right;"><a href="graphical.html#top">Next: Graphical objects</a></td>
</tr>
</table>
<h1 class="docs">Coloured text</h1>
<div style="text-align: center;">
<a href="#index-color">List of color macros</a>
</div>
<div class="rule-medium"><hr/></div>
<h2 class="docs">Introduction</h2>
<p>
Mom’s support for coloured text is straightforward. You begin
by telling mom about the colours you want with
<kbd><a href="#newcolor">NEWCOLOR</a></kbd>
or
<kbd><a href="#xcolor">XCOLOR</a></kbd>.
Afterward, any time you want text to be coloured, you either colour
it with an
<a href="definitions.html#inlines">inline escape</a>
that contains the colour name (e.g. <kbd>\*[red]</kbd>
or <kbd>\*[blue]</kbd>) or invoke the macro,
<kbd><a href="#color">COLOR</a></kbd>,
with the name of the colour you want.
</p>
<p id="color-example">
For example, say you want to have the name “Jack” in the
sentence “All work and no play makes Jack a dull boy”
appear in yellow. You'd begin by telling mom about the colour,
yellow. There are two ways of doing this; see
<kbd><a href="#newcolor">NEWCOLOR</a></kbd>
and
<kbd><a href="#xcolor">XCOLOR</a></kbd>
for a full explanation of the difference between the two.
</p>
<p>
If you use XCOLOR, you'd enter this:
<br/>
<span class="pre-in-pp">
.XCOLOR yellow
</span>
If you use NEWCOLOR, you might enter:
<br/>
<span class="pre-in-pp">
.NEWCOLOR yellow RGB #FFFF00
</span>
</p>
<p id="color-example2" style="margin-top: -1em;">
After “defining” (or “initializing”) the
colour “yellow”, you'd colourize the name, Jack, either
with an inline escape
<br/>
<span class="pre-in-pp">
All work and no play makes \*[yellow]Jack\*[black] a dull boy.
</span>
or with the
<kbd><a href="#color">COLOR</a></kbd>
macro
<br/>
<span class="pre-in-pp">
All work and no play makes
.COLOR yellow
Jack
.COLOR black
a dull boy.
</span>
Notice, in both examples, that a) you have to set the colour back
to black after “Jack”, and b) you don’t have to
define or intialize the colour, black. Mom predefines it for you.
</p>
<p>
For information on using colour during
<a href="docprocessing.html#intro-macros-docprocessing">document processing</a>,
see
<a href="docprocessing.html#color">Colour support in document processing</a>.
</p>
<div class="box-tip">
<p class="tip">
<span class="note">Note:</span>
Mom’s colour support is for text only. She doesn’t
support “fill” (or “background”) colour for
solid, enclosed graphical objects (polygons, ellipses) drawn with
groff’s <kbd>\D</kbd>
<a href="definitions.html#inlines">inline escapes</a>,
although you may give a colour as one of the arguments to
mom’s “box” and “circle” macros,
<a href="graphical.html#dbx">DBX</a>
and
<a href="graphical.html#dcl">DCL</a>
when the first argument to these macros is <kbd>SOLID</kbd>.
</p>
</div>
<div class="box-tip">
<p class="tip">
<span class="experts">Experts:</span>
If you’re accustomed to using groff’s
<kbd>.defcolor</kbd> to define colours, and groff’s inline
<kbd>\m[<colorname>]</kbd> to call them, you may continue to
do so without confusing mom.
</p>
</div>
<div class="macro-list-container">
<h3 id="index-color" class="macro-list">Coloured text macros</h3>
<ul class="macro-list">
<li><a href="#newcolor">NEWCOLOR</a></li>
<li><a href="#xcolor">XCOLOR</a></li>
<li><a href="#color">COLOR</a></li>
<li><a href="#color-inline">\*[<colorname>]</a> (inline escape)</li>
</ul>
</div>
<div class="rule-medium" style="margin-bottom: 1.5em;"><hr/></div>
<!-- -NEWCOLOR- -->
<div class="macro-id-overline">
<h3 id="newcolor" class="macro-id">Creating (initializing) a colour with NEWCOLOR</h3>
</div>
<div class="box-macro-args">
Macro: <b>NEWCOLOR</b> <kbd class="macro-args"><colour name> [<colour scheme>] <colour components></kbd>
</div>
<p>
NEWCOLOR lets you create a colour, rather like an artist mixing
paint on a palette. The colour isn’t used immediately;
NEWCOLOR merely tells mom how to mix the colour when you need it.
If you haven’t invoked <kbd>.NEWCOLOR</kbd> (or
<kbd><a href="#xcolor">.XCOLOR</a></kbd>),
mom doesn’t have a clue what you mean when you reference a
colour (with
<a href="#color">COLOR</a>
or
<a href="#color-inline"><kbd>\*[<color name>]</kbd></a>).
</p>
<p>
The first argument to NEWCOLOR is a name for your colour. It
can be anything you like—provided it’s just one word
long—and can be caps, lower case, or any combination of the
two.
</p>
<p>
The second argument, which is entirely optional, is the
“colour scheme” you want mom to use when mixing the
colour. Valid arguments are
<br/>
<span class="pre-in-pp">
RBG (3 components: red green blue)
CYM (3 components: cyan yellow magenta)
CMYK (4 components: cyan magenta yellow black)
GRAY (1 component)
</span>
If you omit the second argument, mom assumes you
want RGB.
</p>
<p>
The final argument is the components of your colour. This can be
hexadecimal string starting with a pound sign (<kbd>#</kbd>) (for
colour values in the 0-255 range) or two pound signs (<kbd>##</kbd>)
(for colour values in the 0-65535 range), or it can be a series of
decimal digits, separated by spaces, one digit per component, with
the argument enclosed in double quotes. (If this is all gibberish
to you, see
<a href="#color-tip">Tips for newbies</a>.)
</p>
<p>
Thus, to tell mom about a colour named “YELLOW”, you
could enter one of the following:
<br/>
<span class="pre-in-pp">
.NEWCOLOR YELLOW #FFFF00 \"or ##FFFFFFFF0000 or "1 1 0"
.NEWCOLOR YELLOW RGB #FFFF00 \"or ##FFFFFFFF0000 or "1 1 0"
.NEWCOLOR YELLOW CYM #00FF00 \"or ##0000FFFF0000 or "0 1 0"
.NEWCOLOR YELLOW CYMK #00FF0000 \"or ##0000FFFF00000000 or "1 1 0"
</span>
After you've told mom about a colour, you can then get her to set
text in that colour either with the
<a href="definitions.html#inlines">inline escape</a>,
<a href="#color-inline"><kbd>\*[<colorname>]</kbd></a>,
or the macro,
<a href="#color">COLOR</a>.
(See the
<a href="#color-example">example</a>,
above.)
</p>
<div class="box-tip">
<p class="tip-top">
<span class="note">Note:</span>
The colorname you give to NEWCOLOR may be used with groff’s
<kbd>\m[<colorname>]</kbd> inline escape (the <kbd>\m</kbd>
escape is used to set text and rule colours). Thus, assuming
a colorname “blueblack” set with NEWCOLOR,
<kbd>\*[blueblack]</kbd> and <kbd>\m[blueblack]</kbd> are
equivalent. Furthermore, the colorname can be given as an argument
to <b>groff</b>’s
<a href="definitions.html#primitives">primitive</a>
request, <kbd>.gcolor</kbd> (which does the same thing as
<kbd>\m[<colorname>]</kbd>).
</p>
<p class="tip-bottom">
Equally, the colorname may be used with
<kbd>\M[<colorname>]</kbd> and <kbd>.fcolor</kbd>, which set
the “fill” colour for solid graphical objects.
</p>
</div>
<div class="box-tip">
<p id="color-tip" class="tip-top">
<span class="tip">Tips for newbies:</span>
Colour manipulation can be tremendously confusing if you don’t
have a background in graphic arts or computing. My advice, if color
intimidates you, is to stick to using mom’s default RGB colour
scheme, and to fire up a color chooser that gives you the RGB values
you want for the colour you select. Plug those values into the
components argument to NEWCOLOR, and you’ll get the colour
you want. Both the KDE and gnome desktops have colour selectors
that provide you with the shorter RGB hexadecimal string. If
you’re not running KDE or gnome, the X utility, xcolorsel,
provides you with a similar functionality, although it only provides
RGB values for 256 pre-defined colours. If you use xcolorsel, be
sure to click the button “Display format” and select
“8 bit truncated rgb”.
</p>
<p class="tip-bottom">
Alternatively, you can use mom’s simpler
<kbd><a href="#xcolor">XCOLOR</a></kbd>
macro to initialize one of the 256 pre-defined X colours by
supplying the name of the color as an argument.
</p>
</div>
<!-- -XCOLOR- -->
<div class="macro-id-overline">
<h3 id="xcolor" class="macro-id">Initializing a colour with XCOLOR</h3>
</div>
<div class="box-macro-args">
Macro: <b>XCOLOR</b> <kbd class="macro-args"><X colorname> [<alias>]</kbd>
</div>
<p class="requires">
<kbd style="font-style: normal"><X colorname></kbd> <i>must be all one word, all lower case.</i>
<br/>
(See
<a href="#xcolor-names" style="font-style: normal;">Finding X color names</a>
for how to get a list of valid colour names.)
</p>
<p>
XCOLOR is similar to NEWCOLOR in that it tells mom to initialize a
colour, but it’s easier to use. All you have to do is pass
it, as an argument, the valid name of one of the 256 pre-defined
X colours. The name must be all one word, and, breaking with mom
policy, it must be entered in lower case.
</p>
<p>
For example, if you want to intialize the X colour, coral, all you
have to do is enter
<br/>
<span class="pre-in-pp">
.XCOLOR coral
</span>
Afterwards
<br/>
<span class="pre-in-pp">
.COLOR coral
</span>
will colourize subsequent text coral until you instruct mom to
return to black, or some other pre-defined, initialized colour.
(The
<a href="definitions.html#inlines">inline escape</a>
<kbd>\*[coral]</kbd> will equally colourize text coral after you've
initialized the colour with XCOLOR.)
</p>
<p>
The downside of XCOLOR is that you can’t create custom
colours. This restriction, however, is mitigated by the fact that
for many users, 256 colours is more than enough to play around with.
</p>
<p>
While some X colours have fanciful names (peachpuff, papayawhip,
thistle, snow), many are self-explanatory and self-descriptive
in ordinary colour terms. “blue” is pure (rgb)
blue, “green” is pure (rgb) green, and so on.
Furthermore, for many X colors, there exist four variants, each
representing increasingly darker shades of the same colour.
For example, “blue1” is a relatively bright blue;
“blue2”, “blue3” and “blue4” are
increasingly darker shades. For that reason, you may find XCOLOR is
a better choice than NEWCOLOR when it comes to initializing common
colors.
</p>
<p>
The whimsical nature of X colour names sometimes makes for names
that are long to type in, e.g. “mediumspringgreen”. The
optional second argument to XCOLOR allows you to come up with more
convenient name by which to reference the colour. For example, you
could enter
<br/>
<span class="pre-in-pp">
.XCOLOR mediumspringgreen mygreen
</span>
or
<span class="pre-in-pp">
.XCOLOR mediumspringgreen MYGREEN
</span>
so that whenever you want text mediumspringgreen-ed, you
can use either <kbd>.COLOR mygreen</kbd> (or
<kbd>.COLOR MYGREEN</kbd>) or the inline escape
<kbd>\*[mygreen]</kbd> (or <kbd>\*[MYGREEN]</kbd>.)
</p>
<h3 id="xcolor-names" class="docs">Finding X color names</h3>
<p>
There are two ways of finding the names of the pre-defined X
colours. One is to consult the file, rgb.txt, included with all
X11 installations. The location of the file on a Debian GNU/Linux
distribution is typically /etc/X11/rgb.txt. Other distributions and
other X installations may have the file in another location. The
file lists the colour names, but doesn’t show you what the
colours actually look like.
</p>
<p>
A better way to get the colour names, as well as to see what the
colours look like, is to fire up a colour chooser (like xcolorsel)
that both lists the colour names and shows a swatch of the colour
as well.
</p>
<p>
Whichever method you use to find X color names, remember that the
names, passed as arguments to XCOLOR, must be all one word, all in
lower case.
</p>
<div class="box-tip">
<p class="tip-top">
<span class="note">Note:</span>
Both the colorname and the alias you give to XCOLOR may be
used with groff’s <kbd>\m[<colorname>]</kbd>
inline escape (the <kbd>\m</kbd> escape is used to set
text and rule colours). Thus, assuming an X-colorname
“mediumspringgreen” set with XCOLOR, and an alias,
“mygreen”, <kbd>\*[mediumspringgreen]</kbd>,
<kbd>\m[mediumspringgreen]</kbd>, <kbd>\*[mygreen]</kbd> and
<kbd>\m[mygreen]</kbd> are all equivalent. Furthermore, both the
colorname and the alias can be given as an argument to groff’s
<a href="definitions.html#primitives">primitive</a>
request, <kbd>.gcolor</kbd> (which does the same thing as
<kbd>\m[<colorname>]</kbd>).
</p>
<p class="tip-bottom">
The colorname initialized with XCOLOR <i>but not the
alias</i> may also be used with groff’s inline escape,
<kbd>\M[<colorname>]</kbd>, and the corresponding primitive,
<kbd>.fcolor</kbd>, both of which set the “fill” colour
for solid graphical objects. If you need a colour initialized with
XCOLOR for <kbd>\M</kbd> or <kbd>.fcolor</kbd>, you MUST give the
full colorname; the alias won’t work.
</p>
</div>
<!-- -COLOR- -->
<div class="macro-id-overline">
<h3 id="color" class="macro-id">Invoking a color</h3>
</div>
<div class="box-macro-args">
Macro: <b>COLOR</b> <kbd class="macro-args"><colorname></kbd>
</div>
<p id="color-inline" class="requires" style="font-style: normal;">
Inline: <kbd>\*[<colorname>]</kbd>
</p>
<p>
Once you've told mom about a colour (via
<a href="#newcolor">NEWCOLOR</a>
or
<a href="#xcolor">XCOLOR</a>,
you use either the macro, COLOR, or the
<a href="definitions.html#inlines">inline escape</a>,
<kbd>\*[<colorname>]</kbd>, to cause mom to
set subsequent text in that colour. See the
<a href="#color-example2">example</a>,
above, which shows both in action.
</p>
<div class="box-tip">
<p class="tip-top">
<span class="note">Note:</span>
You can use the <kbd>\*[<colorname>]</kbd> inline escape in
any
<a href="docprocessing.html#top">document processing</a>
macro that takes a
<a href="definitions.html#stringargument">string argument</a>.
However, you must remember to reset the colour at the end of the
argument (typically with <kbd>\*[black]</kbd>) unless you want all
subsequent invocations of that particular macro to be colourized.
</p>
<p>
Furthermore, if you use <kbd>\*[<colorname>]</kbd> in the
string argument passed to
<a href="docelement.html#head">HEAD</a>,
<a href="docelement.html#subhead">SUBHEAD</a>
or
<a href="docelement.html#parahead">PARAHEAD</a>,
and you've requested that any of these types of heads be numbered,
the numbers themselves will not be coloured, only the text you
passed the macro. If you wish the numbers to be colourized as well,
you must explicitly tell mom that you wish all of the head(s),
subhead(s) or parahead(s), including the numbers, colourized by
invoking the appropriate
<a href="docelement.html#docelement-control">control macro</a>.
</p>
<p class="tip-bottom">
For colorizing underscored text, see
<a href="goodies.html#underscore-color">Colorizing underscored text</a>
in the notes at the end of
<a href="goodies.html#underscore">UNDERSCORE</a>.
</p>
</div>
<div class="rule-long"><hr/></div>
<!-- Navigation links -->
<table style="width: 100%; margin-top: 12px;">
<tr>
<td style="width: 33%;"><a href="toc.html">Back to Table of Contents</a></td>
<td style="width: 33%; text-align: center;"><a href="#top">Top</a></td>
<td style="width: 33%; text-align: right;"><a href="graphical.html#top">Next: Graphical objects</a></td>
</tr>
</table>
</div>
<div class="bottom-spacer"><br/></div>
</body>
</html>
<!-- vim: fileencoding=utf-8: nomodified: -->
|
