36 replies to this topic

[Jogegore]

Thanks "BH"!
 
It was exactly what I wanted.
 
However, in the comments section (#define comments) and some names of books, do not have the accent, for example: Instead of G?n it should say Gén, in 'xo would be Éxo, etc. I have resolved these errors by making a replacement.
 
Finally, why when I try to save the ".bblx" file from Modules>Bible>Save Bible File book chap:verse (because I have made some corrections), I get the following error legend: "Bad Reference".
 
What is that?

Attached Files

•  Save Bible File .bblx - 2.jpg   99.58K   15 downloads
•  Save Bible File .bblx - 1.jpg   94.27K   15 downloads

[BH.]

Comment section - I'm not seeing what you are seeing in v2.38

 

Bad Reference - first, When T4 READS a BBLX file, it uses English book names, thus I have to conclude you edited the Gen 1 reference.  That said, the reason T4 does not recognize a reference is due to the book abbreviation not being in the Abbreviation List.  Check to be sure that your abbreviation list has the abbreviations required for your project.  Copy the default internal list to a new list and then edit and use that list for your project.

[APsit190]

However, in the comments section (#define comments) and some names of books, do not have the accent, for example: Instead of G?n it should say Gén, in 'xo would be Éxo, etc. I have resolved these errors by making a replacement.
 
Finally, why when I try to save the ".bblx" file from Modules>Bible>Save Bible File book chap:verse (because I have made some corrections), I get the following error legend: "Bad Reference".
 
What is that?

 

If I understand this correctly, you are creating a non-English Bible. The one thing is that in T4 you do not need to change the abbreviated references to the language you are creating it for. e-Sword changes the book names and references when the language of your choice is selected from the Option Menu.

 

Blessings,

Stephen (Php 1:21).

Edited by APsit190, 13 October 2014 - 02:46 PM.

[JPG]

Brent, isn't the "issue" caused by the user selecting the setting in "T4" under Scripture -> Spanish. So....what happens when the Bible is read-in. Where are the abbreviations taken from?

 

Jon

[BH.]

Jon - No.

 

The Spanish option here is only for CREATING tooltips.  When a BBLX file is read in, English names are used.  If the Abbreviations are not being recognized, that is an issue with the Abbreviation list in use.

 

BH

[Jogegore]

Thanks Again "BH" And "APsit190"!

 

In effect, only names of books in English was the solution.

However, again when I try to save the ".bblx" file from Modules>Bible>Save Bible File book chap:verse, I get another error message:

 PLEASE SEE THE ATTACHED PICTURE.

• What is the cause of this error?
• Is it because the words of Genesis 2:23 are separated on different lines or sentences?
• "e-Sword ToolTip Tool NT v2.38" not allow to separate a verse on different lines or sentences?
• How can I omit this "error window" without being pressing the "OK" button?

Thank you in advance for everything.

Attached Files

•  Save Bible File .bblx - Test.jpg   134.84K   8 downloads

[patchworkid]

Hi

try using Shift+Return which will give you a soft break instead of Return which is a full or complete break.

Thanks

[JPG]

Jon - No.

 

The Spanish option here is only for CREATING tooltips.  When a BBLX file is read in, English names are used.  If the Abbreviations are not being recognized, that is an issue with the Abbreviation list in use.

 

BH

 

Brent, could you do one practical test along with me. Set the option to Spanish and read in a bblx file that contains the 66 Bible books. I get them with errors G?n N?m G?l  etc Whereas setting to English does not have the issue.

 

Jon

[BH.]

I see the issue Jon and it is a UTF-8/Ansi encoding issue and I have a simple fix where the book name is inserted into the display.  What I don't see is where in my code the English and Spanish names are being switched, but clearly they are!  ...  found it. 

 

I have fixed the issue in reading BBLX file, but I'm sure there are issues in other places such as reading CMTX and NOTX files.  

[BH.]

Update, T4 v2.39 posted.