From general-return-6026-apmail-xml-general-archive=xml.apache.org@xml.apache.org Mon May 13 04:04:49 2002 Return-Path: Delivered-To: apmail-xml-general-archive@xml.apache.org Received: (qmail 50815 invoked by uid 500); 13 May 2002 04:04:48 -0000 Mailing-List: contact general-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: general@xml.apache.org Delivered-To: mailing list general@xml.apache.org Received: (qmail 50796 invoked from network); 13 May 2002 04:04:47 -0000 Message-ID: <3CDF3B7A.5490DEB@apache.org> Date: Mon, 13 May 2002 13:05:14 +0900 From: Andy Clark X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: general@xml.apache.org CC: xerces-c-dev@xml.apache.org Subject: Re: [Announce] NekoHTML 0.6 Available References: <20020512160126.U1279-100000@fenris.webthing.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 13 May 2002 04:21:54.0386 (UTC) FILETIME=[B66C8320:01C1FA35] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Nick Kew wrote: > Has anyone given any thought to how well/easily this would port to > run under Xerces-C++? I might[1] take a look at that myself, so if > anyone has comments or experiences with it, please tell me! Aside from the fact that NekoHTML is written to work well within the XNI framework, the parser was written from the ground up with little reliance on the Xerces2 implementation. So porting to C++ should not be too difficult. But your question begs another: is anyone in the Xerces-C community considering re-working the C++ parser so that it is also built upon the XNI framework? -- Andy Clark * andyc@apache.org --------------------------------------------------------------------- In case of troubles, e-mail: webmaster@xml.apache.org To unsubscribe, e-mail: general-unsubscribe@xml.apache.org For additional commands, e-mail: general-help@xml.apache.org