Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 40948 invoked from network); 18 May 2000 08:13:31 -0000 Received: from mailgate2.uea.ac.uk (139.222.230.101) by locus.apache.org with SMTP; 18 May 2000 08:13:31 -0000 Received: from [139.222.130.16] (helo=mailserver1.uea.ac.uk) by mailgate2.uea.ac.uk with esmtp (Exim 3.02 #1) id 12sLQx-0008ZV-00 for cocoon-dev@xml.apache.org; Thu, 18 May 2000 09:13:31 +0100 Received: from [139.222.129.44] (helo=luminas.penguinpowered.com ident=mail) by mailserver1.uea.ac.uk with esmtp (Exim 3.02 #1) id 12sLQx-0006WT-00 for cocoon-dev@xml.apache.org; Thu, 18 May 2000 09:13:31 +0100 Received: from paulr by luminas.penguinpowered.com with local (Exim 2.05 #1 (Debian)) id 12sLQw-00008Z-00; Thu, 18 May 2000 09:13:30 +0100 Date: Thu, 18 May 2000 09:13:30 +0100 From: Paul Russell To: cocoon-dev@xml.apache.org Subject: Re: External Entities & bundles Message-ID: <20000518091329.J30740@brit.luminas.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: ; from mengelhart@earthtrip.com on Wed, May 17, 2000 at 06:22:34PM -0500 Organisation: Luminas Ltd. Sender: Paul Russell X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Mike, On Wed, May 17, 2000 at 06:22:34PM -0500, Mike Engelhart wrote: > I tried putting the entity's characters directly into the > PropertyResourceBundle but that just comes out as "?" in my HTML. Did you try my other suggestion of decoding the character entities after you read them in? Basically, you'd just need to write some code that searched through the incoming data and looked for anything beginning with an ampersand. When it finds one, it should look up the name of an entity in a hash to find the unicode character number for it. I used a simple perl script to take the entity declarations from the w3c .ent files and build a properties file from them. You can then read these into a Properties oject and treat it like a hash. I'd suggest you implement this as a class outside your XSP page and it in. -- Paul Russell Technical Director, http://www.luminas.co.uk Luminas Ltd.