On 13/08/10 18:54, Stefan Majewski wrote:
> Please, if you do try it, let me know whether or not you like it and how
> it could be improved. It reflects more or less the way I use
> <biblStruct>s for writing papers. I reckon that I could be mistaken by
> some of the encoding choices.
Looks great, and most of the encoding choices seem fine to me with a
1) Why does the export just produce a <listBibl>? Why not produce a full
TEI document with minimal header (embedding the <listBibl> in <body>)?
This would allow you to do things like document the date/time that the
library was exported, the username the library belonged to, etc., etc.
2) The export embeds notes correctly, but one is allowed to do all sorts
of formatting of these notes, but this is lost. e.g. why not transform
the notes lists, bold, italics, etc. to similar TEI structures? Most
things are basic structures like paragraphs and lists (<head> elements
could perhaps be gathered into <div>s but that is perhaps more
difficult), and highlighting that could be done with <emph>.
This is a good export, I've not tested *all* the various Zotero's
reference types, but certainly promising, and I'm also glad it is GPLed.
I had given up on using Zotero ... I didn't like some of the
privacy/social aspects... (e.g. if you use their CV tool there is no way
to keep it private and only choose to publish it when you've tidied it
up.) But having a decent export to TEI might make it that much more useful!