Giacomo Boffi writes:
> Brice Goglin writes:
> > Hi Giacomo,
> >
> > I guess this problem with the RGB database being replaced by a
> > static table still occurs wth latest xserver-xorg-core 1.3, right?
> > For the record, it looks like we could revert to the old behavior
> > by defining USE_RGB_BUILTIN to 0 during the build (see
> > os/oscolor.c). However, I am not sure it is worth doing it.
>
> imho, it's worth doing because the X rgb database has been severely
> criticized for its unfair distribution of colors [1], in particular
> darkest one, and a user/sysadm that want to define (add) new symbolic
> color names to X can *only* resort to editing rgb.txt
>
> otoh, kpackard himself changed the default behaviour...
i can add another reason to define USE_RGB_BUILTIN to 0 during the
build: some debian chap added the color "RedDebian" to
/etc/X11/rgb.txt in a recent release of the x11-common package
please imagine the deluded face he'd sport when xsetroot -solid
DebianRed reply will be `unknown color "DebianRed"'...
ciao
gb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
