From owner-freebsd-arch@FreeBSD.ORG Sun Jan 25 17:10:47 2015 Return-Path: Delivered-To: arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A61715E6; Sun, 25 Jan 2015 17:10:47 +0000 (UTC) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 5E77BB80; Sun, 25 Jan 2015 17:10:47 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1YFQhu-000MlR-Lv; Sun, 25 Jan 2015 20:10:42 +0300 Date: Sun, 25 Jan 2015 20:10:42 +0300 From: Slawa Olhovchenkov To: Poul-Henning Kamp Subject: Re: [RFC] Set the default locale to en_US.UTF-8 Message-ID: <20150125171042.GQ3698@zxy.spb.ru> References: <20150124143357.GI81001@ivaldir.etoilebsd.net> <20150125143243.GB76051@zxy.spb.ru> <7B1D8345-248B-4C44-9568-079BA29614C2@ixsystems.com> <23506.1422204612@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <23506.1422204612@critter.freebsd.dk> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: arch@FreeBSD.org, Baptiste Daroussin , Jordan Hubbard X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2015 17:10:47 -0000 On Sun, Jan 25, 2015 at 04:50:12PM +0000, Poul-Henning Kamp wrote: > -------- > In message <7B1D8345-248B-4C44-9568-079BA29614C2@ixsystems.com>, Jordan Hubbard > writes: > > The point about vi(1) is that if you happen to open an ISO-8859 file > while in UTF-8 mode, change something on the first line, it will > happily and almost imperceptively truncate your file at the first > non-UTF byte sequence. > > Needless to say, that is *not* the expected behaviour. I can't remember other cases, but vi(1) is not exclusion. Similar cases will be with some like sed/grep. I think this behaviour must be stopper to _upgrade_ locale on existing installations. System software (from FreeBSD base) not exclusive for this behaviour (dangerous dependens from current locale). This is may be third-party sofware or software writen by customer. Unexpected setting locale to UTF-8 may be broken this software. For new install setting locale to UTF-8 will be ok.