68 replies to this topic

[Josh Bond]

Ephesians 5:26 is acting like the text is Hebrew. I can override it to the Koine Font which makes it render in Greek. And yeah, in your file description, we should probably say the Koine font is required and add that as a download as well.

I will fix all verses like Ephesians 5:26 now...

There's also some problems in the Book comments area. I'll look at that too.

Edited by Josh Bond, 09 October 2011 - 05:40 PM.

[pfpeller]

THere are quite a few other verses scattered throughout like Eph 5:26...

Man, this file is difficult!

[Josh Bond]

Does the original text have Hebrew characters in it?

Nevermind, I see what it is.

Edited by Josh Bond, 09 October 2011 - 05:55 PM.

[Josh Bond]

This is like the Who Wants to be a Millionaire show. They would always say: Final answer? I hope this is the final answer to this one!

The attached zip has the (again) revised commentary, the Greek font, and the Hebrew font. Both fonts are necessary to view the file.

Attached Files

•  eadie.zip   1.59MB   5 downloads

[BH.]

I got a full night of sleep. I tried this one more time. This time what I did in T3 is take all the fonts, except f0, and move them up 20. So, f1 become f21, f2 -> f22, etc. I rebuilt the file and except for the spacing with diacritics, the file looks OK. Perhaps that is the solution?

Edited by BH., 11 October 2011 - 09:49 AM.

[Josh Bond]

Sure, sounds good to me. I kept toying with Peter's commentary until everything displayed properly. Your automatic fix will sure beat editing the database manually. Hopefully this situation will not arise very often as I'm not sure its a "best practice" for e-Sword module building. Thanks for revisiting it.

Josh

[jonathon]

This type of thing isn't well documented. And in a future version of e-Sword, if Rick disallows the use of RTF headers in commentaries, which I'm using to make the font display properly, people will have to use other software to view this commentary.

Not "if", but "when".

I would not be able to get it to work. So in that sense, this commentary is "fragile".

You are doing things with e-Sword that Rick neither anticipated, or envisioned.

jonathon

[BH.]

Not "if", but "when".



You are doing things with e-Sword that Rick neither anticipated, or envisioned.

jonathon

All that has been leveraged here is embedding RTF code with in RTF code. Most RTF rendering engines that I have used accept this. This appears also to be true in e-Sword as far as rendering. It may not work if you try to copy and paste the data out of e-Sword. The disadvantage of this is that is breaks the standard fonts. The advantage is that it is not bound by the standard fonts. It puts a burden on the module creator to assure everything displays correctly, meaning the installation and distribution of fonts. Is it best practice? I do not recommend it. What has been done here has been done with full disclosure, nothing is secret. As Jesus said in John 18:20 AKJV Jesus answered him, I spoke openly to the world; I ever taught in the synagogue, and in the temple, where the Jews always resort; and in secret have I said nothing.

Edited by BH., 28 October 2011 - 01:38 PM.

[SpreadTheWord]

Not "if", but "when".

jonathon

I don't think so. e-Sword 10 shows e-Swords compliance with rtfeven better. The Reference Library's rtf control is an official item from Microsoft... So if anything, e-Sword seems to be embracing the RTF standard instead of moving away from it.

Edited by SpreadTheWord, 28 October 2011 - 02:42 PM.