Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932419AbXBSRDD (ORCPT ); Mon, 19 Feb 2007 12:03:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932429AbXBSRDD (ORCPT ); Mon, 19 Feb 2007 12:03:03 -0500 Received: from 85.8.24.16.se.wasadata.net ([85.8.24.16]:38471 "EHLO smtp.drzeus.cx" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932419AbXBSRDA (ORCPT ); Mon, 19 Feb 2007 12:03:00 -0500 Message-ID: <45D9D848.4010608@drzeus.cx> Date: Mon, 19 Feb 2007 18:03:04 +0100 From: Pierre Ossman User-Agent: Thunderbird 1.5.0.9 (X11/20070131) MIME-Version: 1.0 To: OGAWA Hirofumi CC: LKML Subject: Re: Racy NLS behaviour in FAT (and possible other fs) References: <45D9C80A.2030905@drzeus.cx> <87tzxim6ic.fsf@duaron.myhome.or.jp> In-Reply-To: <87tzxim6ic.fsf@duaron.myhome.or.jp> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1001 Lines: 29 OGAWA Hirofumi wrote: >> I'm experiencing a rather odd behaviour with the character set >> conversion. If I mount a vfat fs with utf8 and then create a file >> with invalid utf-8 sequences, the file will briefly exist with these >> invalid sequences, then quickly convert to a stripped version. >> > > Yes. utf8 support is broken, and it will fail to convert letter case > on many case. And it's why that is not recommended. > > Is there any ongoing work to fix this? UTF-8 is standard on more or less every distribution these days. Rgds -- -- Pierre Ossman Linux kernel, MMC maintainer http://www.kernel.org PulseAudio, core developer http://pulseaudio.org rdesktop, core developer http://www.rdesktop.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/