I'm a bit biased there. Reading that they want to use CSL and the
discussion at http://tex.stackexchange.com/a/69284/9075, I question,
whether that makes sencse.
On the one hand, we should also point him to JabRef's BibTeX-VM, which is
capable to interpret all kinds of BibTeX style files. OK, possibly, BibTeX
will be replaced by BibLaTeX, where we don't have a VM. But do we really
need citeproc-js / CSL?
On the other hand, maybe CSL is the future and we should integrate CSL
support in JabRef?
(For the entry previewing)
On the one hand,we have other more urgent things to do. For instance, XMP
support. More work on supporting collaborative working. Better BibLaTeX
support, ... On the other hand, I agree that we do not receive that many
donations to get ourselves motivated to do something huge, so let's reroute
donations until the other project is finished...
Cheers,
Oliver
> [...]
http://www.docear.org/2013/08/14/who-wants-to-develop-docear4libreoffice-or-docear4openoffice/
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Jabref-devel mailing list
Jabref-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jabref-devel