On Jan 25, 2008, at 5:50 PM, Christiaan Hofman wrote:
> All default templates included in BibDesk don't have this problem.
> The rules are clearly explained on the Wiki and in the Help. Returns
> right after a collection tag and a condition tag are not exported
> (either for the open and close tag).
Thanks very much for the really clear explanation of this issue, which
is going to help me a lot as I get more into templates.
As it turns out, my problem was a bit different but it took me a while
to track it down. I had derived my templates from a template I
downloaded from the BibDesk Wiki templates page, abbrvTemplate.rtf,
dated April 15, 2007.
Anyway, that file has the following sequence in its techreport template:
<$fields.Type?><$fields.Type/><?$fields.Type?>Technical report</
$fields.Type.titleCapitalizedString?>
Apparently on each tech report, processing would proceed until it hit
the closing $fields.Type tag with the inappropriate modifier, then
fail and go on to the next reference. No data was processed in the
template after the opening <$fields.Type?> tag, including the final
return, which was what caused the following reference to append to the
end of that one.
Sorry for pulling the trigger before I had it fully worked out--it
took a while for the light bulb to go on this time.
Ideally there would be a way to pass template errors up to the user
level ("Unrecognized token on line x of template y," or some such)
though naturally I have no idea whether it such a thing would be
practical.
Best wishes,
Jim Harrison
UVa
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
