From owner-freebsd-bugs@freebsd.org Sat Nov 11 20:22:35 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D71CDE72FCC for ; Sat, 11 Nov 2017 20:22:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C64796DA54 for ; Sat, 11 Nov 2017 20:22:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vABKMZa9035827 for ; Sat, 11 Nov 2017 20:22:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 223598] ls utf output Date: Sat, 11 Nov 2017 20:22:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bsd@haps.ca X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Nov 2017 20:22:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223598 --- Comment #6 from bsd@haps.ca --- Ah, this is all very interesting, the -w option seems to be exactly what is needed. It seems further that the LANG setting will cause a re-interpretat= ion of what is 'printable'. However, maybe I'm just confused about this, but it seems unlikely that 'ls' should try to determine what is 'printable' beyond truly unprintable characters (control chars, etc). In reality, support by a font would be more indicative of what is printable, and ls would have no way of determining that. The fact that -w shows print= ed characters on my linux terminal, but not on my freebsd terminal, is due to = the font support. It still seems to me 'bug'-ish that without any locale, printable but non-a= scii characters are converted to '?'. It seems counter-intuitive that a charact= er belonging to a different alphabet would be considered 'non-printable'. The characters that come to mind as 'non-printable' are things like CR, LF, EOL. --=20 You are receiving this mail because: You are the assignee for the bug.=