Dave Pawson wrote:
On 11/10/05, Bruce D'Arcus <[EMAIL PROTECTED]> wrote:
Might be silly Bruce, but if you are trying to please a number of users;
how about splitting it (to ease processing and reduce compromises).
By "it" you mean the processing code? That's certainly a possibility.
Perhaps even the end to end options.
Is it effectively 3 items?
1. Gloss entry (Is the xforms input helpful here?)
2. Integration with the remainder of the document.
3. Output transforms.
What sense does it make viewing the path through the 3 bits
in isolation (with hooks for the other stages?)
I'm not following you above Dave (the xforms thing has me stumped), but
there ARE three bits. User experience would be:
1. user starts document, chooses style
2. user drops citations on document (or perhaps links content to a
reference in some other way than inserting)
3. citation and bibliography is automatically generated
On my xbib website I actually have menu items that reflect this
more-or-less:
cite
style
process
There are a variety of issues here. Does user choose citation style
apart from document template styling? I could imagine a menu item with
the citation styles, for example, so that user just changes with a
change of menu item. In fact, as a user I would prefer that.
Related, you have to understand the larger styling issues here. There
are literally thousands of bibliographic styles out there. Every
journal and book publisher basically has their own. With the Word
plug-in Endnote, they have an online repository of citation styles that
numbers over 1000, and the user can just download them. But they're
closed binary files.
We can change this because my style language is XML, and because OD
itself is XML. So while I could imagine downloading a complete OD
template file that defined citation formatting too from some website
(say a publisher's), I could also imagine separately downloading
citation styles (ideally via web service access).
The discussion about citation styling -- the low-level details of how it
would work -- obviously impacts on that, which is why I was asking about
that. I'm under pressure to stabilize CSL, in part because other
(non-OOo) developers are now building applications around it. See:
<http://netapps.muohio.edu/blogs/darcusb/darcusb/archives/2005/10/05/csl-design-and-guis>
He now has a working app, but doesn't want to release it until I can
tell him the schema is relatively stable.
Likewise, I've talked to a guy who was interested in using CSL for a
Perl formatting solution that did both OOo and LaTeX files IIRC.
Bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
