Compiling Personal Book Tyndale Bible has 13,400 warnings?
Has anyone tried recompiling the Tyndale Bible 1534 version that was posted on the forums as a Personal Book? It has 13,400 warnings, albeit it compiles successfully. They are all "Closing field bible that is already closed".
Any ideas?
Comments
-
Dominick Sela said:
Has anyone tried recompiling the Tyndale Bible 1534 version that was posted on the forums as a Personal Book? It has 13,400 warnings, albeit it compiles successfully. They are all "Closing field bible that is already closed".
Any ideas?
Tarnation. 13,400!
I successfully compiled this and did not receive any warnings whatsoever. I wonder if it is an issue which has come in with a recent software update? Are you running beta?
I will be back on my PC later this afternoon and will try compiling a second copy to see if I can repeat your issues (unless someone beats me to it).
Do you have the link to the .docx to hand (just to ensure that I am looking at the same thing)?
Andy
0 -
Yes, I am running on the latest beta (Beta 13). I have attached the DOCX file I used. Thanks!
0 -
Dominick Sela said:
Yes, I am running on the latest beta (Beta 13). I have attached the DOCX file I used. Thanks!
Dear Dominick,
Just to confirm that I have successfully compiled the attached file twice (for good measure) without incident or error message. The screenshot below confirms this. You will note that I previously successfully compiled this PB some weeks ago,
And, on successful compilation,
I am running the stable release (Mac and PC). I compiled this on the PC side (stable release). I wonder, therefore, if the issue is as a result of the current Beta? Perhaps someone running the Beta could attempt to compile this in order to pin down the issue. Alternatively, I wonder if there is an issue with the .docx at your end (corrupted in the download)... Exceedingly unlikely, I know.
Let me know if you need me to try anything else.
Andy
0 -
Hi gents
I have just tried to compile this document (for the first time on this computer) and it succeeded with 0 errors and 13,399 warnings!
I am also running 4.5 B13 (Windows) so it looks as though this could be a 4.5 issue
Graham
0 -
Graham Criddle said:
I am also running 4.5 B13 (Windows) so it looks as though this could be a 4.5 issue
It does compile successfully, Andy you won't see the warnings message in 4.3 because that's something new added to 4.5. The issues could have always been there but now they are reported - or it could be a bogus message. I sure don't see anything wrong with the Bible fields but I am not an expert!
0 -
Dominick Sela said:
Andy you won't see the warnings message in 4.3 because that's something new added to 4.5.
Apologies, Dominick, I missed that this had been posted under Beta.
Sorry for any confusion.
Andy
0 -
Hi Dominick
Dominick Sela said:Andy you won't see the warnings message in 4.3 because that's something new added to 4.5
I had missed that this error reporting was introduced in 4.5
Dominick Sela said:I sure don't see anything wrong with the Bible fields but I am not an expert!
I don't see anything wrong with them - although the verse numbers do use the "pipe" format which has now been replaced by ">>". But even changing this didn't seem to make any difference.
Need someone with a deeper understanding of PB syntax than me, I'm afraid!
Graham
0 -
Graham Criddle said:Dominick Sela said:
I sure don't see anything wrong with the Bible fields but I am not an expert!
I don't see anything wrong with them - although the verse numbers do use the "pipe" format which has now been replaced by ">>". But even changing this didn't seem to make any difference.
Need someone with a deeper understanding of PB syntax than me, I'm afraid!
I tried unsuccessfully to get an understanding of this message in the early beta's and my test PBB is a mere 2 pages with 6 Warnings. 13 400 should alert someone.
Dave
===Windows 11 & Android 13
0 -
Dominick Sela said:
Any ideas?
Appears {{field-on:Bible}} is not being recognized/processed after superscript verse number.
Keep Smiling [:)]
0 -
Appears {{field-on:Bible}} is not being recognized/processed after superscript verse number.
Which you can prove by turning "Bible Text Only" on in the compiled resource; only the first verse of each chapter is shown.
Additionally, the superscript verse number has lost its superscript formatting.
Both of these bugs will be fixed in the next beta.
0 -
YAY! Thanks Bradley, very nice job!!!
0 -
said: