From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 27 18:26:43 2014 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D1AE7B71 for ; Thu, 27 Feb 2014 18:26:43 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8D30C1623 for ; Thu, 27 Feb 2014 18:26:43 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s1RIQgQE059013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Feb 2014 10:26:43 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s1RIQfW1059012; Thu, 27 Feb 2014 10:26:41 -0800 (PST) (envelope-from jmg) Date: Thu, 27 Feb 2014 10:26:41 -0800 From: John-Mark Gurney To: ghostmansd@gmail.com Subject: Re: GSoC proposal: Quirinus C library (qc) Message-ID: <20140227182641.GE47921@funkthat.com> Mail-Followup-To: ghostmansd@gmail.com, hackers@freebsd.org, Jordan Hubbard , ??ukasz =?iso-8859-1?Q?W=F3jcik?= , Fernando =?iso-8859-1?Q?Apestegu=EDa?= References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Thu, 27 Feb 2014 10:26:43 -0800 (PST) Cc: Jordan Hubbard , ??ukasz =?iso-8859-1?Q?W=F3jcik?= , hackers@freebsd.org, Fernando =?iso-8859-1?Q?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: Thu, 27 Feb 2014 18:26:43 -0000 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. 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... 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? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."