From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265753AbUBPTFr (ORCPT ); Mon, 16 Feb 2004 14:05:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265775AbUBPTFq (ORCPT ); Mon, 16 Feb 2004 14:05:46 -0500 Received: from mail.uni-kl.de ([131.246.137.52]:4041 "EHLO uni-kl.de") by vger.kernel.org with ESMTP id S265753AbUBPTFo (ORCPT ); Mon, 16 Feb 2004 14:05:44 -0500 Date: Mon, 16 Feb 2004 20:05:24 +0100 From: Eduard Bloch To: Pascal Schmidt Cc: linux-kernel@vger.kernel.org Subject: Re: JFS default behavior Message-ID: <20040216190524.GA15087@zombie.inka.de> References: <1pvUz-6j-1@gated-at.bofh.it> <1pRVj-2am-29@gated-at.bofh.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.5.1+cvs20040105i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Moin Pascal! Pascal Schmidt schrieb am Monday, den 16. February 2004: > > When I do this, I still cannot enter unicode chars "as usual". I see > > them, mutt (for example) displays everything correct with a UTF-8 > > locale. However, I cannot insert them correctly. When I use vim, I have > > to press another key (eg. Space) 2..4 times after an umlaut was pressed, > > only then the char appears. > > You're right, inputing UTF-8 (in joe) doesn't work, but that's an > application problem, I think, because it works just fine on a shell > prompt. No, does not work for me either (up-to-date bash). General multibyte support in joe is a different problem. Regards, Eduard. -- Wie man sein Kind nicht nennen sollte: Mario Hanna