Citation management for HTML editors or web authoring applications?
Hello,
I have been using Zotero MS Word plug-in to manage my inline citations and references. However most writing I do nowadays are for posting online and it is often easier to directly write in an HTML editor or web authoring application, this way I don't have to deal with all the junk generated by the Word-HTML conversion. But as I am aware of, the most time saving utility offered by Zotero--the automatic refreshing, citation style changing, and re-ordering of citation numbers (e.g. in IEEE style) is only available in the MS Word plug-ins. Is there a similar utility for HTML editor or web authoring application? If not I really wish there were...
I have been using Zotero MS Word plug-in to manage my inline citations and references. However most writing I do nowadays are for posting online and it is often easier to directly write in an HTML editor or web authoring application, this way I don't have to deal with all the junk generated by the Word-HTML conversion. But as I am aware of, the most time saving utility offered by Zotero--the automatic refreshing, citation style changing, and re-ordering of citation numbers (e.g. in IEEE style) is only available in the MS Word plug-ins. Is there a similar utility for HTML editor or web authoring application? If not I really wish there were...
http://johnmacfarlane.net/pandoc/
markdown is designed to convert to super clean html.
I doubt anything particular for html is going to happen, but the pandoc solution is quite elegant.
We could suggest a patch to pandoc that would assume common key formats if they were missing from the bibliography file (at least with the first author last name/last two digits of publication year that is used in examples). That seems like it'd make pandoc more useful, though may require too much effort for disambiguating references.
A script that adds keys to RIS/MODS seems like low hanging fruit, though.
Bruce: remind me again why you use RIS in your workflow?
Dan - any thought on whether we can get this into the next version after the Nov. 20 release?
why not just build it into a separate MODS export translator? We probably shouldn't ship that with Zotero, but from a user experience, just having to save a .js to the translator folder once seems ideal.