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 C97891382C5 for ; Wed, 30 Dec 2020 08:44:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3303EE0BC7; Wed, 30 Dec 2020 08:44:16 +0000 (UTC) Received: from smtp.hosts.co.uk (smtp.hosts.co.uk [85.233.160.19]) (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 BCE94E0B93 for ; Wed, 30 Dec 2020 08:44:15 +0000 (UTC) Received: from host86-158-105-41.range86-158.btcentralplus.com ([86.158.105.41] helo=[192.168.1.64]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1kuX5Z-0005oZ-7I for gentoo-user@lists.gentoo.org; Wed, 30 Dec 2020 08:44:13 +0000 Subject: Re: [gentoo-user] Re: ncurses; I think I wrecked my fresh install To: gentoo-user@lists.gentoo.org References: <9095281.eNJFYEL58v@noumea> From: Wols Lists Message-ID: <5FEC4722.8070900@youngman.org.uk> Date: Wed, 30 Dec 2020 09:23:46 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 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 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Archives-Salt: b5f3ae7f-481e-4665-ae44-444b33534f93 X-Archives-Hash: f52501fe4d928fb474142433e4324c3e On 30/12/20 01:04, Grant Edwards wrote: > 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. There is utf-16 - MS's default version. They wrote their unicode support *before* utf-8 really was a thing. So we have the nix's settling on an 8-bit char, and MS settling on a 16-bit char BEFORE that. Unbaking that mess would be fun ... So that file is probably something to do with MS and ASCII-16 :-) Cheers, Wol