68 replies to this topic

[BH.]

Yes, I think so, but I do not know Greek. I can send you theWord version if you like.

Hold on, I will compare to my source text.

Then if TheWord is showing the data correctly, then the issue is with e-Sword, no?

[pfpeller]

Yes, I would say it is with e sword. I crosschecked a verse in theWord with the source text and it appears to be fine with propper spacing.

[Josh Bond]

I can get it to work by manually editing Peter's cmtx file. If I tell you what I did, it will make you scream.

I opened Galations 1:1 in the database. I edited the RTF header and changed the font specification from f1 to f2. Then I changed the font designation in front of the greek text from f1 to f2. e-Sword apparently wants the font to be f2? Bizarre, but it works.

Edit: Let me add, maybe you cannot override the f1 font specification. But you can the f2 font specification? It's all in how Rick programmed it...

[BH.]

This is not a general fix unfortunately. What if there were multiple fonts? The KoineTT font may not be f1 or f2, but f5. So yes, AAAAAAAAHHHHH. :-)

[Josh Bond]

I haven't tested it, but I suspect f0 and f1 are protected. And maybe f2+ is not protected. If you want me to, rather than you continuing to modify your code, I can just search and replace this in Peter's commentary. This is getting crazy, lol.

[BH.]

Actually, f0-f13 are "protected"

⍝ F0 = Default
⍝ F1 = Greek (161)
⍝ F2 = Hebrew (177)
⍝ F3 = Latin (0)
⍝ F4 = Chinese(traditional) (136)
⍝ F5 = Cyrillic (204)
⍝ F6 = Eastern European (238)
⍝ F7 = Chinese(simplified) (134)
⍝ F8 = Thai (222)
⍝ F9 = Korean (129)
⍝ F10= Arabic (178)
⍝ F11= Turkish (162)
⍝ F12= Vietnamese (163)
⍝ F13= Japanese (128)

Edited by BH., 09 October 2011 - 04:49 PM.

[Josh Bond]

Yet, we're able to somehow override f2 at least, and possibly others that we haven't tried...

[BH.]

Yeah - but we are "violating" the way e-Sword puts together CMTX modules. I understand why e-Sword works the way it does. That way, you can change fonts, sizes, etc. But it would be nice to have CMTX modules work like TOPX/NOTX modules where we can specify the RTF entirely. I'm glad you can help Peter!! :-) I'll go back to playing with the next module type I started working on last night...

[Josh Bond]

Ok Peter, here's your commentary. The Greek text is showing in the right font now. And we don't fully understand why. 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. Under that scenario, I would not be able to get it to work. So in that sense, this commentary is "fragile".

 eadie - galations, collosioins.zip   1.54MB   6 downloads

[pfpeller]

Hey Josh and BH,
Thanks for all your help. This looks much better. There is still an occasional verse where the Greek does not show up, like Eph 5:26 for example. Should I just post as is?

I am assuming I need to post it with the font.
Thanks,
Peter