(I'm guessing a lot here.) I think that it is down to the way in which PGF inserts colours in to the output file. To see this, it's worth reviewing the levels in the TikZ/PGF system.
- At the top, we have TikZ. This is the frontendlayer and defines the syntax that the user (usually) uses. It's job is to translate user-friendly stuff into a simpler state ready for further processing.
- In the middle, we have PGF. This is the basiclayer. This is where all the detail takes place. Here, things are done in a machine/program-friendly way. The full power of TeX is used to do some heavy machinery. All the path decorations and similar are done here. The goal of this layer is to translate what the user wants in to basic path entities.
- At the bottom, we have the drivers. These form the systemlayer. Here is where the PGF code is interpreted in to specific instructions. These have to be specific to the planned output type.
So the thing to remember in this is that when you say \fill[color=RedSpot] then that is a TikZ command to set the colour to RedSpot which then gets further interpreted by PGF and then the driver. Chasing definitions through, we find that color=RedSpot calls \pgfsetcolor which calls \pgf@setcolor which calls \pgfsys@color@<model>. This is now a driver level command. Its definition, say for CMYK, is
\def\pgfsys@color@cmyk@stroke#1#2#3#4{\pgfsysprotocol@literal{#1 #2 #3 #4 K}}
from which we can see (and tracing back through the definitions, this gets clearer) that even if we've defined a colour name, it is the CMYK values that get put in the file.
The point is that PGF cannot know that it is possible in PDF to alias colours, because it doesn't know that the final output will be PDF. So it translates the colours to their raw values. And 0 1 1 0 setcmykcolor isn't the spot colour.
A lot of the above is speculation, I'll admit. Here's my evidence for this being the case. If you compile the PSTricks file above and look at the PS, you'll find that the drawing code is:
tx@Dict begin STP newpath /ArrowA { moveto } def /ArrowB { } def
0.8 SLW TeXDict begin XC@black end 142.26378 142.26378 113.81102
.5 CLW mul sub 0 360 arc closepath gsave TeXDict begin XC@RedSpot
end 1. .setopacityalpha fill grestore end
But if you compile the TikZ version and look at the PS, you'll find:
0 1 1 0 setcmykcolor
141.73404 141.73404 moveto
255.12128 141.73404 moveto
255.12128 204.35689 204.35689 255.12128 141.73404 255.12128 curveto
79.11119 255.12128 28.3468 204.35689 28.3468 141.73404 curveto
28.3468 79.11119 79.11119 28.3468 141.73404 28.3468 curveto
204.35689 28.3468 255.12128 79.11119 255.12128 141.73404 curveto
closepath
So the RedSpot gets put literally in to the PS from PSTricks but is translated back to 0 1 1 0 internally by PGF first.
The clincher is to do the following. Edit the PS file and replace the 0 1 1 0 setcmykcolor by XC@RedSpot. Then do the gs and montage stuff, and you get:
which is what you wanted.
However, editing the postscript isn't a great way to do this! Here's what I think you'd have to do to use spot colours in TikZ. I think you'd have to define a new colour model, say spot. You'd then tell PGF that the spot colour model is to be treated specially in that the name of the colour is to be used (or at least XC@<name>). To define a spot colour, you could (I think) use xcolor to define it using one model and then convert it to another. That would ensure that the definition got in to the PS file (which it does already). I don't know how to do all those steps, because it relies on knowing how xcolor works and I don't know much about that. But that's what I would do.
I suppose the lower cell is filled with colour after the multirow is created, hence covering up its contents. If you instead move the multirow to the lowest row, and use -2 instead of 2, it works better.
To define colours using RGB values, use either
\definecolor{<name of colour>}{rgb}{<red>, <green>, <blue>}
where <color> is in the interval [0,1], or
\definecolor{<name of colour>}{RGB}{<red>, <green>, <blue>}
where <color> is integers in the interval [0,255].
\documentclass[a4paper]{report}
\usepackage{multirow}
\usepackage[table]{xcolor}
\definecolor{MyColor}{rgb}{0.8, 0.8, 0.8}
\begin{document}
\begin{table}
\rowcolors{1}{gray!15}{gray!15}
\centering
\begin{tabular}{rrrrr}
\rowcolor{MyColor}
Header & 1 & 2 & 3 & 4 \\
Row1 & a & b & c & d \\
\multicolumn{1}{c}{} & a1 & b1 & c1 & d1 \\
\multicolumn{1}{c}{\multirow{-2}[0]{*}{Multirow1}} & a2 & b2 & c2 & d2 \\
Row2 & aa & ab & ac & ad \\
\end{tabular}
\end{table}
\end{document}
Best Answer
All features of
colorare available by loading thexcolorpackage as well. I would say that you can always load the latter one since:You don't have to care which features are in which one.
You surely satisfy all other packages relying on
color/xcolor.Many package load it anyways (
tikzto name the most important one), so you even don't have to load it yourself.Notice that there are other pairs of packages where one extends the other:
color<xcolorgraphics<graphicxamsmath<mathtools(in the sense you don't have to loadamsmath)