robert burrell donkin wrote:
On Friday, September 26, 2003, at 04:08 AM, Craig R. McClanahan wrote:
robert burrell donkin wrote:
On Thursday, September 25, 2003, at 09:36 PM, Craig R. McClanahan
wrote:
robert burrell donkin wrote:
hi janek
i don't see any reason why we shouldn't put
On Mon, 2003-09-29 at 13:20, Matthijs Wensveen wrote:
http://www.w3.org/TR/REC-xml#sec-pi says:
PIs are not part of the document's character data
http://www.w3.org/TR/REC-xml#dt-chardata, but must be passed through
to the application.
To me this means that you shouldn't catch PI's but send
On Wed, 2003-09-24 at 15:25, Norbert Pabi wrote:
Udao Ci si znale regue na processing instruction?
--
Norbert Pabi
AFAIK there is no rule set for using PIs when building the data. If you
are happy to obtain the PIs after the parse you could adapt this class
which collects PIs into a
robert burrell donkin wrote:
hi janek
i don't see any reason why we shouldn't put something to allow access
to processing instructions into digester. this probably means storing
the indexed processing instruction (just as your example code does).
probably worth giving a getting for the keys
On Thursday, September 25, 2003, at 09:36 PM, Craig R. McClanahan wrote:
robert burrell donkin wrote:
hi janek
i don't see any reason why we shouldn't put something to allow access to
processing instructions into digester. this probably means storing the
indexed processing instruction (just
robert burrell donkin wrote:
On Thursday, September 25, 2003, at 09:36 PM, Craig R. McClanahan wrote:
robert burrell donkin wrote:
hi janek
i don't see any reason why we shouldn't put something to allow
access to processing instructions into digester. this probably means
storing the indexed
