From general-return-5903-apmail-xml-general-archive=xml.apache.org@xml.apache.org Wed Apr 10 14:45:46 2002 Return-Path: Delivered-To: apmail-xml-general-archive@xml.apache.org Received: (qmail 49930 invoked by uid 500); 10 Apr 2002 14:45:43 -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 49916 invoked from network); 10 Apr 2002 14:45:42 -0000 Message-ID: <3CB4501E.1DFC9924@apache.org> Date: Wed, 10 Apr 2002 23:45:50 +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 Subject: Re: HTML Parser Update Available References: <3CA98771.9CC96B3F@apache.org> <3CB40C4A.1660A0A4@gis-systemhaus.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Apr 2002 14:59:49.0271 (UTC) FILETIME=[5C66BA70:01C1E0A0] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Harald Hett wrote: > Why are the elements converted to upper case? Wouldn't it be nice to > be able to change this feature between the three states (1) do nothing, > (2) convert to uppercase, (3) convert to lowercase? I was thinking about this actually. It would be very easy to add, actually -- it's just a matter of picking the appropriate way to handle this. Since there are three states, a feature (as in the "setFeature" method) doesn't seem to fit. But it would seem weird to use a property. Or maybe not... Which would you rather prefer? 1) Two features, for example: "http://cyberneko.org/html/names/modify" { true, false } "http://cyberneko.org/html/names/uppercase" { true, false } OR... 2) A property, for example: "http://cyberneko.org/html/names/modify" { "upper", "lower", "default" } [These are just examples. I might want to modify the names.] > Is it planned to include NekoHTML into the Xerces release? There hasn't been an overwelming demand for it. Although, a few people responded and said it would generally be a "good" thing to include with Xerces. Certainly if there is a need for it, I wouldn't mind rolling it into the codebase -- it's actually quite small so it wouldn't add a lot to the source or Jar file(s). What do people think? -- 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