Re: [kbd] unicode option for not working correctly since commit: bad17ea03
Michal Soltys <[email protected]> Mon, 19 Sep 2016 22:10:58 +0200
| Newsgroups | dev.linux.lists.kbd |
|---|---|
| Message-ID | <[email protected]> |
On 2016-09-06 21:26, Alexey Gladkov wrote: > On Thu, Jun 16, 2016 at 03:06:43AM +0200, Michal Soltys wrote: >> Hi, >> >> So for example (assuming LANG is set correctly as well to utf8 locale): >> >> unicode_start LatArCyrHeb-16 >> loadkeys -u pl > > Can you show me your keymap ? > It's standard kbd keymap (pl.map.gz). >> still behaved fine. >> >> loadkeys -u no longer works and despite the console operating in utf-8 >> mode requires console map (in this case -m 8859-2). > > You mean `setfont -m 8859-2 ...` ? > Yea, it still seems to handle input with 8th bit set providing workaround for the issue. Simple test: 1) log on console, assure proper LANG (e.g. pl_PL.utf8 or en_US.utf8) 2) unicode_start LatArCyrHeb-16 3) loadkeys -u pl This basically should work just fine. Polish glyphs are under alt-a,c,e,l,n,o,s,x,z On pre-2.0 versions all will be working fine (or to be precise, pre-commit I bisected). After that commit some will be failing. If you do setfont -m 8859-2 - this will provide the workaround.