From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on sa.local.altlinux.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 To: kbd@lists.altlinux.org From: Michal Soltys Message-ID: Date: Thu, 16 Jun 2016 20:35:51 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-ID: A798157CA5.A335A X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details X-MailScanner-From: soltys@ziu.info Cc: gladkov.alexey@gmail.com Subject: [kbd] loadkey's unicode option (-u) not working correctly since commit bad17ea03 X-BeenThere: kbd@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Linux console tools development discussion List-Id: Linux console tools development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2016 18:35:58 -0000 Archived-At: List-Archive: Hi, There seems to be an issue since the following commit: 2) http://git.kernel.org/cgit/linux/kernel/git/legion/kbd.git/commit/?id=bad17ea033bf571e03b05e1330e81e6238fd61f0 (the commit directly preceeding this one doesn't compile) which causes invocations such as 'loadkeys -u' or 'dumpkeys | loadkeys -u' to not work correctly in utf8 mode (after for example unicode_start). The last working (and able to compile easily) commit where loadkeys works fine is http://git.kernel.org/cgit/linux/kernel/git/legion/kbd.git/commit/?id=8d37c0e76fdb487845da74bdf0bbce13eebf7596 For example consider: export LANG=en_US.utf8 unicode_start LatArCyrHeb-16 loadkeys -u pl This will produce correct output (e.g. alt+l) on builds up to commit bad17ea03. Afterwards it will behave as if the keymap wasn't translated to unicode and followed charset specification from the keymap file itself. This (in this particular case) requries - to behave correctly: setfont -m 8859-2 LatArCyrHeb-16 Despite full utf8/unicode mode. PS. I earlier sent similar message w/o subscribing to the mailing list, so just disregard it.