From owner-freebsd-arch@FreeBSD.ORG  Thu Jul 31 08:44:14 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 62795AD6;
 Thu, 31 Jul 2014 08:44:14 +0000 (UTC)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
 by mx1.freebsd.org (Postfix) with ESMTP id 25E102B1C;
 Thu, 31 Jul 2014 08:44:13 +0000 (UTC)
Received: from critter.freebsd.dk (unknown [192.168.48.2])
 by phk.freebsd.dk (Postfix) with ESMTP id 505101578;
 Thu, 31 Jul 2014 08:44:06 +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 s6V8i33h094842;
 Thu, 31 Jul 2014 08:44:03 GMT (envelope-from phk@phk.freebsd.dk)
To: Phil Shafer <phil@juniper.net>
Subject: Re: XML Output: libxo - provide single API to output TXT, XML,
 JSON and HTML
In-reply-to: <201407302324.s6UNOB2H087915@idle.juniper.net>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <201407302324.s6UNOB2H087915@idle.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <94840.1406796243.1@critter.freebsd.dk>
Date: Thu, 31 Jul 2014 08:44:03 +0000
Message-ID: <94841.1406796243@critter.freebsd.dk>
Cc: sjg@freebsd.org, arch@freebsd.org, John-Mark Gurney <jmg@funkthat.com>,
 marcel@freebsd.org
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 08:44:14 -0000

--------
In message <201407302324.s6UNOB2H087915@idle.juniper.net>, Phil Shafer writes:
>John-Mark Gurney writes:

>>My vote would be to use and *enforce* UTF-8 by the API.   That means if
>>someone passes a string in, it must be properly formed UTF-8...

Given that libxo is just now starting to stare at trunk and that
the next .0 release is some way of still, the consequences of
enforcing UTF-8 will not be seen by users at large until mid 2015
or so.

The real question is how it will be perceived if we are *not* actively
going UTF-8 by that time?

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