BUG 6.10 Beta 1 (probably stable versions as well) copying Hebrew fonts is 2/3 broken
In 6.10 Beta 1, copying text in Hebrew font and bringing it to MS Word is broken in 2 of 3 functionality variants.
Doing this via selecting text and Print/Export and "Add to new Word file" will result in a wrong fontname handed over to MS Word in that the proper name is prefixed with ./# so SBLHebrew is given as ./#SBLHebrew (same goes for Ezra SIL) which the text processor can't recognize and will substitute e.g. with Times New Romans.
Using the Copy Bible Verse tool is buggy in this respect as well, MS Word not showing a wrong fontname but a substitute font (Times New Romans).
See my post in another thread, including screenshots from taking Hebrew text over to Word (in my case a German language installation of Word 2007 on Win 7 32bit).
Note that simple Copy/Paste via keyboard or right-click menu seems to work perfectly fine, as does text in Greek language as far as I tested tonight.
I've seen the same issue in screenshots by user Sascha John in an earlier release and assume the OP of the thread linked above is not on Beta, too.
Have joy in the Lord! 
Comments
-
6.10 Beta 1 Mac OS 10.11.3
Partially confirmed: I use Ezra SIL as the default Hebrew font because MS Office for Mac 2011 refused to recognize SBL Hebrew as a legitimate font. The Hebrew text is Deuteronomy 25:13.
As Mick noted, Copy/Paste works correctly, even if Word does require extra steps. But that is a long-standing MS bug and not a Logos problem.
0 -
NB.Mick said:
In 6.10 Beta 1, copying text in Hebrew font and bringing it to MS Word is broken in 2 of 3 functionality variants.
I can reproduce this and will create a case to get this fixed.
0 -
Angela Murashov said:NB.Mick said:
In 6.10 Beta 1, copying text in Hebrew font and bringing it to MS Word is broken in 2 of 3 functionality variants.
I can reproduce this and will create a case to get this fixed.
Thanks!
Have joy in the Lord!
0 -
Angela Murashov said:
I can reproduce this and will create a case to get this fixed.
This should be fixed on 6.11 Beta 1.
0
