Am 09.01.2012 um 00:36 schrieb Hans Hagen: > a side effect of mp's color models not being to clever .. why exactly do you > need the never
For setting colors to black (better explained here): Anfang der weitergeleiteten E-Mail: > Von: Hans Hagen <pra...@wxs.nl> > Datum: 1. März 2010 16:56:09 MEZ > An: mailing list for ConTeXt users <ntg-context@ntg.nl> > Betreff: Re: [NTG-context] MkIV gray, no MkII black ? > Antwort an: mailing list for ConTeXt users <ntg-context@ntg.nl> > > On 1-3-2010 15:02, Peter Rolf wrote: >> Hi Steffen, >> >> Am 01.03.2010 13:41, schrieb Steffen Wolfrum: >>> Hi, >>> >>> in MkII I set \setupcolors[state=start] to activate defined colors (for >>> text, numbers etc.), >>> and \setupcolors[state=stop] to set these colors to black. >>> >>> Now, in MkIV \setupcolors[state=stop] does set these colors to gray. Not to >>> black. >>> [Log: "color : system gray is global activated"] >>> >>> >>> What is the key to set either "color is color" or "color is black" again? >>> >> i don't think mkiv has such an option (but maybe i'm wrong). >> how about defining some color palettes then? this should work with both >> marks. >> >> \definepalet[coloredtext][...] >> \setuppalet[coloredtext] >> >> \startmode[black] >> \definepalet[blacktext] [red=black, blue=black,...] >> \setuppalet[blacktext] >> \stopmode > > as colorspace info travels indepently you can say > > \attribute\colormodelattribute\attributeunsetvalue > > > i'll add > > \setupcolors[state=stop,conversion=never] Steffen ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________
