With the upcoming release in mind, a quick plug for the issue in this mail-thread (see below for a quick summary). Would anyone be able to look into this issue, and come up with a fix?
I'm really not familiar with the codebase myself, and with how XML schema validation works in general, so I'm afraid I can't come up with a patch myself. All I can do is report the issue as clearly as possible, and ask :-). See https://bugzilla.gnome.org/show_bug.cgi?id=670865 in Bugzilla. Quick summary of the email conversation: On Fri, Feb 24, 2012 at 2:14 PM, Johan Corveleyn <jcor...@gmail.com> wrote: ... > I'm running into a "non-determinist" error with a schema even though I > don't think it's non-determinist (and both XSV and Xerces agree with > me; they too have no problem with the schema). I have reduced my > test-case to a simple example, see below. On Fri, Feb 24, 2012 at 2:58 PM, Pete Cordell <petexml...@codalogic.com> wrote: >> FWIW, the schema looks OK to me and neither Visual Studio or the W3C's XSV >> seem to report an error, so it does look like a libxml2 bug. On Tue, Feb 28, 2012 at 6:00 AM, Daniel Veillard <veill...@redhat.com> wrote: ... > Well in that case it seems the underlying code is generating a > wrong automata so it should be a matter of running that minimal > test case under gdb with the breakpoint appropriately set to find out > what wrong transition got added ... > > BTW thanks for making a minimalist case it is clearly a bug ! Thanks, -- Johan _______________________________________________ xml mailing list, project page http://xmlsoft.org/ xml@gnome.org http://mail.gnome.org/mailman/listinfo/xml