7 replies to this topic

[oakleaf1]

Having a problem tooltipping a commentary. The verse references look like this when opened in e-Sword:
Gen 1:1<ref:Gen.1.1>
The Gen 1:1 works to pop up the verse reference but how do I get the unnecessary <ref:Gen.1.1> to not show up?

[patchworkid]

Hi 

 

To help you, you will need to give a sample of your commentary mainly gen chapter 1. Then someone will be able to help you more clearly.

 

thanks

[oakleaf1]

The commentary is on the Gospel of John and had verse references within it including from Genesis. Strong's numbers unfortunately came out similarly as verse references. Here is a partial of John 1:1 using copy and paste from e-Sword which loses the complete underlines under the verse references and Strong's numbers. The "<num:G3056>" and "<ref:Gen.1.1>" and similar should not be visible, which is the problem.

Thanks for any help you can give!

 

John 1:1

 

This verse is a 3-step increasingly greater revelation of the "Word" G3056 <num:G3056>. First we see that He was in the beginning, then we are shown that He was with God, and lastly that He is God. It speaks of the Word’s eternity in three different aspects: 

1. eternal existence = "In the beginning was the Word" 

2. eternal position = "and the Word was with God" 

3. eternal identity = "and the Word was God." 

"In the beginning" sounds like Gen_1:1 <ref:Gen.1.1> which speaks of the beginning of the old creation. The Word came to earth to begin a new creation 2Co_5:17 <ref:2Co.5.17>. 

"beginning" can have 2 meanings: 

1. in the beginning of history. In that case, this would mean that the Word always was. Rev_1:8 <ref:Rev.1.8> 

2. at the root of the universe, which would make this mean that all things depend eternally upon the Word. Col_1:17 <ref:Col.1.17> 

"In the beginning the Word already was" is the correct translation of the tense of the verb "to be." 

[DSaw]

Hi 

 

It seems that the source file was designed for or exported from a bible program that needs the references set up like <ref:Col.1.17> but this is not needed in esword 

 

in the source file everything between and the marks and the marks themselves <> need to be deleted 

 

are You using tooltip tool to create the module T4 is a WYSIWYG (what you see is what you get) 

 

DSaw

[oakleaf1]

Hi

Actually the commentary was written in its most updated form in e-Sword HD on my iPad. However, since I cannot use tooltips on my iPad I copied each verse and emailed it to myself so I could receive it on my IBM type computer and then use tooltips on it. The marks <> and what is between them is not visible in the source file. I also have those notes (verse by verse commentary) available in an older form without all the updates in a Microsoft Word document and in a program I originally did them in on the IBM type computer called Online Bible.

[patchworkid]

hi

 

Open the file in micro soft Word 

click on find and replace

click on more and click on Wild cards 

type this on

Find:  (\<*\>)

Replace:  (Keep Blank)

 

This will remove all your <ref: scripture references>

make sure you make a back up before you do this process

 

thanks 

[oakleaf1]

Thanks for the information. I will certainly try that! It seems the formatting comes from e-Sword HD since that is where I added the Strong's numbers and they have the same problem as the verse references.

[APsit190]

Thanks for the information. I will certainly try that! It seems the formatting comes from e-Sword HD since that is where I added the Strong's numbers and they have the same problem as the verse references.

 

Files used by the Topic Note, Study Note and etc Editors are compatible right across all Apple's OS X and iOS platforms, and therefore irrespective of which e-Sword type is running on any of Apple's devices, there are no conflicts in the formatting in the resource files. Therefore, Strong's Numbers read on e-Sword HD, is read the same way on e-Sword LT and e-Sword X and so on. There is no difference.

 

Having said that, I think (theory only), that when it actually to the compilation (the actual exporting) of the file, it appears, or seems, you may be compiling of for e-Sword PC, and not for iOS/OS X.

 

I could be wrong, and its OK if you tell me that I am wrong. That said, just check out the file extension after compilation is completed to see if you got it for the right platform.

 

Blessings,

Edited by APsit190, 20 December 2015 - 02:51 PM.