373 replies to this topic

[ebulerdo]

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

[DoctorDaveT]

About the RTF headers and Bible fonts:

so, all of the special characters that should be used must be found within the TITUS Cyberbit Basic?

[BH.]

About the RTF headers and Bible fonts:

so, all of the special characters that should be used must be found within the TITUS Cyberbit Basic?

Or change your default font to one that works with your project, understanding that that will affect everything else.

[DoctorDaveT]

Hey, BH,

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?

[DSaw]

My understanding of Unicode is this

almost every font follows a standard called Unicode each character is assigned a number all the fonts that carry that character say an "A" will have an A so when you switch fonts the A stays an A even though they may look a little differently

But not every font carries every character if you want Greek You have to select a font that carries Greek when you use a font that does not carry that character you will get a box

If I'm understanding correctly the problem comes when special fonts that dont follow the standard are used that need to be sent with the module and have to have an RTF header to basically to tell eSword to use this font at these places in the text and with eSword now not allowing headers we get garbage

So TITUS cyberbit basic seems to be the one font that contains the most EXTRA characters and would be the font use for Greek Hebrew
but the other languages that TITUS does not carry there are language type selections in eSword but they to do not cover all languages

My knowledge on this is not 100% so please feel free to add or refute comments


I seem to be repeating myself But A published standard for eSword modules would be very Helpful

[God's Prayer Warrior]

Josh,

Thanks for the reply and thanks for the pic to show me what the Permissions should look like.
As I said to you in my previous post, my Permissions already look like that. I even got my landlord, who is an IT expert to have a look at it to confirm that I am looking at the right thing, and he confirms it.
He also can't find the fault. He even downloaded eSword version 10.03 to see for himself.

[ebulerdo]

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

[patchworkid]

Hi Do you think it will be in 10.05 version?

thanks

[Michael Arnold]

I'm new to e-Sword so I am just starting to get around in it and download some resources. I have 9.9.1. Can I install 10.0.4 without causing any problems? I mean with the modules that I have installed.

[dyan]

Hi Michael,

Welcome to Biblesupport.

There won't be a problem with any modules after installing e-Sword ver. 10.0.4, but I would suggest you wait for e-Sword ver. 10.0.5, which is due for release today/tomorrow 11.11.2011.
It (most probably) is the final version.