Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Parsing of an entity if it appears as an attribute value.

From: vineeth.narayanan@-----.--- (-------)
To: NULL
Date: 11/2/2004 9:30:00 PM
richard@c... (Richard Tobin) wrote in message news:<cm7r31$123f$1@p...>...
> In article <c47eb923.0411012225.2daa6709@p...>,
> Vineeth <vineeth.narayanan@g...> wrote:
> 
> >My application does not need a DTD for execution as
> >it is not supposed to perform any validation.
> 
> But then you say:
> 
> >The problem that
> >I am facing is with respect to any entity other than the 5 builtin
> >ones.
> 
> So you *do* need a DTD.  DTD's aren't just for validation.  If you want to
> use non-built-in entities, you need a DTD.  Even if you managed to hack
> around it, you would not be using XML, but a proprietary variant.
> 
> Why not use a DTD?
> 
> -- Richard


Hi Richard,

The problem with DTD is that my application does not have access to
the DTD. The basic functionality of my application is to convert the
XML document into a text based format document. I have written an
entityResolver implementing the Lexicalhandler interface, this
Resolver is called if the entity occurs in the content but it does not
get called up if the entity occur as an attribute value.

I somehow need access to the NonNormalized value of the attribute.

Any suggestions are welcome.

--Vineeth


transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent