14 replies to this topic

[StandingFirm]

I am also buiding a module. In some of the text the scripture is references such as "Rom. 3:8". In other cases it is referenced as "verses 10-12", meaning that it is in the same book and chapter as the previous reference. Will I have to change these to the full book, chapter, verse referece or can T3 figure it out? Thanks for your help.

Michael

[Josh Bond]

Unfortunately, no T3 cannot deduce implicit references. If you want verses 10-12 tooltipped, you will need to specify the full reference. But in some cases, that's just not plausible because of the size of a resource. I always try to do it (usually). But even some official e-Sword premium commentaries contain implicit references, presumably because it would have just taken too much time to make them explicit references. On a large resource, with thousands of these, it can take more time to make implicit references explicit than all other module making tasks combined.

[StandingFirm]

Thanks Josh. I appreciate your help. I kind of expected that might be the case.

[StandingFirm]

Just one more question regarding T3, When entering scripture references does it handle for example John 3:16, 17 as well as John 3:16-17? Is there a preference? Which works the best? Thanks again.

[Josh Bond]

T3 is very good at recognizing verses. That's the magic of T3. T3 is the best I've ever seen at parsing words to recognize scripture references even with odd punctation and ordering. The parsing and logic is world class and as always, my hat's off to Brent for making this utility.

Using the default abbreviations, T3 will recognize these and probably others:

• St John 3:16
• john 3.16
• joh 3:16
• joh3:16
• jo.3:16
• john 3:16, 18, 20-21.
• John 2:1; 3:16; 4:2

You can control which book abbreviations T3 recognizes by clicking the Abbr command from the main menu. You can use the internal T3 list or use the "external" T3 abbreviation list. By using the external list, you can edit the abbreviations. I strongly advise removing IS (for Isaiah) if your resource doesn't require it because it will lead to false hits. The same applies to SON (Song of Solomon).

T3 recognizes verse ranges like this: John 3:16-18. And also like this: John 3:16, 17, 18. And also like this John 2:1; 3:16; 4:2. Notice that T3 detects the implicit references in a comma or semicolon delimited list. But in the previous example, T3 does require semicolons when the chapter changes--commas if it's just a verse change.

If Option > V3 Tooltip Formatting is enabled, John 3 will become Joh_3:1-36. The entire chapter will be recognized.

One great tip I can share: I run a second instance of T3 to test how it detects references sometimes. I will think: Will T3 handle this correctly before I get too deep into this syntax? I can launch a second instance of T3 and test a sample right there. I recommend you do the same. Just be sure not to change the settings in the second instance of T3 because I don't think it will effect the first instance until you close and restart T3.

Another great tip: Click Options > Show Only Bad References in Lower Pane. This way, you can instantly see which verses did not tooltip--that usually means a syntax problem with the reference OR (more likely) the verse reference does not exist. You would be surprised at the number of mistakes and typos in older books. You can then click the "bad" reference in the lower pane and T3 will take you to that location in the text. That means, T3 "knows" the valid verse and chapter references for every book/chapter in the Bible.