[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#561008: console-setup: approximations for 'toilet -f future' symbols look different before and after X



On Mon, 14 Dec 2009 23:02:53 +0200 Anton Zinoviev wrote:

> On Mon, Dec 14, 2009 at 08:08:12PM +0100, Francesco Poli wrote:
> > 
> > No, I cannot: this command belongs to the kbd package, but I do not
> > have this package installed on any of the Debian boxes I use.
> > 
> > Should I switch from console-tools to kbd, in your opinion?
> 
> Console-tools has several bugs that are not going to be fixed, it 
> doesn't have upstream maintainer.  On the other hand Kbd is actively 
> maintained (both in Debian and by the upstream).  Thats why the future 
> versions of Debian are going to use Kbd instead of console-tools.

That's useful news, thanks: I now begin to remember reading some similar
considerations, but it was long ago and I had forgotten...   :-(

I'll probably try and switch to kbd, as soon as I find some time to do
so.

[...]
> > Or is there an equivalent command in console-tools?
> 
> The equivalent command is 'showcfont' but it doesn't work on my machine 
> (outdated version of Debian unstable).

I had tried with 'showcfont', but I thought it didn't do what you
wanted.  Instead of telling me the name of the used font (as I
expected), it wrote a complete table with all the gliphs and codes.

Well, I am not able to be sure the font has not changed, just by
looking at this table!

> 
> > > Does the look of 'toilet -f future hello' restore if you use the command 
> > > 'setupcon'?
> > 
> > No, it doesn't.
> > After issuing the 'setupcon' command (as root), the look stays the same
> > (broken lines).
> 
> I suppose that only the horizontal lines are broken (the vertical are 
> OK)?

Bingo!
You guessed!

Does this help?
Sorry for not saying it explicitly before...

> Can you use the command 'consolechars -f FONTNAME' in order to 
> make sure that the other fonts (both in console-setup and console-data) 
> have the same problem.  In particular can you see whether the fonts that 
> you used before console-setup are also with broken lines?

I've just tested the following commands:

  $ consolechars -f Lat15-Fixed16
  $ consolechars -f Lat15-Terminus16
  $ consolechars -f Lat15-TerminusBold16
  $ consolechars -f Lat15-TerminusBoldVGA16
  $ consolechars -f Lat15-VGA16
  $ consolechars -f lat1u-16

All these fonts share the problem.

As far as lat1u-16 is concerned, please note that it has always had
this problem (broken horizontal lines): that's why I labeled it as a
"compromise solution".

With TerminusBoldVGA the problem doesn't show up before starting X,
hence I was astonished to see it come back, as soon as I started X and
switched back to the console!



P.S.: Anton, I cannot stress enough how I appreciate your quick and
helpful replies; your dedication to the improvement of console-setup
and your assistance for users are really great!   :-)


-- 
 New location for my website! Update your bookmarks!
 http://www.inventati.org/frx
..................................................... Francesco Poli .
 GnuPG key fpr == C979 F34B 27CE 5CD8 DC12  31B5 78F4 279B DD6D FCF4

Attachment: pgpAVAHc9N8Do.pgp
Description: PGP signature


Reply to: