The idea was to use it for the cite processor test suite to simultaneously test citeproc-js, citeproc-hs and citeproc-ruby, i.e. I would mostly use very short styles but caching is more or less out of the question. My results with SpiderMonkey are very encouraging so I will probably stick with it.
Many thanks, Sylvester On Aug 15, 2011, at 6:22 PM, Simon Kornblith wrote: > If you're planning to parse a style and then use it many times, jsdom would > work. It's what we use in citeproc-node > (https://www.zotero.org/svn/citeproc-node/trunk/). However, jsdom is > glacially slow, at least with larger documents. If you can't cache and reuse > styles, it's possible that SpiderMonkey would be faster than V8+jsdom. > > Simon > > On Aug 15, 2011, at 12:11 PM, Sylvester Keil wrote: > >> To return briefly to the issue of executing citeproc-js using embedded >> JavaScript engines. In the meantime I am able to use citeproc-js embedded >> into Ruby using either Rhino (for JRuby) or SpiderMonkey (for Ruby 1.8.7); >> because the V8 is so fast it would be great to use that to run citeproc-js, >> too; however, the engine itself comes without the DOM parsing functions >> (such as getElementsByTagName) – could anyone suggest a good DOM parsing >> solution for citeproc-js + V8? (Perhaps 'jsdom'?) >> >> Many thanks! >> >> Sylvester >> >> >> On Aug 2, 2011, at 9:51 AM, Frank Bennett wrote: >> >>> On Tue, Aug 2, 2011 at 6:25 AM, Sylvester Keil <[email protected]> wrote: >>>> Frank, >>>> >>>> bibtex-ruby does not implement any disambiguation support yet, so >>>> everything is fine by me. >>>> >>>> In unrelated news, I am currently working on a wrapper around citeproc-js >>>> for the csl-test environment (to make it possible to access different >>>> citeproc engines through a single API) but have run into several issues >>>> with different JavaScript interpreters (using xml4e for Rhino and >>>> SpiderMonkey and xmldom for everything else). Right now the wrapper is >>>> designed to work with any of the common interpreters (V8, Rhino, >>>> SpiderMonkey, node, JavaScriptCore, or the JScript) so I wanted to ask if >>>> you were aware of any major obstacles in getting citeproc-js to work in >>>> any of them? >>>> >>>> Many thanks >>>> Sylvester >>> >>> This sounds great. >>> >>> I had this note from Faolan Cheslack-Postava at Zotero, when he was >>> setting up the node.js server that now drives the repository previews: >>> >>> "Only problem so far with the changes to these are reference to the >>> global CSL object in addInstitutionNodes(). It causes problems with >>> environments like nodejs that use commonJS module systems that wrap >>> them in their own scope so they can't damage the global environment. >>> I've just added a CSL_INSTITUTION_KEYS inside my xml parsing module >>> for now. This is certainly not something you need to be concerned >>> about changing as it can always be passed into whatever xml parsing >>> adapter is being used, but I figured I'd let you know anyway." >>> >>> Apart from that, xmldom.js seems to work everywhere that DOM parsing >>> is available. I use xmle4x.js for testing, so that's known to work >>> where there is an E4X parser. >>> >>> Frank >>> >>> >>>> >>>> On Jul 31, 2011, at 4:36 AM, Frank Bennett wrote: >>>> >>>>> Andrea, Sylvester: >>>>> >>>>> Quite some time ago, Andrea raised an objection to the spec >>>>> description of disambiguation behavior, which I should have addressed, >>>>> but didn't: >>>>> >>>>> http://xbiblio-devel.2463403.n2.nabble.com/disambiguation-one-more-tt5131926.html#a5133985 >>>>> >>>>> Rintze has proposed a revision that clarifies the behavior: >>>>> >>>>> https://github.com/citation-style-language/documentation/pull/16 >>>>> >>>>> Reviewing the amendments, I was reminded of a flaw in citeproc-js, >>>>> which in some situations was failing to drop names that do not >>>>> contribute to disambiguation. The failure is reflected in some of the >>>>> fixtures in the test suite. I took another look at my code, and >>>>> managed to clean up the behavior. The effect can be seen in the >>>>> following changeset: >>>>> >>>>> https://bitbucket.org/bdarcus/citeproc-test/changeset/e4225e251798 >>>>> >>>>> The affected fixtures are linked below. Please take a look at them, >>>>> and let us know whether you approve of the new behavior. The effect on >>>>> the specification is outlined in comments to Rintze's github pull >>>>> request, linked above. >>>>> >>>>> https://bitbucket.org/bdarcus/citeproc-test/src/beda343d95bc/processor-tests/humans/disambiguate_AddNamesFailure.txt >>>>> https://bitbucket.org/bdarcus/citeproc-test/src/beda343d95bc/processor-tests/humans/disambiguate_AddNamesFailureWithAddGivenname.txt >>>>> https://bitbucket.org/bdarcus/citeproc-test/src/beda343d95bc/processor-tests/humans/disambiguate_AndreaEg1.txt >>>>> https://bitbucket.org/bdarcus/citeproc-test/src/beda343d95bc/processor-tests/humans/disambiguate_ByCiteRetainNamesOnFailureIfYearSuffixNotAvailable.txt >>>>> >>>>> Many thanks, >>>>> Frank >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Got Input? Slashdot Needs You. >>>>> Take our quick survey online. Come on, we don't ask for help often. >>>>> Plus, you'll get a chance to win $100 to spend on ThinkGeek. >>>>> http://p.sf.net/sfu/slashdot-survey >>>>> _______________________________________________ >>>>> xbiblio-devel mailing list >>>>> [email protected] >>>>> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA >>>> The must-attend event for mobile developers. Connect with experts. >>>> Get tools for creating Super Apps. See the latest technologies. >>>> Sessions, hands-on labs, demos & much more. Register early & save! >>>> http://p.sf.net/sfu/rim-blackberry-1 >>>> _______________________________________________ >>>> xbiblio-devel mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel >>>> >> >> >> ------------------------------------------------------------------------------ >> uberSVN's rich system and user administration capabilities and model >> configuration take the hassle out of deploying and managing Subversion and >> the tools developers use with it. Learn more about uberSVN and get a free >> download at: http://p.sf.net/sfu/wandisco-dev2dev >> _______________________________________________ >> xbiblio-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel >> > > > ------------------------------------------------------------------------------ > uberSVN's rich system and user administration capabilities and model > configuration take the hassle out of deploying and managing Subversion and > the tools developers use with it. Learn more about uberSVN and get a free > download at: http://p.sf.net/sfu/wandisco-dev2dev > _______________________________________________ > xbiblio-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
