ABIWORD support.
Abiword is a great, more readable (to me) word processor that also (to me) resembles word 2003. Please make a .dll plug-in for Abiword! Open Office is ok, but after some time the typeface of any font rendered by it gives me headaches. To top that off I am required to use 12 point Times New Roman (blah). I am a double major student, and have a lot of typing to do so I need my Abiword.
Their position is that
"the license of zotera is not well known and its compatibity with GPL hasn't been documented"
Is it true that there are issues concerning the compatibility between the Educational Community Licence and the GPL that could be an obstacle for an Abiword-plugin?
Projects like AbiWord need to start thinking about generic interfaces for this sort of thing. It's rather inefficient that every word-processor and every bibliographic solution needs to roll their own code for each piece.
Thanks for your answer. I cannot speak for the community of Abisource developers, but the discussion on
http://bugzilla.abisource.com/show_bug.cgi?id=11271
gives me the impression that, basically due to a lack of manpower, they won't develop a plugin on their own. However, they also write that if someone else (within the Zotero-Project?) would work on a plugin,
"We'd happily help them and consider including their plugin in our distribution."
Unfortunately, I'm no programmer and cannot contribute any code (sigh...). But if someone shares the conviction that an Abiword-integration would be useful, has some time left and is able to write such plugin it would certainly be welcomed by many people who are not happy with, or not even able to make use of, the memory-consuming OpenOffice.org-package.
It might be valuable for the Zotero team to consider licensing the plug-in under different terms than the main code though. Developers do get rightly nervous about licensing issues, and better (in my view) to use widely under licenses where you can.
Also, I think applications like Zotero should be easily able to integrate into ANY editing solution: AbiWord, Google Docs, emacs, etc. etc. But just for the record, I think it's likely that the best way to do this is to develop a generic API.
See also this thread for a discussion on a possible more general solution.
(1) a simple (text-only?) and reliable format for reference-marks which would have to be inserted into the documents (it would suffice if that would be done by selecting the reference in Zotero, applying a certain shortcut and pasting the mark into the document);
(2) a reliable cross-platform post-processor which would process the final document and change the reference marks into full bibliographic data.
The post-processor should be able to process the most important formats (e.g. rtf, odf, doc), but it would not have to deal with all kinds of APIs of many different programs. Currently, formatting bibiliographies is one of the (few) clear weaknesses of Zotero in comparison with programs like EndNote. However, if we abstain from imitating nice but, at least in my view, completely unnecessary features (like the 'cite while you write' functionality), and focus instead on reliability and flexibility (in terms of cross-platform compatibility and a simple and well-documented front-end for modifying bibliographic styles), Zotero could become superior in this area as well.
(begin cheerleading)
This morning I compiled the word processor from source on my netbook, created an AbiCollab account, and clicked around a bit. It's well designed. From end to end, the whole kit is straightforward, lightweight, intuitive, gregarious, and as far as I can tell, very robust. This looks like a truly brilliant solution for collaborative projects, and an excellent companion to Zotero.
To anyone who undertakes to put a plugin together for this product: I hereby undertake to cheer you on with great enthusiasm from the back of the room. It really would be a great contribution.
(end cheerleading)
* Support for metadata embedding seems to be on the to do list of the Zotero developers: http://forums.zotero.org/discussion/8237/merge-two-doc-files/?Focus=37203#Comment_37203
http://msevior.livejournal.com/28805.html
http://www.abisource.com/wiki/AbiCollab
This collaboration feature alone is outstanding. It takes a min for any collaborator to download it (wonders of free software) and start working on a paper together.
Maybe we could pool money together and make a bounty for someone to implement this? If interested, contact me, my lastname @ gmail (homepage on my profile).
I would also like to ask is there anyway to offer to pay/donate to help develop this plugin?
Personally, I find it MUCH more important to improve and support the RTF-scan feature in Zotero so that any program that is able to export to RTF can make use of it. Even writing a paper in collboration with authors who use different text-processors won't be any problem then.
Of course, if you cannot or do not want to use RTF, this solution will not do. Hence, something like LyZ, the Zotero-Connector for LaTeX-processor LyX, is another story. Since I love LyX, I really hope that LyZ will stay.
Also, if you really need something like "Cite while you write", RTF-scan will not be a solution as well. However, I never understood why it could be important to get references and bibliographies formatted "on the fly" instead of after finishing the paper.
I want to be able to write, insert a reference, and then continue writing. Without having to worry about having the correct formatting so that the RTF-scan will pick it up. I could just use LibreOffice/OOo, but I prefer Abiword as it is much lighter, and much nicer for many of the types of writing I do.
It's not the end of the world if I can't use Abiword as I do LibreOffice/OOo, but it would be nice.
fbennett: do you have any idea about developers who might be interested in this type of project?
> It's not the end of the world if I can't use Abiword
> as I do LibreOffice/OOo, but it would be nice.
Well, I agree...
The Abiword project and its forums would probably be the place to check, since whoever undertook it would need to know the Abiword internals pretty well. The hardest part might be lining up maintenance, to be sure the plugin is updated to reflect future Abiword revisions.