From owner-freebsd-hackers@FreeBSD.ORG Sun Mar 2 09:54:15 2014 Return-Path: Delivered-To: hackers@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 C31A2D77 for ; Sun, 2 Mar 2014 09:54:15 +0000 (UTC) Received: from mail-ee0-x22d.google.com (mail-ee0-x22d.google.com [IPv6:2a00:1450:4013:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 543E61200 for ; Sun, 2 Mar 2014 09:54:15 +0000 (UTC) Received: by mail-ee0-f45.google.com with SMTP id d17so3248771eek.18 for ; Sun, 02 Mar 2014 01:54:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=GuTAGOFGpuL9dSKGGthrIbFroRA2PqJ5/ElSUjJuDjE=; b=zV/zt8R00/HuWKZGlvBzaxyEdvbsJOyBQAhDAaFEmgn87esC/UbBVKqvyYKvWcjNux SDHP3RcQUcahyyY4Kb8TWFMfKiTOEB05zuMEgNlpL3yN2+H7S5aiLgckdg2zoh0Rt5hp ekmN+qD88OGVb+VIw9c7Z55TVKFACSbpJhsZcrHvuDChhSghy+8qZFebF5YwdlIVSEgf Gl2iPejlP5IR1iMOkiwNvLCPLXRIOHjA6bEEI4S1l7FWSUKfR4SASg/bq147wzzYxrb0 Qwd6slX6kM3Nox7vI62tXg0xTFoNbt++RlGgBgcPZpUbX4Ql6ohDyuQyQy/lie0F47aY BN5A== X-Received: by 10.15.65.68 with SMTP id p44mr31981425eex.63.1393754053288; Sun, 02 Mar 2014 01:54:13 -0800 (PST) Received: from strashydlo.home (adha144.neoplus.adsl.tpnet.pl. [79.184.156.144]) by mx.google.com with ESMTPSA id o43sm34517528eef.12.2014.03.02.01.54.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 02 Mar 2014 01:54:12 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Subject: Re: GSoC proposal: Quirinus C library (qc) Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=iso-8859-2 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= In-Reply-To: <20140227182641.GE47921@funkthat.com> Date: Sun, 2 Mar 2014 10:54:09 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <5A166BC2-D34A-473C-BEFA-9E04760A0AAB@FreeBSD.org> References: <20140227182641.GE47921@funkthat.com> To: John-Mark Gurney X-Mailer: Apple Mail (2.1283) Cc: Jordan Hubbard , =?iso-8859-2?Q?=3F=3Fukasz_W=F3jcik?= , hackers@freebsd.org, ghostmansd@gmail.com, =?iso-8859-2?Q?Fernando_Apestegu=EDa?= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Mar 2014 09:54:15 -0000 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").