BUG: 5.2b Beta 4 Mac Lost Ezra SIL (again)

This bug is especially annoying as MS Word for Mac will not recognize the presence of SBL Hebrew. Please give me a quick fix.

Find more posts tagged with

Comments

Angela Murashov

This bug is especially annoying as MS Word for Mac will not recognize the presence of SBL Hebrew. Please give me a quick fix.

I'm not sure why this is happening [:(] I will create a case for a Developer to fix this asap.

As a workaround please use the SBL Hebrew font for now until this bug is fixed.

Jack Caviness

As a workaround please use the SBL Hebrew font for now until this bug is fixed.

That works for Logos, but causes a problem when pasting into MS Word which refuses to recognize the existence of SBL Hebrew.

Josh Edwards

Jack, I found this on the SBL Education Resources page (http://www.sbl-site.org/educational/BiblicalFonts_FAQ.aspx)

"When I try to use SBL Hebrew in Microsoft Word for Mac OS X the font does not show up or the text does not display correctly.

Microsoft Office 2011 does not support right-to-left languages. At this time, Microsoft has not announced that any support will be forthcoming. As such, neither Office 2011, Office 2008 nor Office 2004 is a viable option for using the SBL Hebrew font. At this time, NeoOffice does not support the type of complex script layout that SBL Hebrew uses. As a result, consonants will display properly but vowels and other diacritics will not. There are several word processors, such as Mellel and Nisus Writer Pro, which do support the proper complex script layouts, and these are currently the best option. Additionally, users of Leopard (10.5) and later can edit text in Hebrew by using the SBL Hebrew font in TextEdit. For a more detailed explanation of using SBL Hebrew in OS X, please refer to the font manual."

It looks as if it's a MS Office 2011 problem. I don't know if this helps or not, but thought I'd put it out there. Have a great day.

Angela Murashov

I will create a case for a Developer to fix this asap.

Great news! This should be fixed in 5.2b Beta 5 [:D]

Jack Caviness

Great news indeed