75 replies to this topic

[JPG]

Whilst you are testing can you check that you can search the Greek of the text.

Jon

[BH.]

Whilst you are testing can you check that you can search the Greek of the text.

Jon

I can search Greek in T4. Whether e-Sword can search it is another matter. Do you have any insight to share?

[JPG]

I can search Greek in T4. Whether e-Sword can search it is another matter. Do you have any insight to share?

Talking to Ray, a while back, and he figured that e-S needs the \'xx format to search the \uxxxx? won't work.
One of the aforementioned test [module] builds did search Greek but only if partial matching was selected.

Jon

Edited by JPG, 17 July 2012 - 01:07 PM.

[Searcher]

Next iteration of T4 will have a tool to run before running the Greek tool which will reset EVERYTHING to a known state, then run the Greek tool. I'm actually testing it now on your original file right now. Once that version of T4 is posted, you can be the guinea pig and run it on your system. There may be something about your system that does not work the same as mine - - who knows? So it will be informative if you indeed can reproduce a good BBLX.

Great! I look forward to it. I have several more texts that I would like to try it on, including some Greek-Spanish. Thanx!!!

[Searcher]

Talking to Ray, a while back, and he figured that e-S needs the \'xx format to search the \uxxxx? won't work.
One of the aforementioned test [module] builds did search Greek but only if partial matching was selected.

Jon

To be able to search for Greek would be very helpful. Strong's numbers do not cover the full range of Greek words found in the Septuagint [LXX], and a Greek-English interlinear of the LXX is much longed for. Either that, or a new numbering system that will account for the nearly 10,000 Greek words in the LXX vocabulary.

[jonathon]

To be able to search for Greek would be very helpful.

Before my backup drives failed, I had a script that could search user created e-Sword resources, regardless of language and writing system.

I've forgotten the specifics of what I did, but the general algorithm included both glyph substitution, and converting between various character encodings.


jonathon

[BH.]

========================================
Version 1.28- 7/20/2012
========================================
-- New - progress bars for unicode "fixups".
-- Fixed - APL385.TTF font is not installed and install script does not give error feedback. T4 will now check to see if the font is installed, and if not, will show the font preview and give the option to then install it at that time. This only needs to be done once. This font is used for error messages and for Unicode "fixups".

[Searcher]

BH,

Many thanx for your useful updates. I can report partial success. I have attached section 3 of the interlinear to illustrate what is happening.

To create the file, I used the following steps within T4. First I ran the Strong's Numbers Fixup tool. That was followed by the Unicode Greek fixup tool. And then by the Reset ALL Character tool. After that I created the module. Some of the text came out just fine (see Romans chapter 8) and some just as before (see Romans chapters 1-7). I tried changing the font size within e-Sword, but to no effect.

After running the Reset ALL Chars, I observed that there was not uniform line spacing. The line spacing in the areas I checked were set to 13 points, but it resulted in part of the bottom of the characters being truncated. So I selected all, and set line spacing to single.

I might also mention that when the Strong's number tool is run, upon completion it selects (highlights) the first Strong's number of the file. If I forget to unselect it and immediately run the Greek Unicode Char fixup it assumes that it should only do its job within the selected text. Not really a problem, just a minor irritation (with myself for forgetting).

Max
 Interlinear1.zip   1.72MB   7 downloads

[BH.]

First, I would run the fixup tools in the order in which they appear in the menus. Reset ALL first. Note the word ALL! Then run the Greek tool and Strong numbers.

As for spacing, when the module is written, with "Font Size set by e-Sword" checked as it should be, the line spacing will be taken care of by e-Sword.

When viewed in e-Sword, I do not see any issues with your BBLX file. So where is the partial success? Or should I ask, where is the partial failure??? :-)

[JPG]

I see what Searcher is seeing.
Brent, if you look in the module at the rtf codes for the English for example you see that sometimes it is \f0 and others \f1
Easy to see if you have different fonts set for default and Greek.




Jon