From owner-freebsd-arch@FreeBSD.ORG Thu Jul 31 20:50:57 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 329CB568; Thu, 31 Jul 2014 20:50:57 +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 E42B325ED; Thu, 31 Jul 2014 20:50:56 +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 s6VKot8Z034481 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 Jul 2014 13:50:55 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s6VKosKB034480; Thu, 31 Jul 2014 13:50:54 -0700 (PDT) (envelope-from jmg) Date: Thu, 31 Jul 2014 13:50:54 -0700 From: John-Mark Gurney To: Phil Shafer Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML Message-ID: <20140731205054.GT43962@funkthat.com> Mail-Followup-To: Phil Shafer , Poul-Henning Kamp , sjg@freebsd.org, arch@freebsd.org, marcel@freebsd.org References: <94841.1406796243@critter.freebsd.dk> <201407311531.s6VFVbJn094888@idle.juniper.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201407311531.s6VFVbJn094888@idle.juniper.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]); Thu, 31 Jul 2014 13:50:56 -0700 (PDT) Cc: sjg@freebsd.org, arch@freebsd.org, Poul-Henning Kamp , 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 20:50:57 -0000 Phil Shafer wrote this message on Thu, Jul 31, 2014 at 11:31 -0400: > 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 If we don't start, we won't ever move forward... > 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) Why not nvi? :) I just tried out nvi w/ UTF-8-demo.txt, and was surprised that it worked well.. there are issues w/ combining characters, both stargate and Thai, but that's an issue w/ nvi escaping those characters instead of displaying them.. my terminal was Terminal.app from MacOSX... less and more appear to work, and handle the combining characters properly... vt works, but we need much better font support.. The default font is missing lots of math, linguistic, APL, georgian, Thai, Amharic, runes (though MacOS's font I'm using misses these too), Braille (this should be easy for anyone to add), and I believe Japanese... > 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). I must say, from my brief test, I'm surprised it worked as well as it did... :) -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."