Date: Thu, 31 Jul 2014 21:01:21 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: John-Mark Gurney <jmg@funkthat.com> Cc: sjg@freebsd.org, arch@freebsd.org, marcel@freebsd.org, Phil Shafer <phil@juniper.net> Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML Message-ID: <58439.1406840481@critter.freebsd.dk> In-Reply-To: <20140731205054.GT43962@funkthat.com> References: <94841.1406796243@critter.freebsd.dk> <201407311531.s6VFVbJn094888@idle.juniper.net> <20140731205054.GT43962@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <20140731205054.GT43962@funkthat.com>, John-Mark Gurney writes: >Phil Shafer wrote this message on Thu, Jul 31, 2014 at 11:31 -0400: >Why not nvi? :) I just tried out nvi w/ UTF-8-demo.txt, and was >surprised that it worked well.. Having seen peter brave the wemm-field and go utf-8 I recently converted too and most stuff seems to work without trouble. What doesn't work with nvi is that it *recently* started mangling files with invalid byte sequences no matter what charset you set it for except 'C'. I write recently, because I'm quite sure it started in the last year or so, before that it did the right thing. You do get a warning on reading in the file if there are conversion issues, but I really think nvi should be able to edit any file, no matter what charset you have set for it, and invalid byte sequences should just show up as hex-expansions like they do in 'C' mode. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?58439.1406840481>