It's occurred to me in looking at all this again that we need see where
we can simply use and/or enhance the existing bib APIs in OOo: to see
if we can disentangle what are GUI problems, from something fundamental
in the design.
It seems to me these APIs look fine:
Bibliography
============
<http://api.openoffice.org/docs/common/ref/com/sun/star/text/
FieldMaster/Bibliography.html>
It has the necessary sorting properties. I think it might just need a
property to say whether subsequent entries from an author get replaced
with em-dashes. In my CSL language, I have:
<bibliography author-as-sort-order="all" author-shorten-with="———."
sort-order="author-date">
We need something to cover the "author-shorten-with" attribute.
BibliographyDataField
=====================
<http://api.openoffice.org/docs/common/ref/com/sun/star/text/
BibliographyDataField.html#>
This is the one that has always made me cringe, because it's based on
BibTeX.
However, if I understand right, the data values here are just
constants, where the data itself is stored in a hash. If that's right,
then we could easily fix this.
BibliographyDataType
====================
<http://api.openoffice.org/docs/common/ref/com/sun/star/text/
BibliographyDataType.html>
As above, if we can easily change the types (like, say, now!), then we
can fix this.
Where I think the problem is is the citation/bibliography mark, but I
can't find the API documentation for that. Also, the bibliography stuff
needs to be understand as more generic, so that the data can be used
even if there isn't a bibliography printed (as with note citations).
Bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
