Yes, Bruce, I'm still here.I'm not much of a programmer either, but I do have some working on with me, and citeproc is within the scope of our work, the issue is when we can get to it.I will try to contribute more, but for now I think that Python makes sense for the reasons you have given, the
I'm now looking through the existing bib API documentation to see what
we might be able to retain for the bib project, and what would need to
change.
Some quick thoughts:
1) Reference types
One thing we could do is propose to change this to use my class list:
On Jan 29, 2006, at 6:20 PM, pt wrote:
One thing that particularly concerns me is Word to OpenDocument
interchange (both directions). My experience in our practical
courseware publishing project is that we have to work at the level of
standardised style names to interchange documents (this
On Jan 28, 2006, at 10:08 AM, Bruce D'Arcus wrote:
On Jan 28, 2006, at 10:43 AM, Bruce D'Arcus wrote:
I really don't care whether it's Python or Ruby, since both are
object-oriented, and both are easy to read.
At any rate, ultimately I'd like to see both citeproc-rb (think a
module that
I agree that test-driven development will help a lot here.One starting point would be tests that show you can load data into some object from the RDF serialization suggested by Bruce then re-serialize it back out. Trivial to implement at first, but needs to be there as more code gets built.
Bruce,
On Jan 29, 2006, at 9:52 PM, pt wrote:
I agree that test-driven development will help a lot here.
One starting point would be tests that show you can load data into
some object from the RDF serialization suggested by Bruce then re-
serialize it back out. Trivial to implement at first, but
On Jan 29, 2006, at 10:32 PM, Edward Summers wrote:
Bruce, I'm interested in helping out with this. I'm pretty familiar
with both ruby and python but I don't have a good grasp on what
exactly you want to do. Assuming the library existed could you flesh
out how it would be used
