The problem is caused by Unicode code points in keymap files, which were
made possible (and have to be used) for many locales after the
introduction of Unicode support with vt(4).
Am 28.08.2014 um 19:43 schrieb Stefan Esser:
Am 28.08.2014 um 17:03 schrieb Filippo Moretti via freebsd-stable:
I
Ok, so what can we do right now to not have unicode characters in say,
the US keymap file?
(Just a local change, not committed anywhere - I agree it needs to be
fixed in the xorg code.)
-a
___
freebsd-ports@freebsd.org mailing list
Am 31.08.2014 um 09:45 schrieb Adrian Chadd:
Ok, so what can we do right now to not have unicode characters in say,
the US keymap file?
The normal US keyboard (/usr/share/vt/keymaps/us.kbd) does not
contain characters = 0x100.
There is no problem even with ISO8859-1 characters used in many
On 08/31/2014 08:53, Stefan Esser wrote:
The problem is caused by Unicode code points in keymap files, which were
made possible (and have to be used) for many locales after the
introduction of Unicode support with vt(4).
Am 28.08.2014 um 19:43 schrieb Stefan Esser:
Am 28.08.2014 um 17:03
I discovered that:
* if I don't load kbdmap at boot-time as a module, the probe order
works in a way that xorg works;
* if I load kbdmap by hand after boot, or I don't load it at all, then
even the US keyboard map causes xorg to choke.
If I load kbdmap at boot-time then kbdcontrol reports
