From owner-freebsd-questions Wed Feb 5 17:18:29 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93EF237B401 for ; Wed, 5 Feb 2003 17:18:28 -0800 (PST) Received: from mired.org (ip68-97-54-220.ok.ok.cox.net [68.97.54.220]) by mx1.FreeBSD.org (Postfix) with SMTP id 88F3B43F3F for ; Wed, 5 Feb 2003 17:18:21 -0800 (PST) (envelope-from mwm-dated-1044926294.fb46ab@mired.org) Received: (qmail 96617 invoked from network); 6 Feb 2003 01:18:14 -0000 Received: from localhost.mired.org (HELO guru.mired.org) (127.0.0.1) by localhost.mired.org with SMTP; 6 Feb 2003 01:18:14 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <15937.47061.743702.496178@guru.mired.org> Date: Wed, 5 Feb 2003 19:18:13 -0600 To: Walter Cc: Questions Subject: Re: handling non-printable characters in file names In-Reply-To: <3E41A24E.9090607@earthlink.net> References: <3E41A24E.9090607@earthlink.net> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: Mike Meyer X-Delivery-Agent: TMDA/0.69 (Count Fleet) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In <3E41A24E.9090607@earthlink.net>, Walter ty= ped: > There's probably someone who can explain why non- > printable characters are useful in file names, but > I'd really rather disallow them altogether - if > there's a build option or control flag to set. > Anyone? BSD is character-set neutral. Well, it tries. The only two characters that are magic in file names are 0x2f and 0x00, because they both terminate the file name. Other than that, you are free to use whatever character encoding you want to. That's why characters that may be unprintable in some encodings are allowed in file names. What shows up in the locale en_US.ISO8859-1 as "Resum=E9" will show up with an unprintable last character if you haven't set the LANG environment variable. The only way to change this behavior is to change the kernel source to support it. Expect resistance from every developer in a country that doesn't use the English alphabet if you try and get that change put into the tree. =09=09=09http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more inform= ation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message