Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:22870
Return-Path: <john@coggeshall.org>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 96824 invoked by uid 1010); 19 Apr 2006 18:05:46 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 96809 invoked from network); 19 Apr 2006 18:05:46 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 19 Apr 2006 18:05:46 -0000
X-Host-Fingerprint: 69.56.217.178 b2.d9.3845.static.theplanet.com Linux 2.4/2.6
Received: from ([69.56.217.178:49940] helo=coggeshall.org)
	by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP
	id 91/FC-19715-AFB76444 for <internals@lists.php.net>; Wed, 19 Apr 2006 14:05:46 -0400
Received: from [192.168.1.234] (69-162-207-15.bflony.adelphia.net [69.162.207.15])
	(authenticated bits=0)
	by coggeshall.org (8.12.8/8.12.8) with ESMTP id k3JHdpSe030678
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Wed, 19 Apr 2006 12:39:52 -0500
To: Steph Fox <steph@zend.com>
Cc: Nuno Lopes <nlopess@php.net>, internals <internals@lists.php.net>,
	Edin <edink@emini.dk>
In-Reply-To: <0a4301c663ac$9cc9bf70$6602a8c0@foxbox>
References: <09f201c6639c$c8fe39f0$6602a8c0@foxbox>
	<0a0a01c663a0$755b4230$6602a8c0@foxbox>
	<008b01c6639d$f39177d0$0100a8c0@pc07653>
	<0a1f01c663a6$f49711e0$6602a8c0@foxbox>
	<00a201c6639f$bee582e0$0100a8c0@pc07653>
	<0a4301c663ac$9cc9bf70$6602a8c0@foxbox>
Content-Type: text/plain
Date: Wed, 19 Apr 2006 14:01:07 -0400
Message-ID: <1145469667.21753.5.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-6) 
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] tiny patch for Tidy
From: john@coggeshall.org (John Coggeshall)

On Wed, 2006-04-19 at 14:27 +0200, Steph Fox wrote:
> Really this is down to John Coggeshall (as maintainer) - unless someone else 
> feels like going and finding a newer version of libtidy and testing it with 
> the existing extension(s) - e.g. would a newer version also bring other new 
> functions that aren't wrapped in the extension(s) currently?

I can try to find some time and take a look at what is in the most up to
date libtidy and add the functionality to the extension if it makes
sense. However, even then I never was the one to get it working in
Windows :) 

John