Return-Path: <mengelhart@earthtrip.com>
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 18722 invoked from network); 17 May 2000 21:32:14 -0000
Received: from mta4.rcsntx.swbell.net (151.164.30.28)
  by locus.apache.org with SMTP; 17 May 2000 21:32:14 -0000
Received: from [209.184.1.49] by mta4.rcsntx.swbell.net
 (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with ESMTP id <0FUQ00FEL3K9GT@mta4.rcsntx.swbell.net> for
 cocoon-users@xml.apache.org; Wed, 17 May 2000 16:26:34 -0500 (CDT)
Date: Wed, 17 May 2000 16:26:37 -0500
From: Mike Engelhart <mengelhart@earthtrip.com>
Subject: Re: external entities
In-reply-to: <20000517214409.F30740@brit.luminas.co.uk>
To: cocoon-users@xml.apache.org
Message-id: <B54878BD.9A3D%mengelhart@earthtrip.com>
MIME-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

on 5/17/00 3:44 PM, Paul Russell at paul@luminas.co.uk wrote:

> Do you want the bad news, or the bad news?
> 
> You need to declare them as entities in your XML DTD, eg:
> 
> <?xml version="1.0" standalone="yes"?>
> <!DOCTYPE rootelement [
> <!ENTITY auml "&#228;">
> ]>
> 
> Then when you do &auml; in your document...
> 
> <rootelement>
> &auml;
> </rootelement>
> 
> ... it'll get parsed and end up as a unicode character for
> the rest of its journey through cocoon. *Hopefully*, at the
> other end, the serializer will convert it into an HTML entity.
> I'm pretty sure Cocoon1.x does this already, and I've just
> posted a patch to make Cocoon2 do it.

Cool -thanks.  the one thing that perplexes me is that if I use the entity
codes directly they get mangled.

for example:
&#228;
turns into
&amp;#228;

in my HTML output.  Is that the normal behavior??

Thanks,

Mike