I’m testing out Bookends as a bibliography manager at the moment, and so far reckon that it will do me just fine. However, I have one small niggle which I wonder if any of the Bookends experts on the forum can help me with.
When I process the .rtf exported from Scrivener to create the citations and bibliography, and then open the resulting main file in Nisus Writer Pro, en-dashes in page ranges in the citations are replaced by Ã±, so I get 43Ã±45, rather than 43â€“45.
Obviously, I can do a search and replace, using PowerFind Pro if necessary to limit it to replacing Ã± only when it occurs between numbers, but I’d rather not have to. Do any of you know how to get Bookends to retain the en-dash rather than replacing it?
Thanks Bryce. When I open the RTF file exported by Scrivener in NWP it has the en-dashes, so Scrivener is exporting the text without changing that. It’s only after running it through Bookends that they become Ã±.
Have you used en-dashes for page ranges, or do you usually use a simple hyphen? It is possible that Bookends expects hyphens marking page ranges, but for me they should be en-dashes. If that’s the case I’d rather have the Ã±s, as they are much easier to do a targetted find-and-replace on than simple hyphens.
I’ve also written to Sonny Software to see if they can help.
It turns out that the problem of en-dashes converting to Ã± is a result of the RTF coding used by the Apple Text-engine â€” TextEdit shows the same problem â€” being different from that used by both NWP and more importantly Bookends. NWP can handle the different coding, but Bookends, including today’s upgrade, changes the glyph.
The good news is that the next Bookends upgrade will resolve the problem. In the meantime, you can get round it by:
(a) Opening the RTF output by Scrivener in Nisus, resaving it, then scanning that in Bookends;
(b) Scanning the RTF output by Scrivener in Bookends, then doing a Find and Replace on the resulting file in Nisus;