From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Newsgroups: gmane.lisp.guile.user Subject: Re: guile can't find a chinese named file Date: Tue, 31 Jan 2017 13:20:40 +0100 Message-ID: <20170131122040.GB8373@tuxteam.de> References: <874m0gd3z4.fsf@gnu.org> <87wpdc8rx7.fsf@elektro.pacujo.net> <87poj4r04c.fsf@fencepost.gnu.org> <87k29c8q3b.fsf@elektro.pacujo.net> <87h94gqz34.fsf@fencepost.gnu.org> <87fuk0ctve.fsf@elektro.pacujo.net> <878tpsqtzl.fsf@fencepost.gnu.org> <87zii8bcdw.fsf@elektro.pacujo.net> <83r33kwd24.fsf@gnu.org> <87tw8gb7j1.fsf@elektro.pacujo.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed X-Trace: blaine.gmane.org 1485865278 32584 195.159.176.226 (31 Jan 2017 12:21:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2017 12:21:18 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: guile-user@gnu.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Tue Jan 31 13:21:11 2017 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cYXQt-0008Dk-KO for guile-user@m.gmane.org; Tue, 31 Jan 2017 13:21:11 +0100 Original-Received: from localhost ([::1]:37481 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYXQy-00055Y-VU for guile-user@m.gmane.org; Tue, 31 Jan 2017 07:21:16 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46324) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYXQd-00055P-CB for guile-user@gnu.org; Tue, 31 Jan 2017 07:20:56 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cYXQY-0004Ho-E4 for guile-user@gnu.org; Tue, 31 Jan 2017 07:20:55 -0500 Original-Received: from mail.tuxteam.de ([5.199.139.25]:38850 helo=tomasium.tuxteam.de) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cYXQY-0004Gp-7s for guile-user@gnu.org; Tue, 31 Jan 2017 07:20:50 -0500 Original-Received: from tomas by tomasium.tuxteam.de with local (Exim 4.80) (envelope-from ) id 1cYXQO-0002UP-IG for guile-user@gnu.org; Tue, 31 Jan 2017 13:20:40 +0100 In-Reply-To: <87tw8gb7j1.fsf@elektro.pacujo.net> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 5.199.139.25 X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Original-Sender: "guile-user" Xref: news.gmane.org gmane.lisp.guile.user:13160 Archived-At: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Jan 30, 2017 at 10:46:26PM +0200, Marko Rauhamaa wrote: [...] > You are jumping the gun. Linux won't be there for a long time if ever. > Nothing prevents a pathname, or a command-line argument, or an > environment variable, or the standard input from containing illegal > UTF-8. To put more emphasis on this point: as things stand, you won't be able to avoid having paths with illegal UTF-8. Consider mounting a file system with UTF-8 file names over one containing Latin-1 file names. Then even if both are consistent in themselves (a far stretch, because there might be multiple apps under multiple locales creating and naming files), the combined path might be bad UTF-8 As long as the OS keeps out of this business I guess the application will need a "layer" from which to look at paths (and env variables and argv and all that) as mere byte sequences, before any interpretation takes place. > (Also note that even Windows allows pathnames with illegal Unicode in > them if I'm not mistaken.) This is so Microsoft: the file name character set in the file system is Unicode... except when it isn't :-) regards - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAliQgRgACgkQBcgs9XrR2kaOFwCeLo5oUgkTM9NPWo2aK+1SRObY 3yoAniTL3HgxPqh1mdXMx774fmohmnYb =YuFv -----END PGP SIGNATURE-----