Date: Thu, 31 Jul 2014 08:44:03 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Phil Shafer <phil@juniper.net> Cc: sjg@freebsd.org, arch@freebsd.org, John-Mark Gurney <jmg@funkthat.com>, marcel@freebsd.org Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML Message-ID: <94841.1406796243@critter.freebsd.dk> In-Reply-To: <201407302324.s6UNOB2H087915@idle.juniper.net> References: <201407302324.s6UNOB2H087915@idle.juniper.net>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?94841.1406796243>