From owner-freebsd-arch@FreeBSD.ORG Wed Jul 30 03:41:39 2014 Return-Path: Delivered-To: freebsd-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 4AE2DBAA for ; Wed, 30 Jul 2014 03:41:39 +0000 (UTC) Received: from smtp10.server.rpi.edu (gateway.canit.rpi.edu [128.113.2.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 049A62F26 for ; Wed, 30 Jul 2014 03:41:38 +0000 (UTC) Received: from smtp-auth1.server.rpi.edu (smtp-auth1.server.rpi.edu [128.113.2.231]) by smtp10.server.rpi.edu (8.14.3/8.14.3/Debian-9.4) with ESMTP id s6U3fbue008633 for ; Tue, 29 Jul 2014 23:41:37 -0400 Received: from smtp-auth1.server.rpi.edu (localhost [127.0.0.1]) by smtp-auth1.server.rpi.edu (Postfix) with ESMTP id 653C65806D for ; Tue, 29 Jul 2014 23:41:37 -0400 (EDT) Received: from [128.113.24.47] (gilead-im124.netel.rpi.edu [128.113.124.180]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drosih) by smtp-auth1.server.rpi.edu (Postfix) with ESMTPSA id 57C1D5800D for ; Tue, 29 Jul 2014 23:41:37 -0400 (EDT) From: "Garance A Drosehn" To: freebsd-arch@freebsd.org Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML Date: Tue, 29 Jul 2014 23:40:14 -0400 Message-ID: <1092D020-F782-4587-A199-C7313BC2CD20@rpi.edu> In-Reply-To: <448BB170-6DDC-442B-A5C5-973EC35FF7B9@rpi.edu> References: <20140725044921.9F0D3580A2@chaos.jnpr.net> <20140728054217.AC1A0580A2@chaos.jnpr.net> <20140728055336.GJ50802@ivaldir.etoilebsd.net> <20140729230345.31E9B580A2@chaos.jnpr.net> <53D85495.4050408@mu.org> <448BB170-6DDC-442B-A5C5-973EC35FF7B9@rpi.edu> MIME-Version: 1.0 X-Mailer: MailMate (1.7.2r3905) X-Virus-Scanned: ClamAV using ClamSMTP X-Bayes-Prob: 0.0001 (Score 0, tokens from: outgoing, @@RPTN) X-Spam-Score: 0.00 () [Hold at 15.10] X-CanIt-Incident-Id: 03MwrFBTJ X-CanIt-Geo: ip=128.113.124.180; country=US; region=New York; city=Troy; latitude=42.7495; longitude=-73.5951; http://maps.google.com/maps?q=42.7495,-73.5951&z=6 X-CanItPRO-Stream: outgoing X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.230 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: Wed, 30 Jul 2014 03:41:39 -0000 On 29 Jul 2014, at 23:19, Garance A Drosehn wrote: > > In any case, I am interested to see how the GSOC project works out, or > whatever happens with this libxo project. I also wanted to highlight an issue that Simon brought up in the initial message for this thread: "The main open issue (assuming this functionality is still desired) is support of wide characters. 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?" In my own experiments I've pretended that all the output 'lpq' generates is simple ascii, although that's not necessarily true. The filename field is set by whatever generated the output, which might be a PC or Mac which may or may not be unicode-aware. The field might be gibberish (aka "invalid unicode"). Obviously "pretending" is the wrong way to handle this issue. -- Garance Alistair Drosehn = drosih@rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA