BUG: BDB footnotes are not copying and pasting when pasting text from BDB

When copying and pasting text into Word, no footnotes show up for BDB. I have to go back to Logos to physically copy and paste them into Word or any other Word processing program. I restarted Logos and the problem persists. I have Logos version 4.2a SR-2 (4.21.5.0906). I am not sure what other information you need.

Also, please fix the Morphology Searching. Clicking the tags still does not work properly. I have to type the correct corresponding letter to such as qal, or hiphil, etc. and same with masculine or feminine, or singular or plural or dual. I have type those tags in myself. Please fix this.

Caleb

Find more posts tagged with

Comments

Jack Caviness

When copying and pasting text into Word, no footnotes show up for BDB.

Do you have "Copy Footnotes" set in Program Settings?

Caleb S.

https://community.logos.com/discussion/comment/230161#Comment_230161

Well, by default it was never on. But when copying and pasting from any other book, such as HALOT, BDAG, or any other commentary, it automatically pasted a footnote for the resource, without Copy Footnotes on. I guess I will turn that on and see if it works.

*less than 5 minutes later* Okay, so I closed Logos last night and I opened it back up this morning. I turned on Copy Footnotes, and opened a different Word Processing program and it added not just a footnote for BDB, everything else that was highlighted that had a footnote got pasted, such as there is a Logos footnote on the square root sign, and that got pasted. Since I don't need ALL of those footnotes, I turned it back off. Recopied and pasted and it did paste a citation for BDB this time. Opened up Word, and it pasted the footnote citation for BDB as well. So, it somehow fixed itself, since it works now. Not sure how that happened. Thanks anyway. (Oh and yes, I had closed Logos and reopened it up yesterday to no avail; but it worked this time...odd.) So it is fine now.

Jack Caviness

https://community.logos.com/discussion/comment/230337#Comment_230337

So it is fine now.

Thank you for the update.