You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you inside a calstable cell (\cell{}) issue a colour-command for foreground colour (\cell{\color{green}Testing} the colour will leak outside the cell, colourising not only the rest of the tabular and its rules (borders), but also the rest of the document. According to Stackexchange user, Ulrike Fischer, (see her comments to this answer at Stackexchange) the reason is that cals does not use "colour-safe" boxing commands.
I believe this may be a similar issue as described in David Carlisle's answers in these two answers:
Thanks, I'll re-check the issue. I expected that colour-safe boxes add whatis-boxes, and it is fatal for cals, which re-builds the internal structure of boxes. I hope I'm wrong.
Work-arounds are using \cell{\textcolor{<colour>}{Cell text}} or extra grouping inside the cell, \cell{{\color{<colour>}Cell text}}.
However, fiddling around with color{<colour>} different places inside, discloses some surprising effect on foreground text and rules.
Maybe a solution is to implement a cals@fgcolor{}-command, similar to the cals@bgcolor{}-command.
"Poor mans" arraycolor for cals is issuing a color{<colour>} outside the calstable, and use a textcolor{<textcolour>}{Cell text} in each cell. Using \cals@AtBeginCell colourise the inside table rules in addition to the text.
If you inside a calstable cell (\cell{}) issue a colour-command for foreground colour
(\cell{\color{green}Testing}
the colour will leak outside the cell, colourising not only the rest of the tabular and its rules (borders), but also the rest of the document. According to Stackexchange user, Ulrike Fischer, (see her comments to this answer at Stackexchange) the reason is that cals does not use "colour-safe" boxing commands.I believe this may be a similar issue as described in David Carlisle's answers in these two answers:
The text was updated successfully, but these errors were encountered: