…
- Is it OK to have so many differing implementations of citeproc?
More of a philosophical question, but my initial reaction to needing a Ruby
CSL processor was to find the most compatible one and try to use it from
Ruby.
Going back to this, I may have mentioned this before, but might be
worth creating Java and C-based libraries or executables that embed
rhino and tracemonkey* respectively?
This seems to suggest doing so is trivial.
http://www.mozilla.org/rhino/tutorial.html
Bruce
- since the current code relies on E4X, other engines (like, say, V8, are out).
…
- Is it OK to have so many differing implementations of citeproc?
More of a philosophical question, but my initial reaction to needing a Ruby
CSL processor was to find the most compatible one and try to use it from
Ruby.
Going back to this, I may have mentioned this before, but might be
worth creating Java and C-based libraries or executables that embed
rhino and tracemonkey* respectively?
This seems to suggest doing so is trivial.
http://www.mozilla.org/rhino/tutorial.html
Bruce
- since the current code relies on E4X, other engines (like, say, V8, are out).
As noted in another thread, citeproc-js now runs in Google Chrome (V8)
and IE6 and above; basically anything that supports the DOM and
roughly adheres to ECMA standards should work.
Frank