Date: Sun, 25 Jan 2015 20:10:42 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: arch@FreeBSD.org, Baptiste Daroussin <bapt@FreeBSD.org>, Jordan Hubbard <jkh@ixsystems.com> Subject: Re: [RFC] Set the default locale to en_US.UTF-8 Message-ID: <20150125171042.GQ3698@zxy.spb.ru> In-Reply-To: <23506.1422204612@critter.freebsd.dk> References: <20150124143357.GI81001@ivaldir.etoilebsd.net> <20150125143243.GB76051@zxy.spb.ru> <7B1D8345-248B-4C44-9568-079BA29614C2@ixsystems.com> <23506.1422204612@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150125171042.GQ3698>