Import BibTeX styles and DOI turning Chinese

[macvet]

Hi Jon,
dear all,

with my change to an Intel iMac I will also transfer my ~30.000 references from Papyrus to Bookends. As recommended I tried to make use of the BibTeX export format in Papyrus and import filter in Bookends.

Unfortunately some text formats didn't make the transfer:

\underbar{phrase} -> phrase underlined
{\bf phrase} -> phrase in bold style
{\it phrase} -> phrase in italic style
{\copyright} -> COPYRIGHT sign ©
\break -> should be a line break
\% -> %
\~ -> ~
\& -> &

There might be more, but for now I found those above. For some of them I can just run a script to exchange the expressions. But AFAIK Bookends accept only pure text files so I can't use real bold and italic style formats in a text file. Is there any solution to keep such style formats when transferring the database?

Furthermore the contents of the DOI field are changing to asian characters after a while, which is strange.

Thanks for your help!

[Jon]

Hi,

The only transfer method that transfers styles along with text is via EndNote XML, and that obviously won't work with Papyrus. Bookends won't convert BibTeX style runs to styled text. I haven't tried, but if EN does import BibTeX with styles, you could import it into the EN demo (unlimited references for 30 days) and then export as EN XML...

As for the DOI business, please Repair (not Rebuild) your database. If you still have problems, please contact tech support.

Jon
Sonny Software

P.S. If you're going to have 30K+ references, don't forget to increase your database cache (Preferences). I'd try 20 or 25 MB.

[Eingang]

I've also had the DOI field insisting on being some non-Roman character set on some records as well. I was never able to figure it out and now that I see someone mention it, I can't, of course, find an example. If I do, I'll remember to mail support. Just thought I'd mention it so you'd know it's not just a one-person issue.

[Jon]

Hi, it's a rare but known issue that is due to the database getting confused about the "endian-ness" of the data. The happens to some old databases migrated from a PPC to an Intel Mac. It happens to text in the reference window drawer, not the main window. The bug in the database engine was fixed long ago, but it can still pop up in databases made long ago. The solution is to Repair (not Rebuild) the database if that happens. This usually (not always) fixes the existing text, and always allows you to enter new text without this problem.