Steve Terpe
Steve Terpe
This should compile correctly with emscripten SDK 1.29.0 see #4.
If you can put together a small repo that reproduces the issue I will look into this further.
@rajashekhargundeti This seems to be similar to #11. Unfortunately, I don't think anyone has a solution for this yet. It looks like what you are trying to do is use...
It seems like certain types of `.xml` & .`xsd` can have problems because they specify pathing relative to each other but that pathing does not correspond to the virtualFS filesystem...
http://syssgx.github.io/xml.js/js/xmllint.js was compiled with an earlier version of `emscripten` perhaps there have been internal changes.
Does polotek/libxmljs work?
I'm a bit unclear. Your changes break using xmllint within node.js completely. I'm also unclear why this API proposal offers over the previous options object? Edit: Okay I get what...
To be clear: I'm totally for the capability this provides, but xmllint should still work in node & the solution should extend the existing api in a fully backwards compatible...
I will look into supporting this capability as well. Sent from my iPhone > On Apr 20, 2015, at 6:13 AM, Alf Eaton [email protected] wrote: > > Basiclaly I'm just...
I think that @hubgit was trying to solve the schema that imports other schemas in the browser. I was reluctant to pull in those changes because they break the library...