From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 22:27:45 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 027D2131 for ; Tue, 1 Jul 2014 22:27:45 +0000 (UTC) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C16D825F5 for ; Tue, 1 Jul 2014 22:27:44 +0000 (UTC) Received: from [157.181.96.215] ([157.181.96.215]) by mail.gmx.com (mrgmxus002) with ESMTPSA (Nemesis) id 0Lu8BM-1WcQPL3PJ0-011Vex; Wed, 02 Jul 2014 00:27:42 +0200 Message-ID: <53B335BB.5090402@gmx.com> Date: Wed, 02 Jul 2014 00:27:07 +0200 From: dt71@gmx.com User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26 MIME-Version: 1.0 To: David Chisnall Subject: Re: freebsd and utf-8 directory names References: <3B0F582294DE3E448963BA62DC306AEE3C7F5FBCEC@exchange.mands.hu> <53B2C8B4.50306@gmx.com> <7C6EC1A0-520F-49CA-8C05-1F3205080543@FreeBSD.org> In-Reply-To: <7C6EC1A0-520F-49CA-8C05-1F3205080543@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:ETvRjaUHgIgBe3JsSeFeC1KZ9+Dtb52XFreATT+7jaxlf1i2Mtj CSVMl+HagYrdT8u9ZwbHDbYvXov0hjxSRAWzlK+VPUrfvJauvqVpNzo88jz8h4UHQwAIrPf iPAfS1soY7CA1Hej+WtyxFnZ4KbbJZdYigsAwdyeSY/s29V9gXPaWIjDFPn+0NyZzsgMAkA PccxyTYiod+2vjKym4UWQ== Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2014 22:27:45 -0000 David Chisnall wrote, On 07/01/2014 19:06: > Please note that forums.freebsd.org is not a bug tracker. I tried searching the bug tracker for bugs with FAT and filename or FAT and utf-8/utf8/character in their names and could not find any reference to this issue. > > If you actually want to see bugs fixed, rather than just complain about them, please file them here: https://bugs.freebsd.org/bugzilla/enter_bug.cgi Make sure that you provide all of the steps required to reproduce them. I neglected to submit a bug report because: (1) there were already at least 3 bug reports related to (FAT32 and) character sets or encodings, some of them even had patches; (2) the reports were very old, indicating that the FreeBSD developers don't care about FAT32; (3) at least one report was seemingly related, and I didn't want to create a(nother) possible duplicate. But now, eat this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191540