two remarks on this good feature:
- it seems to be that ambiguous citations which are used in Mellel's footnotes are always asked twice. (the citation is definitely used only once in the manuscript.)
- it would be great if the option "use always this one" would be serviced: I would like to select the correct citation only once and saved this decision within my original Mellel manuscript. Now I sadly have to make the same selection again and again each time I scan my document.
ambiguous citations
sorry but I don't understand what's your point here: There is no second pass. I make *one* scan of a Mellel document which contains *one* ambiguous citation within a footnote. bookends asks me twice which is the correct reference while it only asks once for citations in the main text. therefor I thought this maybe is a bug.Jon wrote:That's a function of the way the function works. If it's still ambiguous after the first pass, you queried again on the second pass.
yes, of course. I did that meanwhile. But the point is: why should I do something manually, the software could do for me the first time the problem occurs? Please understand this as a feature request for further improvement of Bookends, which is already real great but far away from being perfectJon wrote:If this is so sad, why don't you just disambiguate the actual citation in Mellel? Add a unique word or the unique ID (#123432) to the citation.

Thanks, now I understand.
But how can it be that a citation is still ambiguous if I selected the correct citation before using the "this one"-button?
I just tried to reproduce the thing, but with a new document everything works as expected. If I delete the unique ID # again in the file the error occured, there it occurs again.
another little feature request: it would be fine if Bookends would allow the copying of the unique ID
But how can it be that a citation is still ambiguous if I selected the correct citation before using the "this one"-button?
I just tried to reproduce the thing, but with a new document everything works as expected. If I delete the unique ID # again in the file the error occured, there it occurs again.
another little feature request: it would be fine if Bookends would allow the copying of the unique ID