Has anyone got these tags working?

I've not had any success getting these types of tags to work. Has anyone else?

(v.[[14|Bible:Ezekiel 12:14]], e.g.),
I've tried with/without a space after the colon following Bible. The PBB output simply repeats the code, and won't parse it as I'd like: (v.14,e.g.)

EDIT: can't get the hyperlink on the 14 to properly point to Ezekiel 12:14 on this forum. Probably a simple fix, but I don't know what it would be. But you still get the idea.

Find more posts tagged with

Comments

Mark Barnes

There are two bugs that affect links, both documented on the Wiki page:

The links sometimes aren't recognised (the RTF workaround usually fixes this)
The compiler does not handle datatype links correctly. When specifying a datatype link, the compiler creates both a datatype link to any resource, and
an ordinary link to the current resource. This is correct only if the
current resource has a location that matches the datatype. If it does
not have that location, the compiler should not add the ordinary link
because doing so prevents the datatype link working. The work around is
that instead of clicking on the link, you can right-click on it, select
the datatype and choose ‘open’.

<edit>This post includes some example documents that use the format you're attempting to 'prove' it does work!</edit>

Rich DeRuiter

https://community.logos.com/discussion/comment/256683#Comment_256683

There are two bugs that affect links, both documented on the Wiki page:

The links sometimes aren't recognised (the RTF workaround usually fixes this)

I've tried the RTF workaround numerous times without success. I also have smart tags and grammar turned off. The rest of my document compiles as desired.

Maybe it's still in the realm of 'unknown factors.' It's not that big of a deal, but it does make me wish there was a PBB editor built in to the system.

BTW, how does one view the background code for a docx file? Maybe there's something going on in the XML that might give me a hint about how to fix it.

Mark Barnes

https://community.logos.com/discussion/comment/256688#Comment_256688

BTW, how does one view the background code for a docx file? Maybe there's something going on in the XML that might give me a hint about how to fix it.

Use WinZip to open the .docx file directly. If you don't have WinZip or an equivalent, rename the .docx to a .zip and use Windows to open it. Then open the word folder, and look at document.xml in a text editor.

Rich DeRuiter

https://community.logos.com/discussion/comment/256695#Comment_256695

Use WinZip to open the .docx file directly. If you don't have WinZip or an equivalent, rename the .docx to a .zip and use Windows to open it. Then open the word folder, and look at document.xml in a text editor.

Thanks Mark. Doing so showed some interesting things that got mixed into the text by Word.

I deleted the entire reference and retyped it (rather than editing what I had put in earlier) and it worked in the way you described. Hovering the reference doesn't display the verse, but it does show the verse in a pop-up in the lower left of the panel, and I can open the text through the right click menu.

Obviously, it's not what we want as a final solution, but it will work for now.

I must say I'm quite discouraged by MSWord's ability to keep its XML clean. It's going to make the PBB design very difficult, without washing the code through a filter of some sort. I'm beginning to understand why it's taken so long to get the PBB to this point.

I wonder if using PDF as the base text for import would simplify things on the programming end.

Mark Barnes

https://community.logos.com/discussion/comment/256760#Comment_256760

I must say I'm quite discouraged by MSWord's ability to keep its XML clean. It's going to make the PBB design very difficult, without washing the code through a filter of some sort. I'm beginning to understand why it's taken so long to get the PBB to this point.

Yes, Logos will have to 'wash' the XML itself - it can't be expected that we users do it separately. I don't think it will be too complex though. It's almost always the same tag that is causing the problem.

I wonder if using PDF as the base text for import would simplify things on the programming end.

PDFs are worse. Just one example - a PDF won't create a link between a footnote indicator and the footnote itself.