Date: Thu, 4 Apr 2019 21:06:43 +0200 From: Matthias Apitz <guru@unixarea.de> To: freebsd-questions@freebsd.org Subject: Re: vi(1) and ISO 8859-1 Message-ID: <20190404190642.GA4609@sh4-5.1blu.de> In-Reply-To: <trinity-f25766ad-e745-4e70-98d1-52c0ba83fe56-1554398089214@3c-app-mailcom-lxa05> References: <trinity-f25766ad-e745-4e70-98d1-52c0ba83fe56-1554398089214@3c-app-mailcom-lxa05>
next in thread | previous in thread | raw e-mail | index | archive | help
El día Thursday, April 04, 2019 a las 07:14:49PM +0200, Rocky Hotas escribió: > Hello! > I have an ISO-8859-1 text file, which is opened and shared by several OSs. > If I open it with vi(1) in FreeBSD 12.0, its encoding is not detected and > UTF-8 is used, instead. Any non-ascii character will be read and written > incorrectly in UTF-8, creating an ambiguous encoding. Are you sure that the file is completely ISO-8859-1 encoded? What does file(1) says about and what happens if you run it through iconv(1) translating from ISO-8859-1 to UTF-8 into /dev/null, will iconv(1) do it or complain? matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub 70 years of NATO - 70 years of wars (Jugoslavia, Afghanistan, Syria, ...) and 70 years of war preparation against Russia. -- PEACE instead of NATO !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190404190642.GA4609>