From owner-freebsd-arch@FreeBSD.ORG Thu Jul 31 15:48:03 2014 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 62E50929; Thu, 31 Jul 2014 15:48:03 +0000 (UTC) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0239.outbound.protection.outlook.com [207.46.163.239]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C1682104; Thu, 31 Jul 2014 15:48:01 +0000 (UTC) Received: from BY2PR05CA051.namprd05.prod.outlook.com (10.141.250.41) by BLUPR05MB721.namprd05.prod.outlook.com (10.141.207.144) with Microsoft SMTP Server (TLS) id 15.0.995.14; Thu, 31 Jul 2014 15:32:23 +0000 Received: from BY2FFO11FD004.protection.gbl (2a01:111:f400:7c0c::159) by BY2PR05CA051.outlook.office365.com (2a01:111:e400:2c5f::41) with Microsoft SMTP Server (TLS) id 15.0.995.14 via Frontend Transport; Thu, 31 Jul 2014 15:32:23 +0000 Received: from P-EMF02-SAC.jnpr.net (66.129.239.16) by BY2FFO11FD004.mail.protection.outlook.com (10.1.14.158) with Microsoft SMTP Server (TLS) id 15.0.990.10 via Frontend Transport; Thu, 31 Jul 2014 15:32:22 +0000 Received: from magenta.juniper.net (172.17.27.123) by P-EMF02-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 31 Jul 2014 08:32:21 -0700 Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id s6VFWIn29075; Thu, 31 Jul 2014 08:32:18 -0700 (PDT) (envelope-from phil@juniper.net) Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.14.4/8.14.3) with ESMTP id s6VFVbJn094888; Thu, 31 Jul 2014 11:31:42 -0400 (EDT) (envelope-from phil@idle.juniper.net) Message-ID: <201407311531.s6VFVbJn094888@idle.juniper.net> To: Poul-Henning Kamp Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML In-Reply-To: <94841.1406796243@critter.freebsd.dk> Date: Thu, 31 Jul 2014 11:31:37 -0400 From: Phil Shafer MIME-Version: 1.0 Content-Type: text/plain X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:66.129.239.16; CTRY:US; IPV:NLI; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(6009001)(164054003)(199002)(189002)(48376002)(84676001)(87936001)(19580395003)(102836001)(85852003)(69596002)(80022001)(64706001)(47776003)(15202345003)(20776003)(83322001)(15975445006)(81342001)(4396001)(50466002)(92566001)(83072002)(76482001)(44976005)(110136001)(46102001)(6806004)(31966008)(107046002)(54356999)(103666002)(106466001)(74662001)(92726001)(86362001)(76506005)(85306003)(81156004)(97736001)(21056001)(50986999)(74502001)(79102001)(81542001)(105596002)(53416004)(99396002)(95666004)(77982001)(68736004); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR05MB721; H:P-EMF02-SAC.jnpr.net; FPR:; MLV:sfv; PTR:InfoDomainNonexistent; MX:1; LANG:en; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID: X-Forefront-PRVS: 0289B6431E Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.16 as permitted sender) Authentication-Results: spf=softfail (sender IP is 66.129.239.16) smtp.mailfrom=phil@juniper.net; X-OriginatorOrg: juniper.net Cc: sjg@freebsd.org, arch@freebsd.org, John-Mark Gurney , marcel@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2014 15:48:03 -0000 Poul-Henning Kamp writes: >The real question is how it will be perceived if we are *not* actively >going UTF-8 by that time? And moving toward UTF-8 won't be simple. I just tossed a couple of file from http://www.cl.cam.ac.uk/~mgk25/ucs/examples/ into a few apps that are supposed to support UTF-8 (emacs, vim, firefox) and the results were underwhelming. Skimming the description of xterm support for UTF-8 gives some appreciation for how complex this crap is (http://www.cl.cam.ac.uk/~mgk25/unicode.html#xterm). That said, I'm a bit tired of explaining to my kids why I'm typing in black and white terminal windows in the age of HTML5 ;^) Thanks, Phil