From owner-freebsd-arch@FreeBSD.ORG  Wed Jul 30 19:38:21 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 3C333131;
 Wed, 30 Jul 2014 19:38:21 +0000 (UTC)
Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "funkthat.com", Issuer "funkthat.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 14A352AEF;
 Wed, 30 Jul 2014 19:38:20 +0000 (UTC)
Received: from h2.funkthat.com (localhost [127.0.0.1])
 by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id s6UJcJAu014435
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Wed, 30 Jul 2014 12:38:19 -0700 (PDT)
 (envelope-from jmg@h2.funkthat.com)
Received: (from jmg@localhost)
 by h2.funkthat.com (8.14.3/8.14.3/Submit) id s6UJcJUa014434;
 Wed, 30 Jul 2014 12:38:19 -0700 (PDT) (envelope-from jmg)
Date: Wed, 30 Jul 2014 12:38:19 -0700
From: John-Mark Gurney <jmg@funkthat.com>
To: Simon Gerraty <sjg@juniper.net>
Subject: Re: XML Output: libxo - provide single API to output TXT, XML,
 JSON and HTML
Message-ID: <20140730193819.GM43962@funkthat.com>
Mail-Followup-To: Simon Gerraty <sjg@juniper.net>, arch@freebsd.org,
 sjg@freebsd.org, marcel@freebsd.org, phil@juniper.net
References: <20140725044921.9F0D3580A2@chaos.jnpr.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140725044921.9F0D3580A2@chaos.jnpr.net>
User-Agent: Mutt/1.4.2.3i
X-Operating-System: FreeBSD 7.2-RELEASE i386
X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88  9322 9CB1 8F74 6D3F A396
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html
X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE
X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger?
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2
 (h2.funkthat.com [127.0.0.1]); Wed, 30 Jul 2014 12:38:19 -0700 (PDT)
Cc: sjg@freebsd.org, arch@freebsd.org, marcel@freebsd.org, 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: Wed, 30 Jul 2014 19:38:21 -0000

Simon Gerraty wrote this message on Thu, Jul 24, 2014 at 21:49 -0700:
> The main open issue (assuming this functionality is still desired) is
> support of wide charachters.
> 
> We figure the worst case solution is a sed(1) script to generate the wide
> version of the API from the normal one, but perhaps simply always using
> UTF8 would be a better solution?

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...  This
doesn't prevent a wide char API from also being present if someone
really wants to add it..

I would also like to see support for binary data, but as I mentioned,
that would prevent usage from outputing JSON...  Yes, you can hex encode
(why doesn't libc include a hex code/decode function) it, but then it
becomes harder to autodetect typing..

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."