Detection of Word Hyperlinks in Personal Books

Page 1 of 1 (9 items)
This post has 8 Replies | 2 Followers

Posts 68
Vadim | Forum Activity | Posted: Thu, Jul 13 2017 3:58 PM

Hello,

I am having a problem importing personal books where the footnotes are marked by internal Word hyperlinks, rather than the standard Word footnotes/endnotes.

The hyperlinks work fine within the word document, but do not work once imported to Logos.

Is this a know bug?

Note links 6 and 7 in the below example:

Posts 3328
Whyndell Grizzard | Forum Activity | Replied: Thu, Jul 13 2017 4:23 PM

See if converting them to end notes solves the issue- I have found it to work on a few occasions- if not get ready to redo them all.

Posts 68
Vadim | Forum Activity | Replied: Thu, Jul 13 2017 8:24 PM

I assume that would require writing a macro, and would not be an simple task.

I image it would not be a problem to modify the way that Logos processes personal books in order to handled internal hyperlinks.

Posts 3328
Whyndell Grizzard | Forum Activity | Replied: Sun, Jul 23 2017 5:28 AM

Don't know if this could associated- but compiling new PBB's causes a crash for me. I was told it was internal linking- I removed all hyperlinks still have same issue. I went back to my Word docx ctrl/clicked link it takes me to Biblia instead of opening Logos, not sure of the issue- but is directly connected to copy/ paste of note creating footnote from logos resource. Still working on it, but so far only deleting the reference works, and is not a big help solution.

Posts 3031
LogosEmployee
Andrew Batishko | Forum Activity | Replied: Sun, Jul 23 2017 6:10 AM

Whyndell Grizzard:

Don't know if this could associated- but compiling new PBB's causes a crash for me. I was told it was internal linking- I removed all hyperlinks still have same issue. I went back to my Word docx ctrl/clicked link it takes me to Biblia instead of opening Logos, not sure of the issue- but is directly connected to copy/ paste of note creating footnote from logos resource. Still working on it, but so far only deleting the reference works, and is not a big help solution.

That would be important information to post on the other thread where you reported the problem, along with information about which reference is causing the problem.

Andrew Batishko | Faithlife software developer

Posts 190
Scott David | Forum Activity | Replied: Mon, Jan 25 2021 2:23 PM

Andrew Batishko (Faithlife):
 That would be important information to post on the other thread where you reported the problem, along with information about which reference is causing the problem. 

NO DETECTION OF MICROSOFT WORD CROSS-REFERENCES WHEN IMPORTING INTO LOGOS PERSONAL BOOKS

Andrew, I couldn't find Vadim's other thread, or I would have posted there. I didn't want to start a new thread, because although a little different -- my problem is very similar to Vadim's.

My internal cross-references in Word are removed when imported into Logos' Personal Books. Is there any way to keep these cross references upon building a book? The book in particular is a logos manual I built: https://community.logos.com/forums/p/182780/1057673.aspx#1057673

(all the red text in the manual are cross-reference jumps to other sections of the document)

Posts 190
Scott David | Forum Activity | Replied: Fri, Jan 29 2021 1:59 PM

[SOLVED] Instead of using Microsoft Word Cross-References, use:

Insert > Link > Bookmark > (then link to either: A. Bookmark or B. Heading)

Posts 1006
Josh Hunt | Forum Activity | Replied: Fri, Jan 29 2021 2:17 PM

Whyndell Grizzard:

Don't know if this could associated- but compiling new PBB's causes a crash for me. I was told it was internal linking- I removed all hyperlinks still have same issue. I went back to my Word docx ctrl/clicked link it takes me to Biblia instead of opening Logos, not sure of the issue- but is directly connected to copy/ paste of note creating footnote from logos resource. Still working on it, but so far only deleting the reference works, and is not a big help solution.

I had trouble with this and discovered it was caused by Adobe fonts. When I did a select all, change the font to something Logos could deal with, it fixed the problem. You might also make sure styles don't have fonts that Logos doesn't recognize. 

Posts 190
Scott David | Forum Activity | Replied: Fri, Jan 29 2021 2:46 PM

Wow Josh... that's really interesting; thanks for sharing. I wish I had known that a few days ago (just spent hours redoing a Logos Manual) Surprise

https://community.logos.com/forums/t/182780.aspx

Page 1 of 1 (9 items) | RSS