Date: Thu, 03 Jul 2014 10:50:13 +0200 From: dt71@gmx.com To: Kevin Lo <kevlo@FreeBSD.org> Cc: freebsd-current@freebsd.org, David Chisnall <theraven@FreeBSD.org> Subject: Re: freebsd and utf-8 directory names Message-ID: <53B51945.4080202@gmx.com> In-Reply-To: <20140703033313.GA44200@ns.kevlo.org> References: <3B0F582294DE3E448963BA62DC306AEE3C7F5FBCEC@exchange.mands.hu> <53B2C8B4.50306@gmx.com> <7C6EC1A0-520F-49CA-8C05-1F3205080543@FreeBSD.org> <53B335BB.5090402@gmx.com> <20140703033313.GA44200@ns.kevlo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Lo wrote, On 07/03/2014 05:33: > On Wed, Jul 02, 2014 at 12:27:07AM +0200, dt71@gmx.com wrote: >> But now, eat this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191540 > > Well, I'm going to close that PR. :-) > First, > [...] > Let me know if that works for you, thanks. Yes, that did work. When I'll have more time and resources, I'll try to find out why/what didn't work at the time of the IRC conversation. It is possible that Windows was using something like UTF-16, but I tested only UTF-8 -- though the apparent unavailability of any UTF-16 locale on my system indicates that base FreeBSD installations are not able to properly mount commonly-used FAT32 partitions (think about flash drives). Another "next step" is to find out whether a regular user can set a locale environment variable and then create a file that system utilities -- which have one pre-set locale -- (think about disk space usage quota enforcers) won't handle well.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53B51945.4080202>