I've come across an issue with the use of export templates when a list  
of publications are exported (in my case, to the clipboard). I don't  
have all the details of the affected tags worked out, but it is  
repeatable and I thought I'd go ahead and mention it now in case it  
rings any bells for anyone.

The gist of it is that depending on how a specific reference type's  
template tags are set up, if the reference has optional tags in its  
template text and there is no data for these tags, BibDesk may fail to  
place a return after the reference, running it together with the  
preceding reference in the exported text. This occurs with both txt  
and rtf template files. The return character after each reference-type- 
specific template in the file is not contained within the optional  
data tags for that reference type and each reference type is laid out  
similarly, with a return after its last tag and prior to the following  
<?$pubType=xxx> tag. When the same template is used to extract text  
for references one-by-one, each reference comes back with a return at  
its end. It appears consistent that the references that do not receive  
returns are missing a final optional data element (such as an edition  
number for a book or page numbers for an article) and that in addition  
to being optional, the final tags also happen to have a text  
processing directive, such as stringByRemovingTeX or  
stringByAppendingSpaceIfNotEmpty.

Is it possible to guarantee that references separated buy return  
characters in the templates will be separated by returns in the  
exported text, even if some of the final fields are empty?

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

Reply via email to