# CSL editor update

**URL:** <https://discourse.citationstyles.org/t/csl-editor-update/1122>\
**Category:** CSL Development\
**Created:** [September 5, 2012, 3:09pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122 "2012-09-05T15:09:42Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Steve\_Ridout1](https://avatars.discourse-cdn.com/v4/letter/s/258eb7/32.png) [@Steve\_Ridout1](https://discourse.citationstyles.org/u/Steve_Ridout1)\
**Post date:** [September 5, 2012, 3:09pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/1 "2012-09-05T15:09:42Z")

</div>

Hello,

The CSL editor project is getting very close to finishing now. As such, the  
current features won’t change much now within this specific  
Mendeley/Columbia project. You can try it here:  
[http://steveridout.com/csl/about/](http://steveridout.com/csl/about/)

I’m pretty happy with how it’s gone, people are using it to create actual  
styles and I think it’s a lot more inviting to newcomers than editing XML.  
At the same time there are a lot of ideas which couldn’t be done due to  
lack of time. Some of these are ‘risky’ ideas where it’s hard to know how  
well they’ll work before building some prototypes. e.g. a wizard to build  
an initial style template, and a searchable database of all the macros in  
the repo to use as building blocks. Before wrapping up I’ll write up a  
summary future work suggestions.

# Integrating with reference managers

Mendeley have started work on integrating the editor to make the workflow  
nicer for their users. I’d like to invite other devs to take a look at the  
documentation I’ve started putting on github:

> **[citation-style-language/csl-editor](https://github.com/citation-style-language/csl-editor/wiki)**
>
> cslEditorLib - A HTML 5 library for searching and editing CSL styles - citation-style-language/csl-editor

This is still WIP, and before finishing I will add more documentation to  
the source code too. Please don’t hesitate to contact me if you want help  
understanding, or if you think anything should be changed.

# Future Maintenence

Currently the code is split into two repositories on github:

[https://github.com/citation-style-editor/csl-editor](https://github.com/citation-style-editor/csl-editor) - this is the core  
cslEditorLib library, with no code specific to one reference manager  
[https://github.com/citation-style-editor/csl-editor-demo-site](https://github.com/citation-style-editor/csl-editor-demo-site) - this is my  
reference implementation, which different implementors can fork and add  
their own customizations to integrate with their reference managers if they  
wish. It contains cslEditorLib as a git submodule.

Splitting it like this means everyone can benefit from improvements to the  
core cslEditorLib repository.

# My situation

I’ve got about 70 hours of contracted work left on this, which I’ll stretch  
out over the next three weeks. After that I’ll continue to do a bit in my  
free time to help maintain it, and will keep my hosted version of the site  
up for as long as it’s useful and not too much of a burden, or until it  
gets superseded by another ref-manager agnostic version.

Steve

---

<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:** [September 5, 2012, 3:58pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/2 "2012-09-05T15:58:49Z")

</div>

Thanks for the update, and the work, Steve.

In the realm of “stuff everyone needs to think about and work on” (not a  
critique of your work per se), I still think this is an example that needs  
to be MUCH simpler. One-click installs please. Hopefully we’ll see some  
rigorous forking of your repo!

[image: Inline image 1]

> Hello,
> 
> The CSL editor project is getting very close to finishing now. As such,  
> the  
> current features won’t change much now within this specific  
> Mendeley/Columbia project. You can try it here:  
> [http://steveridout.com/csl/about/](http://steveridout.com/csl/about/)
> 
> I’m pretty happy with how it’s gone, people are using it to create actual  
> styles and I think it’s a lot more inviting to newcomers than editing XML.  
> At the same time there are a lot of ideas which couldn’t be done due to  
> lack  
> of time. Some of these are ‘risky’ ideas where it’s hard to know how well  
> they’ll work before building some prototypes. e.g. a wizard to build an  
> initial style template, and a searchable database of all the macros in the  
> repo to use as building blocks. Before wrapping up I’ll write up a summary  
> future work suggestions.
> 
> # Integrating with reference managers
> 
> Mendeley have started work on integrating the editor to make the workflow  
> nicer for their users. I’d like to invite other devs to take a look at the  
> documentation I’ve started putting on github:
> 
> [Home · citation-style-language/csl-editor Wiki · GitHub](https://github.com/citation-style-editor/csl-editor/wiki)
> 
> This is still WIP, and before finishing I will add more documentation to  
> the  
> source code too. Please don’t hesitate to contact me if you want help  
> understanding, or if you think anything should be changed.
> 
> # Future Maintenence
> 
> Currently the code is split into two repositories on github:
> 
> [GitHub - citation-style-language/csl-editor: cslEditorLib - A HTML 5 library for searching and editing CSL styles](https://github.com/citation-style-editor/csl-editor) - this is the core  
> cslEditorLib library, with no code specific to one reference manager  
> [GitHub - citation-style-language/csl-editor-demo-site: Reference implementation of the CSL editor](https://github.com/citation-style-editor/csl-editor-demo-site) - this is my  
> reference implementation, which different implementors can fork and add  
> their own customizations to integrate with their reference managers if  
> they  
> wish. It contains cslEditorLib as a git submodule.
> 
> Splitting it like this means everyone can benefit from improvements to the  
> core cslEditorLib repository.
> 
> # My situation
> 
> I’ve got about 70 hours of contracted work left on this, which I’ll  
> stretch  
> out over the next three weeks. After that I’ll continue to do a bit in my  
> free time to help maintain it, and will keep my hosted version of the site  
> up for as long as it’s useful and not too much of a burden, or until it  
> getsOn Wed, Sep 5, 2012 at 11:09 AM, Steve Ridout \<@Steve\_Ridout1\> wrote:  
> superseded by another ref-manager agnostic version.
> 
> Steve

* * *

 ![](https://canada1.discourse-cdn.com/flex029/uploads/citationstyles/original/1X/04998d178bb922958f2df41e56077e4e29c91072.png)

---

<div class="post-metadata">

**Author:** ![Carles\_Pina](https://avatars.discourse-cdn.com/v4/letter/c/dbc845/32.png) [@Carles\_Pina](https://discourse.citationstyles.org/u/Carles_Pina)\
**Post date:** [September 6, 2012, 11:59am UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/3 "2012-09-06T11:59:58Z")

</div>

Hello,

> Thanks for the update, and the work, Steve.
> 
> In the realm of “stuff everyone needs to think about and work on” (not a critique of your work per se), I still think this is an example that needs to be MUCH simpler.  
> One-click installs please. Hopefully we’ll see some rigorous forking of your repo!

This is a task for the reference managers. The csl-editor project  
offers enough flexibility so $referenceManager can integrate nicely  
(see [Visual Editor · citation-style-language/csl-editor Wiki · GitHub](https://github.com/citation-style-editor/csl-editor/wiki/Visual-Editor)  
, more and better documentation about how to integrate csl-editor with  
$referenceManager to be written soon). We have a prototype here with  
one click installs (when this will be public I’ll send a note here).

Steve did a demoSite with the instructions that you have seen and as a  
example of how to use the cslEditor.

Regards,

---

<div class="post-metadata">

**Author:** ![Charles\_Parnot](https://avatars.discourse-cdn.com/v4/letter/c/57b2e6/32.png) [@Charles\_Parnot](https://discourse.citationstyles.org/u/Charles_Parnot)\
**Post date:** [September 6, 2012, 12:10pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/4 "2012-09-06T12:10:11Z")

</div>

I agree it makes more sense for the clients to do their own integration as they wish. It’s quite a burden to place on the CSL editor developers, particularly if no easy integration is done on the client side, and particularly as the editor itself runs in the browser. So maybe instead Steve can let the clients know what’s the best option for the editor to offer, e.g. a simple URL scheme? In the case of Papers, we have a number of avenues we can take advantage of, like responding to a scheme like papers2://csl/file/path/to/csl/file, or papers2://csl/url/path/to/csl/url.

charles

---

<div class="post-metadata">

**Author:** ![Robert\_Knight](https://avatars.discourse-cdn.com/v4/letter/r/ba9def/32.png) [@Robert\_Knight](https://discourse.citationstyles.org/u/Robert_Knight)\
**Post date:** [September 6, 2012, 12:47pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/5 "2012-09-06T12:47:07Z")

</div>

> In the case of Papers, we have a number of avenues we can take advantage of,  
> like responding to a scheme like papers2://csl/file/path/to/csl/file, or papers2://csl/url/path/to/csl/url.

That is what we’re doing, using a mendeley:// URL. We also have a  
facility to import styles into the app by pasting a style link (the  
style URI) into a box.

Regards,  
Rob.

---

<div class="post-metadata">

**Author:** ![Steve\_Ridout1](https://avatars.discourse-cdn.com/v4/letter/s/258eb7/32.png) [@Steve\_Ridout1](https://discourse.citationstyles.org/u/Steve_Ridout1)\
**Post date:** [September 13, 2012, 4:51pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/6 "2012-09-13T16:51:18Z")

</div>

> I agree it makes more sense for the clients to do their own integration as  
> they wish. It’s quite a burden to place on the CSL editor developers,  
> particularly if no easy integration is done on the client side, and  
> particularly as the editor itself runs in the browser. So maybe instead  
> Steve can let the clients know what’s the best option for the editor to  
> offer, e.g. a simple URL scheme? In the case of Papers, we have a number of  
> avenues we can take advantage of, like responding to a scheme like  
> papers2://csl/file/path/to/csl/file, or papers2://csl/url/path/to/csl/url.
> 
> charles

Sorry for the delay responding.

I doubt the papers2://csl/file/… scheme will be useful in this case since  
saving to the hard drive from a browser is tricky. I used a flash based  
plugin called downloadify which requires the user to specify the  
destination file path. Saving via pure javascript possible in Chrome but  
only to a sandboxed file system (  
[Read files in JavaScript &nbsp;|&nbsp; Articles &nbsp;|&nbsp; web.dev](http://www.html5rocks.com/en/tutorials/file/filesystem/)) - if you could get  
the actual file path this would be OK, but I don’t think you can.

To use a papers2://csl/url/… request you’ll want to add some code to store  
the style on your server first. I’ve kept the demo  
site[https://github.com/citation-style-editor/csl-editor-demo-site](https://github.com/citation-style-editor/csl-editor-demo-site)  
server  
pretty much stateless to keep things simple so I’m afraid I can’t much help  
with this. I’m leaving it to the ref manager devs to override the load and  
save functions to get styles in and out of the editor which you should be  
able to do by following the documentation here:  
[Home · citation-style-language/csl-editor Wiki · GitHub](https://github.com/citation-style-editor/csl-editor/wiki). If there’s  
anything in the core  
library[https://github.com/citation-style-editor/csl-editor](https://github.com/citation-style-editor/csl-editor) that  
stops you doing what you want, or that you don’t understand, please let me  
know.

Another option is passing the whole style in a data URI, e.g.  
papers2://csl/url/$CSL\_DATA\_URI . It would be easy to add links like this  
to the demo site for all the ref managers actually. If something like this  
would work, let me know and I’ll add it.

(Note: In Firefox I tried installing a style to Zotero using  
data:text/x-csl;base64,$ENCODED\_CSL but it only worked for trivially small  
styles. The confirm dialog goes pure black for real styles,  
perhaps because it’s trying to display the whole URL.)

Steve

---

<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:** [September 13, 2012, 5:01pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/7 "2012-09-13T17:01:34Z")

</div>

What about doing as zotero does: serving the file with a special mime (?)  
type?

---

<div class="post-metadata">

**Author:** ![Robert\_Knight](https://avatars.discourse-cdn.com/v4/letter/r/ba9def/32.png) [@Robert\_Knight](https://discourse.citationstyles.org/u/Robert_Knight)\
**Post date:** [September 13, 2012, 5:12pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/8 "2012-09-13T17:12:08Z")

</div>

> I doubt the papers2://csl/file/… scheme will be useful in this case since saving to the hard drive from a browser is tricky.  
> I used a flash based plugin called downloadify which requires the user to specify the destination file path.

In Mendeley we only support mendeley:// links that include a URL for  
the style, where the URL is usually the style ID.  
This is useful since the app can then fetch updates for the style  
using only the information in the style itself.

An important caveat with custom URL scheme handlers not implemented by  
browser extensions is that  
the UX varies across browsers. Google Chrome has a pretty scary  
dialog in particular.

> What about doing as zotero does: serving the file with a special mime (?) type?

You mean serving the style as an ordinary file download and  
registering the app as a handler for the CSL mime type or .csl  
extension?  
I think that would be a more dependable approach.

Regards,  
Rob.

---

<div class="post-metadata">

**Author:** ![Steve\_Ridout1](https://avatars.discourse-cdn.com/v4/letter/s/258eb7/32.png) [@Steve\_Ridout1](https://discourse.citationstyles.org/u/Steve_Ridout1)\
**Post date:** [September 13, 2012, 5:18pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/9 "2012-09-13T17:18:58Z")

</div>

I’ve tried this for Zotero using a data URI with the “text/x-csl” mime type  
and it works but only for trivially small styles apparently due to a bug in  
the confirm dialog.

(I was trying a data URI since I don’t want to write styles to my server,  
but any of the ref managers can host their own version of the editor and  
make it store styles if they want, like Mendeley is doing. I’m just  
considering this to improve the demo site in the meantime)

---

<div class="post-metadata">

**Author:** ![Dan\_Stillman](https://avatars.discourse-cdn.com/v4/letter/d/ecb155/32.png) [@Dan\_Stillman](https://discourse.citationstyles.org/u/Dan_Stillman)\
**Post date:** [September 13, 2012, 5:37pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/10 "2012-09-13T17:37:58Z")

</div>

We’ll fix this—thanks. (I’d guess that it would work if you hit Return,  
though. It does for me in Firefox.)

---

<div class="post-metadata">

**Author:** ![Dan\_Stillman](https://avatars.discourse-cdn.com/v4/letter/d/ecb155/32.png) [@Dan\_Stillman](https://discourse.citationstyles.org/u/Dan_Stillman)\
**Post date:** [September 13, 2012, 5:26pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/11 "2012-09-13T17:26:55Z")

</div>

Then it’s just up to the browser. The reason Zotero can intercept such  
files is because it’s a browser extension. Some browsers allow  
associating external programs based on content type—optionally without  
confirmation—but that will work only once the user sets it up the first  
time. Other browsers don’t support that: Safari, as far as I know,  
doesn’t have external helper app functionality, just a "‘safe’ files"  
list embedded in a plist somewhere. If the ref manager is registered  
with the system for the content type or file extension, browsers that do  
support external helper app functionality might offer it as the default  
choice.

While we’re on the subject, though, we should agree on a different  
content type for .csl files. Among other things, Safari (and possibly  
other browsers) will display "text/_" types rather than downloading  
them._ “x-” is also considered bad practice these days.  
application/vnd.citationstyles.style? Zotero is using  
application/vnd.citationstyles.csl+json for CSL JSON data.

- Downloading isn’t as nice as auto-import or external helper app  
functionality, but it’s better than displaying in the browser. At least  
users can then double-click the downloaded file to open it in a properly  
registered reference manager.

---

<div class="post-metadata">

**Author:** ![Charles\_Parnot](https://avatars.discourse-cdn.com/v4/letter/c/57b2e6/32.png) [@Charles\_Parnot](https://discourse.citationstyles.org/u/Charles_Parnot)\
**Post date:** [September 13, 2012, 6:08pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/12 "2012-09-13T18:08:12Z")

</div>

Thanks for all the info, Steve.

I see now that indeed, a URL scheme won’t help much. In any case, could I ask you one last favor, then, in the current version? We have changed things so that one can simply save a ‘.csl’ file and then drag it into Papers. Could you thus change the text to:

Use the above button to save your .csl file to the ‘Styles’ subfolder within your Papers2 library folder. [More info.](http://support.mekentosj.com/kb/pro-tips/pro-tip-adding-additional-citation-styles)

Note that I have also included a better URL for the link.

Thanks again very much for the hard word, the CSL editor has turned into a very useful tool.

Best wishes,

Charles

---

<div class="post-metadata">

**Author:** ![Dan\_Stillman](https://avatars.discourse-cdn.com/v4/letter/d/ecb155/32.png) [@Dan\_Stillman](https://discourse.citationstyles.org/u/Dan_Stillman)\
**Post date:** [September 13, 2012, 6:10pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/13 "2012-09-13T18:10:53Z")

</div>

> While we’re on the subject, though, we should agree on a different  
> content type for .csl files. Among other things, Safari (and possibly  
> other browsers) will display "text/_" types rather than downloading  
> them._ “x-” is also considered bad practice these days.  
> application/vnd.citationstyles.style? Zotero is using  
> application/vnd.citationstyles.csl+json for CSL JSON data.

It could also be application/vnd.citationstyles.style+xml, since RFC3023  
recommends the use of “+xml” for XML-based media types. I don’t think  
there’s much to be gained from that, but there’s also no particular  
reason not to do it.

From [http://www.ietf.org/rfc/rfc3023.txt:](http://www.ietf.org/rfc/rfc3023.txt:)

> A.15 Why must I use the ‘+xml’ suffix for my new XML-based media type?
> 
> ```
> You don't have to, but unless you have a good reason to explicitly
> disallow generic XML processing, you should use the suffix so as not
> to curtail the options of future users and developers.
> 
> Whether the inventors of a media type, today, design it for dispatch
> to generic XML processing machinery (and most won't) is not the
> critical issue. The core notion is that the knowledge that some
> media type happens to use XML syntax opens the door to unanticipated
> kinds of processing beyond those envisioned by its inventors, and on
> this basis identifying such encoding is a good and useful thing.
> 
> Developers of new media types are often tightly focused on a
> particular type of processing that meets current needs. But there is
> no need to rule out generic processing as well, which could make your
> media type more valuable over time. It is believed that registering
> with the '+xml' suffix will cause no interoperability problems
> whatsoever, while it may enable significant new functionality and
> interoperability now and in the future. So, the conservative
> approach is to include the '+xml' suffix.
> 
> ```

I don’t have a strong preference here.

---

<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:** [September 13, 2012, 6:15pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/14 "2012-09-13T18:15:22Z")

</div>

> While we’re on the subject, though, we should agree on a different  
> content type for .csl files. Among other things, Safari (and possibly  
> other browsers) will display "text/_" types rather than downloading  
> them._ “x-” is also considered bad practice these days.  
> application/vnd.citationstyles.style? Zotero is using  
> application/vnd.citationstyles.csl+json for CSL JSON data.
> 
> It could also be application/vnd.citationstyles.style+xml,

I say we go with this.

Bruce

---

<div class="post-metadata">

**Author:** ![Charles\_Parnot](https://avatars.discourse-cdn.com/v4/letter/c/57b2e6/32.png) [@Charles\_Parnot](https://discourse.citationstyles.org/u/Charles_Parnot)\
**Post date:** [September 13, 2012, 6:19pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/15 "2012-09-13T18:19:51Z")

</div>

Nice. It’s too bad we can’t get github to serve specific mime types for raw files:

> <https://stackoverflow.com/questions/3537575/can-git-store-the-mime-type-of-a-file-like-svn-does-for-browsing-html>

charles

---

<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:** [September 13, 2012, 6:30pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/16 "2012-09-13T18:30:58Z")

</div>

Does that really present any practical problems here though? We use  
the csl. extension for the style files, which servers can use to  
associate the correct mimetype with.

---

<div class="post-metadata">

**Author:** ![Charles\_Parnot](https://avatars.discourse-cdn.com/v4/letter/c/57b2e6/32.png) [@Charles\_Parnot](https://discourse.citationstyles.org/u/Charles_Parnot)\
**Post date:** [September 13, 2012, 6:43pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/17 "2012-09-13T18:43:27Z")

</div>

Ah, yes, that was a bit mysterious, sorry. I meant it would be because it would hopefully prevent Safari from adding a ‘.txt’ extension when saving the file (and maybe would even directly download it instead of displaying it). It makes it a bit easier for adventurous users that find a style on the repository.

Charles

---

<div class="post-metadata">

**Author:** ![Steve\_Ridout1](https://avatars.discourse-cdn.com/v4/letter/s/258eb7/32.png) [@Steve\_Ridout1](https://discourse.citationstyles.org/u/Steve_Ridout1)\
**Post date:** [September 13, 2012, 8:08pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/18 "2012-09-13T20:08:58Z")

</div>

> Thanks for all the info, Steve.
> 
> I see now that indeed, a URL scheme won’t help much. In any case, could I  
> ask you one last favor, then, in the current version? We have changed  
> things so that one can simply save a ‘.csl’ file and then drag it into  
> Papers. Could you thus change the text to:
> 
> Use the above button to save your .csl file to the ‘Styles’ subfolder  
> within your Papers2 library folder. [More  
> info.](http://support.mekentosj.com/kb/pro-tips/pro-tip-adding-additional-citation-styles)
> 
> Note that I have also included a better URL for the link.

Thanks, I’ve altered it, it’ll go into the next release.

---

<div class="post-metadata">

**Author:** ![Steve\_Ridout1](https://avatars.discourse-cdn.com/v4/letter/s/258eb7/32.png) [@Steve\_Ridout1](https://discourse.citationstyles.org/u/Steve_Ridout1)\
**Post date:** [September 13, 2013, 12:58pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/19 "2013-09-13T12:58:45Z")

</div>

I’ve just updated some of the CSL editor dependencies to their latest  
versions:

- locales
- styles
- citeproc-js

There a few other minor changes too and the updated version is live at  
[http://editor.citationstyles.org](http://editor.citationstyles.org). Please keep an eye out for any unintended  
breakages and let me know via github issues.

Steve

PS: I’m still hoping that someone else will take over responsibility for  
future maintenance and development of the editor. I’m no longer in  
academia, and no longer create reference manager software, so it would be  
great to see it evolve in the hands of someone more suitable. I’m very  
willing to help out if anyone needs help finding their way around the code,  
assuming I can still remember how it works!

---

<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:** [September 13, 2013, 1:03pm UTC](https://discourse.citationstyles.org/t/csl-editor-update/1122/20 "2013-09-13T13:03:41Z")

</div>

Thanks Steve!

Anyone here willing to take over the editor project? If not, any  
thoughts on how to find someone?

[Next page](https://discourse.citationstyles.org/t/csl-editor-update/1122.md?page=2)