# embedded citeproc-js (was Continuing development of citeproc-rb)

**URL:** <https://discourse.citationstyles.org/t/embedded-citeproc-js-was-continuing-development-of-citeproc-rb/735>\
**Category:** CSL Development\
**Created:** [August 17, 2009, 3:26pm UTC](https://discourse.citationstyles.org/t/embedded-citeproc-js-was-continuing-development-of-citeproc-rb/735 "2009-08-17T15:26:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [August 17, 2009, 3:26pm UTC](https://discourse.citationstyles.org/t/embedded-citeproc-js-was-continuing-development-of-citeproc-rb/735/1 "2009-08-17T15:26:36Z")

</div>

…

> 1. 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](http://www.mozilla.org/rhino/tutorial.html)

Bruce

- since the current code relies on E4X, other engines (like, say, V8, are out).

---

<div class="post-metadata">

**Author:** ![Frank\_Bennett](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.citationstyles.org/frank_bennett/32/198_2.png) [@Frank\_Bennett](https://discourse.citationstyles.org/u/Frank_Bennett)\
**Post date:** [April 18, 2010, 10:16pm UTC](https://discourse.citationstyles.org/t/embedded-citeproc-js-was-continuing-development-of-citeproc-rb/735/2 "2010-04-18T22:16:14Z")

</div>

> …
> 
> > 1. 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](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.

> **[gsl-nagoya-u.net - This website is for sale! - gsl nagoya...](http://ww16.gsl-nagoya-u.net/http/pub/citeproc-demo/demo.html?sub1=20231212-2330-08bb-8c3c-739c7a2a3f88)**
>
> This website is for sale! gsl-nagoya-u.net is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, gsl-nagoya-u.net has it all. We hope you find what you are...

Frank

---

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [April 19, 2010, 1:39pm UTC](https://discourse.citationstyles.org/t/embedded-citeproc-js-was-continuing-development-of-citeproc-rb/735/3 "2010-04-19T13:39:49Z")

</div>

…

> 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.

Awesome!

Bruce