From: "Petr Vandrovec" Subject: NLS mappings for iso-8859-* encodings Date: Mon, 6 May 2002 23:09:43 +0200 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <47025960266@vcnet.vc.cvut.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: from vcnet.vc.cvut.cz (vcnet.vc.cvut.cz [147.32.240.61]) by zikova.cvut.cz (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id XAA18236 for ; Mon, 6 May 2002 23:08:20 +0100 To: linux-fsdevel@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi, today it was pointed to me (see Debian bugreport #145654, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=145654) that all nls_iso8859-* mappings available in kernel refuse to map characters in range 0x80-0x9F to anything reasonable. This behavior means, that with NLS default set to any of iso8859-* encoding (including default iso-8859-1) filesystems which contain data in cp850/852/437 codepages will have bad problems, as majority of accented characters live in 0x80-0x9F range in these codepages. And worse is that old 2.2.x kernels defaulted to 1:1 mapping, so people were used to see wrong accented characters, but all filenames. Now whey see nothing :-( Is there any reason why 0x80-0x9F range is not mapped identically to 0x80-0x9F unicode range? I believe that unicode is even defined as have first 256 characters identical to iso8859-1. Thanks, Petr Vandrovec vandrove@vc.cvut.cz