It was last compiled on Sep 22 and worked OK in SR-4 until I re-compiled it today. Hardly anything works, starting with the headword milestones.
All I changed was a couple of links in the Hyperlinks section.
8233.Peacemakers.docx
Compile as Bible Notes.
Dave===
Windows 10 & Android 8
Dave Hooton:All I changed was a couple of links in the Hyperlinks section.
I "cleaned" the document but it only fixed the bible milestones shown above!
I can confirm its messed up, compiler is extremely fussy in this build..
Never Deprive Anyone of Hope.. It Might Be ALL They Have
Dave removing all the formatting it has errors but seems happier..
8015.8233.Peacemakers.docx
DominicM: Dave removing all the formatting it has errors but seems happier.. 8015.8233.Peacemakers.docx
Thanks, but it is worse than my "cleaned" version. It's still broken!
sorry - cant hack in and fix code this weekend :D
The => 1534 Tyndale Bible PBB also has milestone and field compilation issues using Logos 4.3 SR-4:
Keep Smiling
Logos Wiki Logos 7 Beta Free Support
Dave,
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
QLinks, Bibl2, LLR, MacrosDell Insp 17-5748, i5, 1.7 GHz, 8G RAM, win 8.1
DominicM: 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 4 Jesus :):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 )
NewbieMick: 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)
Running Logos 9 latest (beta) version on Win 10
steve clark: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!
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.
M G Smith: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
M G Smith: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!
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.
Diagnostic Logging
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!
Tonya J Ross: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 :):The => 1534 Tyndale Bible PBB also has milestone and field compilation issues using Logos 4.3 SR-4:
Keep Smiling 4 Jesus :): 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.
Dave Hooton: Tonya J Ross: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]]
Dave Hooton: 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.
Melissa Snyder: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.