[Vtd-xml-users] [Fwd: Re: 1.6 bug:]

[Mark S. <ma...@Sc...>]

Tatu Saloranta wrote:
> 
> Ok. It is likely it accepts all codes <= 0x0020 as
> white space -- that's usually pretty reasonable
> way to do it with string tokenization.

Excellent suggestion. Jimmy, would that be something you would consider
doing in the near future with vtd (as an option)?

<snip>
> One more thing -- xml 1.1 actually does allow these
> control characters (although not null byte) to be
> included, via character entities. It's too bad, then,
> that xml 1.1 has other problems that make it DOA,
> rarely used anywhere (you can google for various
> people's reasoning why xml 1.1 sucks -- I have my
> own pet peeves -- byt I did work on making Woodstox
> parser support xml 1.1 nonetheless).

Interesting.
(I use and recommend Woodstox (with XFire atm), btw)

> Of course, since you don't control the generation of
> input files this is bit of a moot point. ;-)

:-)

-- 
http://www.ScheduleWorld.com/tg/
Free Google Calendar synchronization with Outlook, Evolution,
cell phones, BlackBerry, PalmOS, Exchange, Mozilla, Thunderbird,
Pocket PC/Windows Mobile. Also sync tasks, notes and contacts!
WebDAV, vfreebusy, RSS, LDAP, iCalendar, iTIP, iMIP support.


-- 
http://www.ScheduleWorld.com/tg/
Free Google Calendar synchronization with Outlook, Evolution,
cell phones, BlackBerry, PalmOS, Exchange, Mozilla, Thunderbird,
Pocket PC/Windows Mobile. Also sync tasks, notes and contacts!
WebDAV, vfreebusy, RSS, LDAP, iCalendar, iTIP, iMIP support.