Jump to content

Please read the Forum Rules before posting.

Photo
- - - - -

Multiple problems with Hebrew / Aramaic Text Handling


5 replies to this topic

#1 Toma

Toma

    e-Sword Addict

  • Veterans
  • PipPipPipPip
  • 64 posts
Offline

Posted 14 February 2020 - 02:58 AM

Great day all.  I'm using e-Sword 10.4.0, and I create e-Sword modules using e-Sword ToolTip Tool NT v1.29

My problems are as follows.

 

#1) Hebrew words and sentences show up properly in e-Sword *unless* they have any English punctuation, such as commas, periods, or quotation marks.  In those cases, the Hebrew text gets mangled.  Why, and how to fix?

 

#2) Estrangelo font copies fine into ToolTip Tool NT from other programs, but when rendered into e-Sword, it appears completely backwards.

 

#3) Is there anyway to insert images into a Commentary or Dictionary file?  I've never found a way to do so up until this point, over the years.  If so, how please?

 

Thank you so much for the help.

Attached Files



#2 kiwi

kiwi

    Liking e-Sword

  • Members
  • PipPip
  • 23 posts
Offline

Posted 18 February 2020 - 12:05 AM

Great day all.  I'm using e-Sword 10.4.0, and I create e-Sword modules using e-Sword ToolTip Tool NT v1.29

My problems are as follows.

 

#1) Hebrew words and sentences show up properly in e-Sword *unless* they have any English punctuation, such as commas, periods, or quotation marks.  In those cases, the Hebrew text gets mangled.  Why, and how to fix?

 

#2) Estrangelo font copies fine into ToolTip Tool NT from other programs, but when rendered into e-Sword, it appears completely backwards.

 

#3) Is there anyway to insert images into a Commentary or Dictionary file?  I've never found a way to do so up until this point, over the years.  If so, how please?

 

Thank you so much for the help.

 

>Hebrew words and sentences show up properly in e-Sword *unless* they have any English punctuation, such as commas, periods, or quotation marks.  In those cases, the Hebrew text gets mangled.  Why, and how to fix?

 

Either use Hebrew punctuation, or before and after each English punctuation mark, put the appropriate right-to-left or left-to-right indicator.

<dir="ltr" lang="en">.<html dir="rtl" lang="he">אבג<dir="ltr" lang="en">

If I remember my html presentation markup correctly.

 

Unicode Ux200F & Ux200E are the glyphs to use for UTF-8.

 

 

 

 

 

>Estrangelo font copies fine into ToolTip Tool NT from other programs, but when rendered into e-Sword, it appears completely backwards.

What happens when you use the SIL Hebrew fonts?

 

>Is there anyway to insert images into a Commentary or Dictionary file?  I've never found a way to do so up until this point, over the years.  If so, how please?

 

In theory, yes. In practice, probably not. 

 

There is some documentation from early versions of e-Sword floating around, that describes how to include both images, and audio files in e-Sword modules. It required performing black magic on the RTF within the e-Sword module.

 

That said, what happens when you include

<img src="example.png" alt="Example" width="128" height="128">

in your markup?
 

 

 

 

 

 

 

 

 

 



#3 agsper652

agsper652

    New to Bible Support

  • Veterans
  • Pip
  • 12 posts
Offline

Posted 08 July 2020 - 11:37 AM

In working with bidirectional text modules, I have noted that the right-to-left (RTL) text needs to be separated from the LTR text.  So parentheses around a Hebrew word in a dictionary file like BDB may look like this in html:  (<heb>...</heb>).  In my computer (Win7), the font I choose in e-Sword does not show up on screen unless I use the wrong encoding, so I do it like this:  (<span dir=LTR><heb>...</heb></span>).  I would assume the same is needed in Syriac / Aramaic.



#4 Tj Higgins

Tj Higgins

    e-Sword Fanatic

  • Members
  • PipPipPipPipPip
  • 785 posts
Offline

Posted 08 July 2020 - 02:05 PM

In working with bidirectional text modules, I have noted that the right-to-left (RTL) text needs to be separated from the LTR text.  So parentheses around a Hebrew word in a dictionary file like BDB may look like this in html:  (<heb>...</heb>).  In my computer (Win7), the font I choose in e-Sword does not show up on screen unless I use the wrong encoding, so I do it like this:  (<span dir=LTR><heb>...</heb></span>).  I would assume the same is needed in Syriac / Aramaic.

The font for Hebrew in e-Sword is Titus Cyberbit Basic, this also the font to use for Greek and Latin words 



#5 agsper652

agsper652

    New to Bible Support

  • Veterans
  • Pip
  • 12 posts
Offline

Posted 15 July 2020 - 05:13 PM

The font I use for Hebrew is Ezra from SIL.org.  It will not display in my Hebrew-containing modules.bbli on my Win7 PC unless the Hebrew is encased in <span dir=LTR><heb>...</heb></span> as mentioned above.  I love Titus Cyberbit Basic for Greek, but the pointings do not display well for Hebrew.  FreeSerif works well and SBLHebrew, though these are somewhat smaller fonts than Ezra.  In e-Sword 12.x under Options one can select the font for Hebrew separately from Greek, but it does not work on my computer unless I have the Hebrew words in the html tags as mentioned.  Without those tags, I can select FreeSerif and it will work, but not Ezra.  Also without those tags the Parallel mode does not display correctly.  Normally in html the correct tag for Hebrew would be <span dir=RTL> but in e-Sword 12.x I need to use the <span dir=LTR> tag, apparently to overcome something in the program's CSS.  I have an Iphone 8 and my <span dir=LTR><heb>...</heb></span> tagged module works fine there in e-Sword-LT,



#6 JPG

JPG

    Bug Hunter

  • Moderators
  • 1,076 posts
Online

Posted 16 July 2020 - 02:34 AM

I contacted the developer in 2016 about the issue in e-Sword for PC.

reply to part of this is....

 

* The display control seems to have a mind of its own in the rendering of right-to-left languages.  It is being told to use the correct font, but it is not doing so.  I cannot fix what I didn't write.

 

I suppose you would need to hard code your font name in the text to get round this. Unless there is an update to the TX Text Control used.

 

Jon





Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users




Similar Topics



Latest Blogs