-----Original Message-----
From: Shankar Unni
> Try an entity instead of xinclude? Not many parsers are good for
> xinclude as yet (a mainly uninformed statement). Entity
resolution is
> easier if the parser is setup correctly.
Oh, that's what we are doing now, but entity resolution
doesn't have a concept of relative paths.
Does your parser support xml:base?
That makes relative paths work.
All in all, entity includes are inflexible and a terrific
pain to work with.
Its an alternative.
regards DaveP
--
DISCLAIMER:
NOTICE: The information contained in this email and any attachments is
confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of the
content of it or of any attachment; you are requested to notify the
sender immediately of your receipt of the email and then to delete it
and any attachments from your system.
RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants. However, it
cannot accept any responsibility for any such which are transmitted.
We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email and
any attachments are those of the author and do not necessarily represent
those of RNIB.
RNIB Registered Charity Number: 226227
Website: http://www.rnib.org.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
