Date: Sun, 2 Mar 2014 10:54:09 +0100 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= <trasz@FreeBSD.org> To: John-Mark Gurney <jmg@funkthat.com> Cc: Jordan Hubbard <jkh@turbofuzz.com>, =?iso-8859-2?Q?=3F=3Fukasz_W=F3jcik?= <lukasz.wojcik@zoho.com>, hackers@freebsd.org, ghostmansd@gmail.com, =?iso-8859-2?Q?Fernando_Apestegu=EDa?= <fernando.apesteguia@gmail.com> Subject: Re: GSoC proposal: Quirinus C library (qc) Message-ID: <5A166BC2-D34A-473C-BEFA-9E04760A0AAB@FreeBSD.org> In-Reply-To: <20140227182641.GE47921@funkthat.com> References: <CAMqzjevahZowxWv0gH=Z8jjQdzGsEaA5U_VB-zsLCcwtoWkvxA@mail.gmail.com> <20140227182641.GE47921@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Wiadomo=B6=E6 napisana przez John-Mark Gurney w dniu 27 lut 2014, o =
godz. 19:26:
> Dmitry Selyutin wrote this message on Thu, Feb 27, 2014 at 19:39 =
+0400:
>> As for strings, I will not use UTF-16 since it provides more problems
>> rather than solutions. If I provide a function which accepts char* or =
char
>> const* argument, I imply that such function uses only ASCII (may be I =
will
>> change ASCII to UTF-8). Encoding is used only if a user has requested =
it
>> explicitly; the only place where I have made exception is system path =
since
>> path requires to be in UTF-16 on Windows. That is the reason why =
qc_path
>> requires qc_codecs-related functions.
>=20
> You do realize that FreeBSD does not enforce any coding on path names
> current, correct? So, requiring a coding format on FreeBSD (UTF-16)
> will mean some paths may not be accessible, since I assume you conver
> the UTF-16 string to UTF-8 before opening on FreeBSD...
>=20
> Hmm.. maybe it's time for a sysctl you can set on your system that
> only allows you to create UTF-8 valid names to allow people to slowly
> migrate to UTF-8? and a tool to report/convert old non-UTF-8 paths?
There's already a ZFS property ("utfmode") exactly for this purpose.
Actually, its funnier than that: because the kernel doesn't know =
anything
about UTF-8, one can create several files with the same name, but with
different UTF-8 encodings. And there is ZFS property to fix this =
problem
as well ("normalization").
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5A166BC2-D34A-473C-BEFA-9E04760A0AAB>