6 replies to this topic

[ebulerdo]

Hi All

I'd like to share something that I found. Maybe it's useful for someone, and maybe someone else can throw more light on it.

Recently I noticed some of my Hebrew dictionaries (I made them myself, not from this forum) show the Hebrew text in the wrong direction, that is, left to right.

When I tried an older version of those same dictionaries, the Hebrew letters were ok, right to left. But when I compared the text from the older and newer versions, they were the same codes in the same order. I used this kind of format:
{\f2 \'e0\'c8\'e1}

All the settings in the old and the new file were exactly the same, but if I copied the text from the old version and pasted it in the newer module, the Hebrew text was inverted.

Then I realized the difference: in the Details table, the value of the Version field in the old files was "2", while in the newer files I had put "3". I always thought this field contained just a module version, for updating purposes. But it seems it's something entirely different. I tried replacing "3" with "2.2", and now all the Hebrew text is displaying correctly.

Can somebody explain what the Version settings really is for?

Thanks!

[ebulerdo]

More information.

I wrote to Rick Meyers regarding this and his answer was:

Version should only be 3 if images are embedded, otherwise leave it empty or set it to 2.

So Version contains some internal RTF specifications versions, rather than a module version.

That implies that, unless corrected, you cannot have a dictionary with images and Hebrew text at the same time.

Regards,

Carlos

[Josh Bond]

More information.

I wrote to Rick Meyers regarding this and his answer was:

Version should only be 3 if images are embedded, otherwise leave it empty or set it to 2.

So Version contains some internal RTF specifications versions, rather than a module version.

That implies that, unless corrected, you cannot have a dictionary with images and Hebrew text at the same time.

Regards,

Carlos

You also have to use version 3 if you have hyperlinks/bookmarks embedded.

[jonathon]

I tried replacing "3" with "2.2", and now all the Hebrew text is displaying correctly.

Are you using "2", or "2.2" for Hebrew?

My impression was that the version number was supposed to be an integer.
I know. SQLite and error trapping/data verification are mutually exclusive concepts.
Still, I'd be surprised if e-Sword allowed a real number there.

jonathon

[ebulerdo]

Hi Jonathon

Are you using "2", or "2.2" for Hebrew?

I changed to 2.2 because I still thought it was a version number, and it works. I think e-Sword ignores anything you have written there unless it's a "3".

Regards,

Carlos

[BH.]

The purpose of the version number has to do with what display engine e-Sword will use for a given resource. If the version=3, then e-Sword will load the "Text Control" display engine. One downside of "Text Control" is that it is not fully right-to-left capable. Changing formatting mid-sentence will cause Hebrew characters to shift position. This can easily be demonstrated in e-Sword. Open Strongs dictionary, Select a entry, say H52 which has two Hebrew words, copy it to the clipboard and paste it into the Topics Editor. Select one work, and make it Italics. Oops. The underlying Unicode has not changed. But the position of the characters has changed drastically. What this shows, is that all formatting needs to be uniform when using Hebrew characters. All the characters in a paragraph should have the same formatting: color, italic, bold, size. Otherwise, you will get shifts in character position with "Text Control".

Attached is a sample image. The two lines of text are identical. The RTF for each line is identical except that one word is underlined in the upper word. Changing the formatting shuffles the words. Therefore, when using Hebrew text, one needs to keep the formatting uniform.

Attached Files

•  Hebrew TC.png   15.29K   0 downloads

[Josh Bond]

The purpose of the version number has to do with what display engine e-Sword will use for a given resource. If the version=3, then e-Sword will load the "Text Control" display engine. One downside of "Text Control" is that it is not fully right-to-left capable. Changing formatting mid-sentence will cause Hebrew characters to shift position. This can easily be demonstrated in e-Sword. Open Strongs dictionary, Select a entry, say H52 which has two Hebrew words, copy it to the clipboard and paste it into the Topics Editor. Select one work, and make it Italics. Oops. The underlying Unicode has not changed. But the position of the characters has changed drastically. What this shows, is that all formatting needs to be uniform when using Hebrew characters. All the characters in a paragraph should have the same formatting: color, italic, bold, size. Otherwise, you will get shifts in character position with "Text Control".

Attached is a sample image. The two lines of text are identical. The RTF for each line is identical except that one word is underlined in the upper word. Changing the formatting shuffles the words. Therefore, when using Hebrew text, one needs to keep the formatting uniform.

Yeah, I remember this bug in the control that e-Sword and T4 uses. You reported it. They acknowledged it was a bug. Then later, someone else reported it in their forums, and they denied it was a bug. Or maybe I'm getting that mixed up with another bug in the control. Errr, I'm sure all the bugs will be fixed "soon".