XSLT: unparsed entities

To:	users@xxxxxxxxxx
Subject:	XSLT: unparsed entities
From:	<deshmol-lists@xxxxxxxxx>
Date:	Mon, 1 May 2006 07:28:26 -0700 (PDT)
Delivered-to:	mailing list users@cinjug.org
Domainkey-signature:	a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=i37bQSfbJB75VmM9uuzyGdzj2vuHW6J86kShi2zNkD7+x0qPXhncHwoug1GzlTgBWc9yHA5mArnJDs9FilGpQwWulyDkyz7vQSXCenf0nzVi08sAeCKBQL2aVb2XkTgwNWfXDdtKpaScmk2mnRDqRQEs+p88K1QiXDBGJqpMSvI= ;
Mailing-list:	contact users-help@cinjug.org; run by ezmlm
Reply-to:	deshmol-lists@xxxxxxxxx

Is there a way to indicate to an XSL
rocessor/XMLFilter 
to leave entities like &#1588; unparsed?

Currently I an XML file containing several such entity

references which when transformed (using a XMLFilter 
chain) to HTML seem to be converting the entities like

&#1588; to their multibyte value rather than retain
the 
entity reference as is in the transformed XML. This 
causes problems when viewing the html since apparently

browsers don't seem to understand multibyte
characters. 
(I even tried setting EntityResolvers on XMLFilters at

every stage, but resolveEntity is never invoked 
for &#1588;-like entities)

(FYI, I am using the SAXON implementation for my 
XMLFilters.)

Thanks,
~ amol

~ They have even applied logic to probability and vice versa. ~

<Prev in Thread]	Current Thread	[Next in Thread>
XSLT: unparsed entities, deshmol-lists <= Re: [cinjug-users] XSLT: unparsed entities, Eric Bardes

Previous by Date:	:SPAM: Pre-approved Application #wmhnkL53238228, Lou Wilkinson
Next by Date:	Ratess approved, Lynette Culver
Previous by Thread:	:SPAM: Pre-approved Application #wmhnkL53238228, Lou Wilkinson
Next by Thread:	Re: [cinjug-users] XSLT: unparsed entities, Eric Bardes
Indexes:	[Date] [Thread] [Top] [All Lists]