From: David M. <da...@an...> - 2004-05-17 11:44:29
|
It's a parsing error, not a semantic error - xml-stylesheet PI's don't work either. But you're right, it's not a good example. In any event, supporting Unicode without forcing the user to specify the encoding manually in the browser is a requirement for me. I don't know of any mechanism for doing that except the XML pseudo-PI, so I sure hope eXist will provide *some* way to insert it in the output stream. - dam On 2004-May-17, at 07:02, Jakob Fix wrote: > David Mundie <dam5 <at> anthus.com> writes: > [...] >> constructors to work. For example, these two queries fail with parse >> errors, whether in a .xql file or submitted through the Basic Xquery >> Interface: >> >> <?xml version="1.0" encoding="UTF-8"?> >> <doc> >> This is a test >> </doc> > > technically, the xml declaration looks like a PI, but is not. > therefore, I > guess, this is not a good example for PI constructors not working. > > cheers, > Jakob. > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > Exist-open mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-open > |