On Thu, Aug 07, 2014 at 06:57:49PM +0000, Ivan Shmakov wrote: > > > This doesn't happen when framebuffer is used. > > Does that mean /dev/fb*, or rather the “kernel mode setting” > (KMS) facility? > > The last time I’ve checked, – it wasn’t the case for KMS-enabled > text VTs. I wasn’t following this closely, though.
All depends on the hardware mode of the videocard. If the videocard is in graphic mode (i.e. the text mode is emulated by the kernel), then there is no color limitation. On the other hand, if the videocard is in real text mode and the font is loaded in the videocard itself, then inevitably there is a color limitation. > > With modern kernels framebuffer is more or less a requirement. > > With xserver-xorg-video-vesa, – it surely isn’t. > > Unfortunately, “native” X video drivers are simply not supported > for my hardware on Debian. (Unless, of course, one considers > firmware-linux-nonfree to be part of Debian, which it’s /not./) OK. > That doesn’t seem like “supported” to me, as: > > • /usr is generally reserved for dpkg-maintained files; the > “custom” ones belong to /usr/local instead; It is not difficult to add a support for /usr/local. But since console-setup already searches for files in /etc/console-setup/ and supports absolute file names, I suppose this isn't really necessary. > • by “custom fontsets support” I mean, specifically, that the > user is provided a tool which locates user’s own fontsets > (either in /etc/console-setup or somewhere under /usr/local, > or perhaps passed via the command line) and generates the > respective font files; alas, I don’t seem to see any such tool > provided by either console-setup, console-setup-linux, or kbd > packages. We shouldn't expect from the users to generate fonts. This is an experienced task that should be done developers. It will be much more convenient if the users use fonts prepared by more experienced people. Now, let as think from the position of the font developer. Do we require from him to prepare the fonts exactly according to the requirements of console-setup (codeset, fontface, fontsize)? Well, I think this is too much work and the benefits -- only moderate considering that console-setup is able to use any non-standard console fonts. In fact, Debian already includes a few packages with non-standard console fonts (console-braille, psf-unifont, fonty-rg). None of these packages follows the standards of console-setup and there is no need for this -- it is much more convenient to use a simple instruction FONT=... than to think in terms of codeset, fontface and fontsize. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140808110020.ga6...@debian.lan
