Joseph Wright
Joseph Wright
Honestly I think this is one for you @car222222: I am not really sure what is needed.
This is independent of the backend: it will work as long as `l3color` is loaded. (Longer-term I'd like to merge that to `expl3` core, but that's also independent.) Assuming it...
Ah, right, that would be tricky: do you want us to even try to set up named colors? Either way, we'll need some dedicated function that allows for 'unknown model'...
@car222222 Separations are each models in their own right, so `l3color` is moving to having them not as a single `spot` model but rather creating a model for each one....
@u-fischer Something like ```latex \protected\def\DefineNamedColor#1#2#3#4{% \@ifundefined{define@color@#1}% {\c@lor@error{model `#1'}}% {\@ifundefined{color@#3}% {\c@lor@error{model `#3'}}% {\@ifundefined{col@#2}{}% {\PackageInfo{color}{Redefining color #2 in named color model}}% \csname color@#3\endcsname\@tempa{#4}% % New: support "usenames" \ifx\c@lor@usename\@gobble\else \@expl@color@set@@nnn{#2}{#3}{#4}% \fi \csname define@color@#1\endcsname{#2}\@tempa...
> > > @josephwright wrote: > they are just colors in their fallback model for l3color. > > Not quite, rather: > 1 They are just colors with a LaTeX...
Are we good to go here? This would be nice to have in 2021-05-01.
Perhaps go for something similar to the `silence` package: just provide an 'on-off' switch for the moment, and see if anything else is needed?
Looking back, this likely wants a higher-level package, but would first need a documented list of message identifiers.