Bug: My Test PB no longer compiles in SR-4

The PDF below is a build with your file from the OP on my load of L4 which is SR-3. There were only 3 tags which did not compile and they are marked in yellow highlighting from L4.

Printout from L4 for Peacemaker; compiled in Logos Bible Software 4.3 SR-3 (4.30.0.1592)

2860.Peacemaker (Dave).pdf

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/290632#Comment_290632

I can confirm its messed up, compiler is extremely fussy in this build..

Concur Logos 4.3 SR-4 has Personal Book build regressions. For example, hyperlink logosres:ldgnt;ref=BibleNA27.Php4.9 for text Php 4:9 (using Word 2010) builds, but shows verse pop-up for Top prioritized Bible (missing LDGNT) and clicking link opens Top Bible instead of LDGNT.

In contrast, a Personal Book built in Logos 4.3 SR-3 with hyperlink logosres:ldgnt;ref=BibleNA27.Eph1.4 for text Eph 1.4 continues to show LDGNT and Top Bible for pop-up in Personal Book in Logos 4.3 SR-4. Also can copy and paste link into new Personal Book document, which shows LDGNT and Top Bible after Logos 4.3 SR-4 Building.

Keep Smiling [:)]

NB.Mick

https://community.logos.com/discussion/comment/290724#Comment_290724

Concur Logos 4.3 SR-4 has Personal Book build regressions

I quote myself (from this thread: http://community.logos.com/forums/t/38857.aspx )

I sometimes wonder why the SR's are not beta tested or capable of manual rollback - they just go into the productively installed base and whoever has automatic update installed will receive the SR without a chance to go back to the last stable release if it was buggy.

and I think we'll see 4.3 SR-5 sooner than 4.5 beta (assuming the developers get the errors sorted out, that is)

Dave Hooton

https://community.logos.com/discussion/comment/290673#Comment_290673

There were only 3 tags which did not compile and they are marked in yellow highlighting from L4.

Thanks Steve,

That's exactly the way it compiled in my SR-3 (1 Cor has invalid verse nos; don't know about the others).

SR-4 has regressed!

M G Smith

I downloaded Dave's first docx and compiled a PB from it, and saw the many links that had failed to compile properly. I then opened the docx in LibreOffice and altered it as follows: Ctrl+A to select all text, changed the font to Times New Roman, saved the changed file. On recompiling the PB, all but two of the links were working: the DBL Hebrew link and the Test in Cor one. The Job 39 link which Steve marked in his pdf as not working in SR-3 was working in the PB compiled as described.

I am not sure what this tells us, but report it anyway.

Dave Hooton

https://community.logos.com/discussion/comment/291153#Comment_291153

I then opened the docx in LibreOffice and altered it as follows: Ctrl+A to select all text, changed the font to Times New Roman, saved the changed file. On recompiling the PB, all but two of the links were working: the DBL Hebrew link and the Test in Cor one.

Sorry, did not work for me using Word 2007

I am not sure what this tells us, but report it anyway.

It tells me that SR-4 should not have been a service release, because it may have fixed ONE bug but caused a few others!

Tonya J Ross

There is a regression in 4.3 SR-4 which prevents milestone, headword, other syntaxes from compiling normally. The issue has already been reported to Development and will be corrected in an upcoming release.

Dave Hooton

https://community.logos.com/discussion/comment/291153#Comment_291153

I am not sure what this tells us, but report it anyway.

My (belated) thanks for reporting what you found.

If LibreOffice got my docx to work in SR-4 then I may have an upgrade path from Office 2007!

Dave Hooton

https://community.logos.com/discussion/comment/291494#Comment_291494

The issue has already been reported to Development and will be corrected in an upcoming release.

Service Release? We shouldn't have to wait for v4.5 for this.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/290724#Comment_290724

The => 1534 Tyndale Bible PBB also has milestone and field compilation issues using Logos 4.3 SR-4:

Concur Logos 4.3 SR-4 has Personal Book build regressions. For example, hyperlink logosres:ldgnt;ref=BibleNA27.Php4.9 for text Php 4:9 (using Word 2010) builds, but shows verse pop-up for Top prioritized Bible (missing LDGNT) and clicking link opens Top Bible instead of LDGNT.

In contrast, a Personal Book built in Logos 4.3 SR-3 with hyperlink logosres:ldgnt;ref=BibleNA27.Eph1.4 for text Eph 1.4 continues to show LDGNT and Top Bible for pop-up in Personal Book in Logos 4.3 SR-4. Also can copy and paste link into new Personal Book document, which shows LDGNT and Top Bible after Logos 4.3 SR-4 Building.

Thankful for Logos 4.3 SR-5 that has fixed my Logos 4.3 SR-4 regression issues.

Keep Smiling [:)]

Dave Hooton

https://community.logos.com/discussion/comment/291503#Comment_291503

The issue has already been reported to Development and will be corrected in an upcoming release.

Service Release? We shouldn't have to wait for v4.5 for this.

Thank you for SR-5. My PB Test is down to one anomaly instead of three! It won't recognise

[[פָּקַד >> logosres:dblhebr;hw=$D7$A4$D6$BC$D6$B8$D7$A7$D6$B7$D7$93]]

Melissa Snyder

https://community.logos.com/discussion/comment/292046#Comment_292046

Thank you for SR-5. My PB Test is down to one anomaly instead of three! It won't recognise

[[פָּקַד >> logosres:dblhebr;hw=$D7$A4$D6$BC$D6$B8$D7$A7$D6$B7$D7$93]]

The syntax above will work in version 4.5. In the meantime, try creating the link using the Word hyperlink feature instead. That worked for me in 4.3 SR-5.

Dave Hooton

https://community.logos.com/discussion/comment/292157#Comment_292157

The syntax above will work in version 4.5. In the meantime, try creating the link using the Word hyperlink feature instead. That worked for me in 4.3 SR-5.

Thanks,

It's weird because the DBL Greek example works

[[χοῖρος >>
logosres:dblgreek;hw=$CF$87$CE$BF$E1$BF$96$CF$81$CE$BF$CF$82]]

I forgot that this still does not work:-

I don’t want this reference {{~ Jn 3:12 }} to be detected.

Melissa Snyder

https://community.logos.com/discussion/comment/292518#Comment_292518

Escape syntax will be converted correctly in version 4.5; the fix will be included in Beta 1.