Major flaw in Qumran Biblical Dead Sea Scrolls Database

Hi All,

I have downloaded and installed the Qumran Biblical Dead Sea Scrolls Database and realized with shock there is a major flaw in the resource. The developers did not make a distinction between the 'square Hebrew' characters (יהוה) and paleo-Hebrew characters used for the Tetragrammaton. Therefore the Qumran Biblical Dead Sea Scrolls Database is not a true representation of the 'original' manuscripts.

It is strongly suggested that this is rectified to do justice to these extremely valuable resources.

Regards,

Peter

Find more posts tagged with

Comments

Vincent Setterholm

Our files have this data and we plan to add that in the future. We didn't have a paleo-Hebrew font that could handle the combining diacriticals used to mark the certainty/uncertainty of the reconstruction. (I think there was another minor issue related to how to handle analyzed words that are in mixed script - like the tetragrammaton with an ending in the square script.) In any event, when we have a working font, we'll add this feature back in.

Peter Nagel

https://community.logos.com/discussion/comment/228398#Comment_228398

Hi Vincent,

thanks for the swift response. Why couldn't Logos use the LbxPaleoHebrew font made available with Libronix 3? This works like a charm...:

1.) Choose LbxPaleoHebrew font;

2.) Change input language to Hebrew;

3.) When typing the paleo Hebrew characters appear;

4.) It is a truly authentic font.

This is truly a significant distinction in some DSS manuscripts, that truly requires urgent rectifying. As you know Logos' competitor has this resource available with the 'correct' manuscript reading in this instance; in addition to this there is a Paleo-Hebrew font made available by Logos which could have been used?

Moreover, there is no indication whatsoever below the Information tab that the manuscript read paleo-hebrew characters. In fact the information supplied is a mere replica of the Tetragrammaton reading in the BHS. I am not satisfied at all, I have been waiting 4 years for this release, rejecting other options to work with this resource digitally, just to find it not to be a true representation of the DSS manuscripts on this pivotal issue?

This, to my opinion, should not be regarded as a 'adding' this feature. This is no feature, it is part and parcel of the original manuscripts. The variations was indeed noted and presented digitally with the Qumran Sectarian Manuscripts?

Thanks

Peter

Vincent Setterholm

https://community.logos.com/discussion/comment/228408#Comment_228408

Why couldn't Logos use the LbxPaleoHebrew font made available with Libronix 3?

LbxPaleoHebrew doesn't support the combining diacritical marks needed. Adding support for those marks in LbxPaleoHebrew is one of the options we're looking into. We'll get this sorted out, we just didn't want to delay getting these materials into your hands while we resolve font issues.

Peter Nagel

https://community.logos.com/discussion/comment/228419#Comment_228419

Dear Vincent,

again, thanks for the feedback. I do appreciate the fact that you are in the process in resolving this.

All the best!

Peter

WAM Project

https://community.logos.com/discussion/comment/228436#Comment_228436

Where does this issue stand at this time????

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/364175#Comment_364175

Looking in my Logos library, noticed last update for Qumran Biblical Dead Sea Scrolls Database was 7 Mar 2011, hence likewise curious about an update plus wonder about potential future compatibility with Hebrew audio pronunciation ?

Keep Smiling [:)]

Martin Grainger Dean

https://community.logos.com/discussion/comment/364221#Comment_364221

The developers did not make a distinction between the 'square Hebrew' characters (יהוה) and paleo-Hebrew characters used for the Tetragrammaton. Therefore the Qumran Biblical Dead Sea Scrolls Database is not a true representation of the 'original' manuscripts.

It is strongly suggested that this is rectified to do justice to these extremely valuable resources.

Hi Logos. What's the status of this issue? Martin.

Martin Grainger Dean

https://community.logos.com/discussion/comment/434982#Comment_434982

Bump.

Martin Grainger Dean

https://community.logos.com/discussion/comment/438080#Comment_438080

No answer from Logos? Martin.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/434982#Comment_434982

Hi Logos. What's the status of this issue? Martin.

As per Vince's original post (http://community.logos.com/forums/p/30816/228398.aspx#228398), we don't have a paleo-Hebrew font that supports combining diacriticals. There is no updated status.

Todd Phillips

https://community.logos.com/discussion/comment/439949#Comment_439949

Hi Logos. What's the status of this issue? Martin.

As per Vince's original post (http://community.logos.com/forums/p/30816/228398.aspx#228398), we don't have a paleo-Hebrew font that supports combining diacriticals. There is no updated status.

Does that mean it's not being worked on? It's been over a year and 8 months since Vince said "We'll get this sorted out".

David Paul

https://community.logos.com/discussion/comment/439976#Comment_439976

Why would "combining diacriticals" (do you mean niqquudh of some sort?) need to be used with Paleo-Hebrew? Is that something that is found in the DSS? It seems like it would be completely anachronistic to mesh these two things.