From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 6BC841382C5 for ; Wed, 30 Dec 2020 01:04:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 12D76E0D68; Wed, 30 Dec 2020 01:04:28 +0000 (UTC) Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B7D46E0D4D for ; Wed, 30 Dec 2020 01:04:27 +0000 (UTC) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1kuPuc-0007hw-CJ for gentoo-user@lists.gentoo.org; Wed, 30 Dec 2020 02:04:26 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Grant Edwards Subject: [gentoo-user] Re: ncurses; I think I wrecked my fresh install Date: Wed, 30 Dec 2020 01:04:21 -0000 (UTC) Message-ID: References: <9095281.eNJFYEL58v@noumea> User-Agent: slrn/1.0.3 (Linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: 53527614-b397-4cca-80ab-63edeb05f9dd X-Archives-Hash: b851e22b85ce046610b3b0590308e066 On 2020-12-29, Walter Dnes wrote: > On Tue, Dec 29, 2020 at 05:11:36PM +0200, Andreas K. Huettel wrote >> Hi Walter, >> >> > "-pch -roaming -sendmail -spell -tcpd -udev -udisks -unicode -upower >> > -xinerama" >> >> mostly out of curiosity, why do you want to disable unicode support >> here? >> >> This feels odd to me since utf8 has effectively become the standard >> encoding over the past years. > > I don't know if this has improved over the years, but my initial > experience with unicode was rather negative. The fact that text > files were twice as large wasn't a major problem in itself. The > real showstopper was that importing text files into spreadsheets > and text-editors and word processors failed miseraby. You must be talking about some sort of weird "wide" encoding (is there such a thing as UTF-16?). I've never seen a file like that. Everybody and everything uses UTF-8 these days and has for years. UTF-8 is a superset of ASCII, and doesn't increase size of the file unless non-ascii characters are used. Converting an ASCII file to UTF-8 encoding is a noop. An ASCII file _is_ UTF-8. > I looked at a unicode text file with a binary viewer. It turns out > that a simple text string like "1234" was actually... > > "1" binary-zero "2" binary-zero "3" binary-zero "4" binary zero, etc. > > This padding explains why the file was twice as large, and also why > "a simple textfile import" failed miserably. I've never seen a file like that. All the Unicode I run into is UTF-8, and a UTF-8 file with the string "1234" is the same exact 4 bytes as an ASCII file with the string "1234". > On top of that Cyrillic letters like "m", "i", "c", and "o" are > considered different from their English equivalants. Security experts > showed proof-of-cocept attacks where clicking on "microsoft.com" can > take you to a hostile domain (queue the jokes). I don't speak or read > or write any languages which have thousands of unique characters. > Seeing Chinese spam "as it was intended to be seen", is not a priority > for me.