ebulerdo

Hi Gilbert

I found the text and prepared your Bible module. The text was in a very easy to import format, so it didn't take long.

I removed all the vowels and other diacritics, so it can now be searched correctly. Also, in this module the font is correctly set as Arabic (in the official one it's wrongly identified as Hebrew) so you can change the appearance of the text using the Arabic Font option.

What do you think would be the best name and abbreviation for this module? Maybe "SVD-"?

Carlos

Hi Jonathon

However, based upon the questions/comments/etc I've been reading, people stick with 8.x, or 7.x for one of the following reasons:

• Resources that they have been unable to migrate to a new version;
• Accessibility related issues;
• Specific functionality in the version they used, that was removed in later versions;

You didn't mention some other reasons:

• People thinking upgrading is a very difficult technical process.
• Plain laziness.

These are the ones I meet most. :-)

Regards,

Carlos

Hi DoctorDaveT

I'm thinking about these guys on the front lines, translating their Bibles into languages that have characters not found in TITUS Cyberbit Basic. How should they proceed if eSword's rtf header system is going to block their work?

In the Options - Fonts menu you can select specific fonts for a good number of scripts.

In the case I was telling I needed some special characters that do not belong to any of those languages, and we even ordered a font from a font-maker in order to display them. I contacted Rick and he has just answered that Bibles will now have special unicode support. If I got it right, when a character is not present in your default font, it will display it using the best font available. I have seen Microsoft Word does something similar.

That improvement is not available yet, but I think it can work very well.

Carlos

Hi Patchworkid

hi sorry, but what is exactly rtf heading?  i need to know  what it is ?

E-Sword modules are written in a format named RTF (Rich Text Format). This format is basically text, with some special tags for format. For instance, if you want to display a word in bold text, you use {\b I'm bold}. If you want to display it in italics, you use \i. Bible references have the format {\cf11\ul Gen_1:1} where \cf11 means green and \ul means underlined. And so on.

An RTF text always begins with a header where you estate the fonts you will be using, the character table, colors and some other details.

E-Sword supplies that header by default, so you don't need to put a header in every verse or in every entry in your module. However, some modules have a header of their own because they require a specific font. That used to work fine in e-Sword until v10.0.2, but in 10.0.3 a new specification was adopted that no longer allows this. So modules that contain their own RTF header didn't display any text. Most of them were commentaries, that's the reason why so many people complained their commentaries were no longer working.

Rick resolved this situation by instructing e-Sword not to apply its header if the module already had one. And this patch works fine with most modules, except with bibles.

And this is the point where we are now. :-) I'm sure Rick will come across with a solution.

I hope this was understandable. O:-)

Carlos

Hi DSaw

Romanian uses the Latin alphabet, with five special characters with diacritics. E-Sword supports Romanian perfectly, and there are already some Romanian Bible modules around.

But the way T3 handles foreign characters makes it unsuitable for Romanian. You need to use a different software, or build the module with T3, then dump it to text, replace the codes for the special characters, and then reimport it. It's the same process for Spanish or any other language that uses any non-English character. It sounds more difficult than it really is.

Regards,

Carlos

Hi

A very good alternative to Omnipage is ABBYY Finereader. I use both Omnipage 16 and Finereader 10 at work, and the results are very similar, but I find Finereader a bit easier to use.

Finereader 11 can be bought new for around 150$. Surely it can be cheaper in Amazon or somewhere else.

Hi

If you are using e-Sword 9 (most likely), you can open old .top files. Go to topic notes editor - menu Open - and in the filetype box select "Old Topic Notes Files". It will convert your file to the latest version (.topx) and ope it.

Regards

Carlos

Hi Brent and group

At last I have learnt how to prepare a Bible module using Tooltip Tool 3.23.

However, I have noticed there's a problem with Spanish special characters. Maybe it's related to the fact Brent mentioned that T3 doesn't work in Unicode.

This is the sample text I'm importing:

#define abbreviation=TEST
#define description=TEST
#define comments=TEST
#define font=DEFAULT
#define ot=1
#define nt=0
#define apocrypha=0
#define strong=0
#define version=1

÷[Gen]
1:1  En el principio creó Dios los cielos y la tierra.
1:2  Y la tierra estaba desordenada y vacía, y las tinieblas estaban sobre la faz del abismo, y el Espíritu de Dios se movía sobre la faz de las aguas.
1:3  Y dijo Dios: Sea la luz; y fue la luz.
1:4  Y vio Dios que la luz era buena; y separó Dios la luz de las tinieblas.
1:5  Y llamó Dios a la luz Día, y a las tinieblas llamó Noche. Y fue la tarde y la mañana un día.

I save that as a .bblx file and I get no error messages. Now when I open my module with e-Sword, all the special characters (áéíóúñ) are gone:

Gén 1:1 En el principio cre Dios los cielos y la tierra.
Gén 1:2 Y la tierra estaba desordenada y vaca, y las tinieblas estaban sobre la faz del abismo, y el Espritu de Dios se mova sobre la faz de las aguas.
Gén 1:3 Y dijo Dios: Sea la luz; y fue la luz.
Gén 1:4 Y vio Dios que la luz era buena; y separ Dios la luz de las tinieblas.
Gén 1:5 Y llam Dios a la luz Da, y a las tinieblas llam Noche. Y fue la tarde y la maana un da.

When I open the module with SQLite Manager, I see the accented letters have been replaced by weird characters:

1 1 1 1 En el principio cre¢ Dios los cielos y la tierra.
2 1 1 2 Y la tierra estaba desordenada y vac¡a, y las tinieblas estaban sobre la faz del abismo, y el Esp¡ritu de Dios se mov¡a sobre la faz de las aguas.
3 1 1 3 Y dijo Dios: Sea la luz; y fue la luz.
4 1 1 4 Y vio Dios que la luz era buena; y separ¢ Dios la luz de las tinieblas.
5 1 1 5 Y llam¢ Dios a la luz D¡a, y a las tinieblas llam¢ Noche. Y fue la tarde y la ma¤ana un d¡a.

Do you see the funny ¢ ¡ ¤ symbols? I have tried using both ANSI and UTF8 text. Is there an option to fix this? Or if not, could it please be fixed in a future version? As it is now, it's not usable to build modules in Spanish. :-(

Thank you!

Carlos

Hi Patchworkid

Thank you very much for this thread. It covers a lot of info that is not in the documentation yet.

I would like to make a small correction regarding Bibles:

Bible Module

#define font=DEFAULT
#define ot=1
#define nt=1
#define apocrypha=0
#define strong=0
#define version=1

÷[Gen] The First Book of Moses:  Called Genesis
1:1 In the beginning God created the heaven and the earth. [...]

There are some variables missing there. After a lot of trial and error, I can say the complete header would be like this:

#define abbreviation=XXX
#define description=XXX
#define comments=XXX
#define font=DEFAULT
#define ot=1
#define nt=1
#define apocrypha=0
#define strong=0
#define version=1

Also, the ÷ mark is needed only once at the beginning of the text. I was using it for every book, but that's not OK.

Regards,

Carlos