[sword-devel] NASB Lexicons

anthony kerr anton_kylie at pacific.net.au
Wed Jul 21 04:53:17 MST 2004


I am not a hebrew expert, but am studying Hebrew in 2nd year of college.

Using Bibletime CVS, and in fact most KDE apps since a recent upgrade, and 
using SIL Ezra unicode Font my Hebrew Module shows final kaf perfectly.

I put a small screen shot up on my server at 
http://www.jesuscentral.net/images/snapshot1.jpg - this is the latest hebrew 
module WLC.

I think the trick was QT being able to read the OpenType features of the SIL 
Ezra font. I think that most people who do Hebrew are sticklers for detail, 
(you have to be to get all the pointing right) therefore it would be best to 
encode things correctly and let the window managers sort it out. That is my 
perspective anyway, for what its worth.

I am not really in the right frame of mind to fully follow all of the 
codepoint stuff at the moment because my wife gave birth to our first child 
yesterday and God has blessed with a lovely little daughter.

But feel free to email me in the next few days if what I said above isn't of 
any help.

in Christ
anthony kerr

On Wed, 21 Jul 2004 11:21 am, David wrote:
> The only remaining problems with the NASB is to have someone more qualified
> than myself to examine the conversions from the Hebrew, and Greek fonts to
> unicode. There 79 characters used in the Greek lexicon, and 88 used in the
> Hebrew. Many of those are alphabetic, or are very distinct in appearance
> and easily checked. In some cases there are multiple characters with very
> close to the same appearance. This is what mainly needs to be checked.
> Other than that I believe that all problems with the lexicons have been
> handled.
> There some problems that could not be fixed. There is a precomposed
> character in the original font (74) Final Kaf with a character that appears
> something like Sheva, except aligns within Final Kaf instead of below, the
> character does not exist in the unicode specification alone, or precomposed
> with Final Kaf. Instead of deleting the character I replaced it with Sof
> Pasuq, it probably will not make much difference to people that can't read
> Hebrew, and people who do will probably realize there is a problem, and
> since Sof Pasuq appears similar to the missing character it may help them
> realize what the problem is.
> The multiple entries for a number have been handled by keeping them in one
> entry, and adding seperate entries for each subentry. As Troy, and Chris
> both suggested. Although I am not sure if there was any final decision on
> it.
> 00112:
> 112a.
> 112b.
> 00112a:
> 112a.
> 00112b:
> 112b.
> If anyone has any ideas of how to handle the Final Kaf problem in a better
> way, or wants to check the conversion routines let me know.
> David
> _______________________________________________
> sword-devel mailing list
> sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel

More information about the sword-devel mailing list