PBB and non-recognizable Bible Reference Hyperlinks

I am not sure if this is since the SR-4 update or not, but I cannot seem to get the non-recognizable Bible Reference Hyperlink syntax to work. I have looked at the help reference and viewed the MP video.

I am typing the double brackets to the left of the reference, then a space AFTER the text followed by the two greater than symbols followed by a space followed by the scripture reference followed by the double brackets -like the below...

And, this is exactly how it shows up in the PB.

Has anyone else experienced this?

I have tried this several times. I have removed the space before the double-greater-than brackets, and then tried that. Still no change. I have tried removing the space after the double-greater-than brackets, and then tried that. Again, no change. I have tried saving the file as an RTF (as suggested in the wiki) and opening the RTF and saving as docx. Still, no change.

I am not sure what to do.

Find more posts tagged with

Comments

Graham Criddle

Hi Bill

I have just typed the reference as you have it into a .docx file and it compiles fine for me - on SR4

You might try posting a fragment of the document containing this reference and we can have a look at it.

Graham

Rosie Perera

https://community.logos.com/discussion/comment/290574#Comment_290574

Sometimes the XML code (which you can't see, it's packaged inside the .docx file) gets split up into separate chunks when you edit the document, and the Logos PBB compiler sometimes chokes on that.

Try typing that bit of text (from the open double square-brackets to the closing double-square-brackets) back in again completely in one feel swoop with no edits (and only then deleting the old version of it after you've copied it verbatim). That has fixed this problem for me when I've had it in the past. However I do think the PBB compiler should be more robust about it. What you see in Word should be what you get in the PB, regardless of how yucky the XML code looks under the hood. (Actually, Word shouldn't create yucky XML code in the first place.)

Bohuslav Wojnar

Bill, 1 Cor. is not abbreviation recognized by Logos of the 1 Corinthians. You can use the following:

1
Cor, 1 Co, I Co, 1Co, I Cor, 1Cor, I Corinthians, 1Corinthians, 1st
Corinthians, First Corinthians (see the following page: http://www.logos.com/support/lbs/booknames )

I hope it helps.

Dave Hooton

I am not sure if this is since the SR-4 update or not.

I cannot get the 1 Cor. reference to work after removing all full stops (periods) between [[ ... ]] but my Test PB is definitely broken by SR-4!

See http://community.logos.com/forums/t/38892.aspx

Graham Criddle

https://community.logos.com/discussion/comment/290582#Comment_290582

Hi Bohuslav

Bill, 1 Cor. is not abbreviation recognized by Logos of the 1 Corinthians. You can use the following:

I thought that was the case but - as per my post above - when I type it in it compiles correctly.

My test document attached

3108.Test PBB.docx

resulting in

Graham

Christine Francis

All my PBB now show the milestones on Logos 4 if I rebuilt them. They did not before. The ones I just open and do not rebuild are fine. I have not changed the milestones.

I deleted all my files in one personal book and started from scratch by re-adding the files and the milestones still show up in my personal books in Logos 4. Do I need to rename all my files and do it again?

Thanks for your help.

Bill Cook

https://community.logos.com/discussion/comment/290706#Comment_290706

Thanks folks! Is it possible that the document is just too complex?

I have tried running the Office repair twice and it is still not working. I have uninstalled Office 2010 and have installed LibreOffice. I will eventually re-install Office 2010... LibreOffice crashes when attempting to save this document.

But, I really believe things were working better under SR-3.

I CAN in LibreOffice just type [[14:1 >> 1 Cor 14:1]] and run PBB and it works.

So, am surmising that some part of the XML is messed up... Oh brother... I have put many hours in this and was about half way done.

Tim Drushal

https://community.logos.com/discussion/comment/290794#Comment_290794

I have been experiencing this same issue. I, however, am using Word 2007 in Windows XP. I have tried re-saving the original .rtf to .docx (cleaning?) at least three times. I have deleted the PBB and rebuilt it twice. Just to make sure that it wasn't one particular document, I tried compiling two other documents through the same process with exactly the same results. I also went back into a document that had been previously compiled without any problems and added a new "labled datalink". It compiled everything again EXCEPT the new datalink.

Other than the Logos update, Windows XP had a security update this this week. I am at loss for what to do next.

Dave Hooton

https://community.logos.com/discussion/comment/290706#Comment_290706

I deleted all my files in one personal book and started from scratch by re-adding the files and the milestones still show up in my personal books in Logos 4. Do I need to rename all my files and do it again?

As I said above PB is broken in SR-4. We have to wait for Logos.

Bohuslav Wojnar

https://community.logos.com/discussion/comment/290794#Comment_290794

I CAN in LibreOffice just type [[14:1 >> 1 Cor 14:1]] and run PBB and it works.

As I said already in the above post 1 Cor. is not valid abbreviation in Logos. You have to use one of those given above, for example 1 Cor (without full stop).

EDITED: I just noticed you commented my previous post and tried to use the abbrev. without full stop. It have to be the problem with the SR4.

Bohuslav Wojnar

https://community.logos.com/discussion/comment/290837#Comment_290837

As I said above PB is broken in SR-4. We have to wait for Logos.

That is exactly what I just noticed when trying to compile books I already successfully build previously. Milestones do not compile sometimes at all.

Bill Cook

https://community.logos.com/discussion/comment/291017#Comment_291017

Well, I think I have a work-around for this now. I can get it to work in Word 2010. What I have to do is highlight the text, not backspace over it, and delete. Then, I go back and type [[14:1>>1 Cor 14:1]]. Also, it DOES NOT work with a space before and after the greater than brackets as instructed... Those spaces have to be removed. Then, and so far, it seems to have worked...

I have not tried with any of the above milestone issues. But, perhaps it might work.

Dave Hooton

https://community.logos.com/discussion/comment/291363#Comment_291363

I have not tried with any of the above milestone issues.

See Logos' response http://community.logos.com/forums/p/38892/291494.aspx#291494