Non-recognisable Bible Reference hyperlink not working
I've followed the video instructions from http://www.mpseminars.com/videos#,
but the link doesn't seem to be working. I've got:
Normal
0
false
false
false
EN-AU
X-NONE
X-NONE
Normal
0
false
false
false
EN-AU
X-NONE
X-NONE
6 Ps 50:14; 1 Cor 16:2; 2 Cor 8 and [[9 >> 2 Cor 9]].
However, it tags everything except the 9 that I want tagged (see attached file).
I can't figure out what I'm doing wrong. I'd greatly appreciate any assistance.
Comments
-
Hi Ruurd - and welcome to the forums.
The syntax below should work:
Ps 50:14; 1 Cor 16:2; 2 Cor 8 and [[9>>Bible:2
Cor 9]]Note:
- you don't need the first two references to be hyperlinked to Biblia - but it doesn't cause any problems if they are
- no spaces either side of the ">>"
- you need to tag the 2 Cor 9 reference as a Bible Datatype link (see details at http://wiki.logos.com/Personal_Books)
Hope this helps
If it doesn't work, please post back
Graham
0 -
Hello Graham
Thanks for your help. That worked. However, when I put the full stop back after the last square bracket, it stopped working. Putting a space between the square bracket and full stop solved the issue. However it is a bug that needs to be resolved.
I also have the same problem at another place in my document, but I haven't been able to find out the problem is here. I've even tried putting spaces between the last square bracket and the semicolon.
1 Gen 1 and [[2>>Bible:Gen 2]] ; Ex 20:11; Job 38 and [[39>>Bible:Job 39]] ; Ps 33:6;Is 44:24; Acts 4:24; 14:15.
Ruurd
0 -
-
Hi Ruurd
Ruurd Offringa said:However, when I put the full stop back after the last square bracket, it stopped working. Putting a space between the square bracket and full stop solved the issue. However it is a bug that needs to be resolved.
I have just run a test with a period after the closing brackets and it works fine.
Are you able to post a sample where its not working?
Graham
0 -
Hi Graham
I've attached the document with the two problem parts.
The results are a bit random - I tested it again after your reply with no space between the square bracket and the period and it worked. However, the last one I send doesn't work. I've attached a screenshot of the compiled results.
Ruurd
0 -
I have a quite similar problem. When I compile the book, the Bible milestones don't work. Does anybody have a clue how I fix it?
Clacir Virmes Junior
0 -
Ruurd Offringa said:
I've attached the document with the two problem parts.
Put space either side of >> e.g.
[[36 >> Bible:Jn:3:36]]
Dave
===Windows 11 & Android 13
0 -
Hi Dave
Thanks for the suggestion. However, it doesn't solve the problem.
Ruurd
0 -
Hi Ruurd
Can you post the document - not just a screen shot of the document?
Graham
0 -
Clacir Virmes Junior said:
I have a quite similar problem. When I compile the book, the Bible milestones don't work. Does anybody have a clue how I fix it?
Can you post a portion of the actual document?
Graham
0 -
-
Sorry Graham
I thought I had - It must have been removed when I attached the screenshot. When I compiled the shortened document the second reference with the fullstop also didn't work again.
Ruurd
0 -
I have examples of similar inconsistencies! Upload your docx file so others can experiment with it.
Dave
===Windows 11 & Android 13
0 -
Clacir Virmes Junior said:
I have a quite similar problem. When I compile the book, the Bible milestones don't work. Does anybody have a clue how I fix it?
Upload your docx file (or part thereof) as mentioned above (click the blue hyperlink and attach the docx file same as Log files).
Dave
===Windows 11 & Android 13
0 -
-
Clacir Virmes Junior said:
It is attached. Thanks for the help!
Hi, when I compile this the document seems to be created ok - including the milestone.
The problem seems to be that it isn't recognising "Gênesis 1:1" as a Bible reference and hence creating the correct linkage.
This looks to be an issue with language support in the parser - I have seen a few reports of similar issues.
As a temporary workaround you could use the construct "[[Gênesis 1:1
>> Bible:Genesis 1:1]]"Here you are using the text you want as a label and then linking to a Bible reference.
Updated document attached
1346.Hinário Adventista do Sétimo Dia.docx
Hope this helps
Graham
0 -
Clacir Virmes Junior said:
It is here.
Hi Clacir,
Your milestone worked for me when i built your docx.
1. After building your PB click on text after where you placed your milestone.
2. Then if the milestone worked you will see it here in the reference box.
0 -
Ruurd Offringa said:
I thought I had - It must have been removed when I attached the screenshot. When I compiled the shortened document the second reference with the fullstop also didn't work again.
Strange - I have taken your document, compiled it and see the problem.
If I create a new document and type the same string "Gen 1 and [[2 >> Bible:Gen 2]]; Ex 20:11; Job 38 and
[[39 >> Bible:Job 39]]; Ps 33:6; Is 44:24; Acts 4:24; 14:15" by hand it works fine!How are you creating your document? From scratch or from some other source?
Graham
0 -
Thanks, Graham. I'll figure out why it is not compiled as expected. Thanks again for your effort. God bless you!
Clacir Virmes Junior
0 -
Thanks, Steve. God bless you!
Clacir Virmes Junior
0 -
Thanks so much, Graham. God bless you!
Clacir Virmes Junior
0 -
Thanks Graham
Retyping it solves the problem.
I created the document from a document I had prepared for Logos 3 PBB. I also saved it to rtf and then saved it back to docx to try clear any problems.
Ruurd
0 -
Ruurd Offringa said:
Thanks Graham
Retyping it solves the problem.
I created the document from a document I had prepared for Logos 3 PBB. I also saved it to rtf and then saved it back to docx to try clear any problems.
Ruurd
It worked for me initially after retyping but not after I made a change. See http://community.logos.com/forums/t/37373.aspx
Dave
===Windows 11 & Android 13
0 -
Hi Ruurd
Ruurd Offringa said:Retyping it solves the problem.
That's good news
Ruurd Offringa said:I also saved it to rtf and then saved it back to docx to try clear any problems.
Yes, I tried that as well but it didn't seem to fix anything.
Looks like there is an underlying problem which Dave has reported. But glad yours is working
Graham
0
