From owner-freebsd-arch@FreeBSD.ORG  Thu Jul 31 21:01:22 2014
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id EA710C9C;
 Thu, 31 Jul 2014 21:01:22 +0000 (UTC)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
 by mx1.freebsd.org (Postfix) with ESMTP id ACD832786;
 Thu, 31 Jul 2014 21:01:22 +0000 (UTC)
Received: from critter.freebsd.dk (unknown [192.168.48.2])
 by phk.freebsd.dk (Postfix) with ESMTP id 88A0616D2;
 Thu, 31 Jul 2014 21:01:21 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
 by critter.freebsd.dk (8.14.9/8.14.9) with ESMTP id s6VL1LVT058440;
 Thu, 31 Jul 2014 21:01:21 GMT (envelope-from phk@phk.freebsd.dk)
To: John-Mark Gurney <jmg@funkthat.com>
Subject: Re: XML Output: libxo - provide single API to output TXT, XML,
 JSON and HTML
In-reply-to: <20140731205054.GT43962@funkthat.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <94841.1406796243@critter.freebsd.dk>
 <201407311531.s6VFVbJn094888@idle.juniper.net>
 <20140731205054.GT43962@funkthat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <58438.1406840481.1@critter.freebsd.dk>
Date: Thu, 31 Jul 2014 21:01:21 +0000
Message-ID: <58439.1406840481@critter.freebsd.dk>
Cc: sjg@freebsd.org, arch@freebsd.org, marcel@freebsd.org,
 Phil Shafer <phil@juniper.net>
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jul 2014 21:01:23 -0000

--------
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.