A proper aleph?

Just noticed yet another comma, instead of an aleph.

Is this an encoding issue on Logos' end? A font issue? Some resources have it correctly (and proper ayins, too!) and others do not. This is from Dictionary of Jesus and the Gospels.

Does this count as a typo? Should I be reporting them all?

Find more posts tagged with

Comments

MJ. Smith

Does this count as a typo? Should I be reporting them all?

yes and yes

Bradley Grainger (Logos)

Since it's a systemic issue, I'll file an internal bug report for this resource. (It should be U+02BE, not U+02D2.)

Dylan Rondeau

https://community.logos.com/discussion/comment/534653#Comment_534653

This should be fixed in the 2013-10-22 update to the resource.

Ben

https://community.logos.com/discussion/comment/542556#Comment_542556

Looks like this is a problem in the Word Biblical Commentary as well.

This from the Genesis 1 volume. (The arrows are mine, but look at the alephs in the right column.)

George Somsel

https://community.logos.com/discussion/comment/563266#Comment_563266

I'm afraid I don't understand you. What is a systemic problem with WBC? I'm looking at your example of Irad עירד and I note that the yod is a correct transliteration of the Hebrew while I thought you were referring to the transliteration of the aleph. Perhaps you can explain it more simply so I can understand.

Jack Caviness

https://community.logos.com/discussion/comment/563274#Comment_563274

I'm afraid I don't understand you

Believe he may have been referring to the transliteration of Methuselah

George Somsel

https://community.logos.com/discussion/comment/563283#Comment_563283

I'm afraid I don't understand you

Believe he may have been referring to the transliteration of Methuselah

That is also correct since it is different in cap 5 from cap 4.

Vincent Setterholm

https://community.logos.com/discussion/comment/563289#Comment_563289

Right, there was a period of time when our only transliteration font had used the wrong Unicode code point for the aleph and ayin transliteration marks. At the time it looked right, but when we switched fonts, it suddenly looked wrong. They should be corrected in all the resources created during that period of time. Luckily the incorrect marks (the forms positioned lower) are not commonly encountered in biblical studies, so a simple find-replace is unlikely to introduce many (if any) typos. In any event it will fix far more than it breaks. I'll send a reminder about the issue to the team involved.

Ben

https://community.logos.com/discussion/comment/563297#Comment_563297

I thought I'd found some more of these bad alephs as commas, in the Jewish New Testament Commentary.

However, it looks like the JNT is using a comma instead of a schewa, which is quite weird.

Ben

https://community.logos.com/discussion/comment/823687#Comment_823687

According to google books, these commas should be alephs, which is not a good choice of transliteration of Hebrew.

So there is some kind of Logos encoding problem here, because in Logos these are commas, not alephs.
https://books.google.com/books?id=ES_BNmC18GIC&pg=PA2005&dq="upholding+all+that+exists+by+his+powerful+word"&hl=en&sa=X&ved=0ahUKEwij89bDsv3MAhXELmMKHdCzDY4Q6AEIHTAA#v=onepage&q="upholding all that exists by his powerful word"&f=false

George Somsel

https://community.logos.com/discussion/comment/823688#Comment_823688

I don't have the JNT so I was not aware of this problem until you raised it. This is simply one of the reasons I don't like transliteration. Hebrew should be Hebrew and Greek should be Greek.