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

Re: Bug#666542: incorrect rendering of lat15 characters

Hi Anton,

Thank you for looking into this...

El 15 d’abril de 2012 9:40, Anton Zinoviev <anton@lml.bas.bg> ha escrit:
> Unfortunately kFreeBSD kernels seem to be unfriendly to localizations.
> I suppose this is due to the UTF-8 patch.  I suppose it is possible to
> fix this without changes in the kernel with some undocumented command,
> but unfortunately last time I checked I was unable to find any useful
> documentation.
> So in order to fix this important bug I need help.  I don't know how one
> can use on kFreeBSD fonts that are not encoded in CP437.  On normal
> FreeBSD one can use the following commands:
> vidcontrol -f FONT_FILE
> vidcontrol -l FONT_ENCODING_FILE
> I am almost certain that in order to do this with current kernels one
> has to disable somehow the UTF mode on the console and work in 8-bit
> encoding.

I tried with kfreebsd-downloader on an up-to-date Debian GNU/kFreeBSD
system.  kfreebsd-downloader downloads binaries for kFreeBSD 9.0 from
upstream.  So as far as the kernel it's concerned, we get the same

I didn't notice any difference when booting with upstream kernel.

> I think on normal FreeBSD console-setup works "out of the box".  So if
> some developer has FreeBSD (not Debian) and wants to see how
> console-setup works there (s)he can test console-setup using its source
> package:
> http://ftp.de.debian.org/debian/pool/main/c/console-setup/console-setup_1.75.tar.gz

Tried that on FreeBSD 10-CURRENT, but I notice setup instructions have
many references to a terminal type that is no longer in use (cons25).
Since FreeBSD 9.0 the default is xterm.  Have you tested with recent
versions of FreeBSD?

Robert Millan

Reply to: