Syriac Final Forms

It has been reported long ago. The problem is much worse on the Mac version.

.NET 3.5 Which Logos is built on, does not handle Syriac script correctly. .NET 4.0 resolves this problem but also introduced showstopper bugs. When and if Microsoft resolves those issue then Logos will update the program to .NET 4

https://community.logos.com/discussion/comment/268528#Comment_268528

Here's the most recent thread I could find on the Syriac issue.

http://community.logos.com/forums/p/4369/149415.aspx

DLS

https://community.logos.com/discussion/comment/268528#Comment_268528

Thanks for the info!

I think I would rather have a vowel-less text...

https://community.logos.com/discussion/comment/268528#Comment_268528

.NET 3.5 Which Logos is built on, does not handle Syriac script correctly. .NET 4.0 resolves this problem but also introduced showstopper bugs. When and if Microsoft resolves those issue then Logos will update the program to .NET 4

If my situation is any indication, it is using .NET 4.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/268527#Comment_268527

It has been reported long ago. The problem is much worse on the Mac version.

Using "Logos Bible Software 4.3 Beta 12 (4.30.0.1276) (Update Channel: beta)" on Mac, not know if much worse (or not):

Screen capture has Logos 4 Mac on top (and behind) original PDF posted in this thread.

Keep Smiling [:)]

https://community.logos.com/discussion/comment/268539#Comment_268539

.NET 3.5 Which Logos is built on, does not handle Syriac script correctly. .NET 4.0 resolves this problem but also introduced showstopper bugs. When and if Microsoft resolves those issue then Logos will update the program to .NET 4

If my situation is any indication, it is using .NET 4.

Since I don't know Syriac I wouldn't see when this know when it got fixed. I don't remember reading anything in the release notes indicated that .NET 4 has been adopted.

https://community.logos.com/discussion/comment/268545#Comment_268545

not know if much worse (or not):

It is. Look at ܐܵܡܪܼܝܢ in verse 21

Another thing is that search results in Mac are completely garbled.

https://community.logos.com/discussion/comment/268578#Comment_268578

This bug is not fixed yet and logos is not using .NET4 yet. I breathlessly await each and every beta hoping that the bug is fixed. But, according to Bradly, the fix is not even slated for the 4.3 series of Beta tests. See this thread: http://community.logos.com/forums/thread/233678.aspx

I truly believe that the only reasonable solution is to have the
ability to turn off the display of vowel points and diacriticals. But,
then, Logos also needs the ability to ignore diacriticals and vowel
points in other areas also. Such as in lemma searches.

I bring this up about every six months. So, based upon the results of my forum searches, I guess it is about time the issue was raised again [:)] Thanks to the David Sobey for starting this thread. I am really glad to see that I am not the only one who needs this fixed. But then despite the fact that Aramaic/Syriac may have been the predominate lingua franca within the Church in the early years, we who read Syriac are in the minority in this modern era of Biblical Studies [:D]

https://community.logos.com/discussion/comment/268807#Comment_268807

era of Biblical Studies

I wouldn't call that Biblical Studies. We are in an era of darkness.

https://community.logos.com/discussion/comment/268807#Comment_268807

This bug is not fixed yet and logos is not using .NET4 yet.

It looks a lot like .NET 4 to me.

Graham Criddle

https://community.logos.com/discussion/comment/268847#Comment_268847

George

Did you install some of Steve Clark's Logos tools? I believe he bundled the V4 client (I am sure he will correct me if wrong).

This doesn't mean that Logos is using its functionality.

Graham

https://community.logos.com/discussion/comment/268847#Comment_268847

Just because .NET 4 is installed on your machine it doesn't mean that Logos uses it.

https://community.logos.com/discussion/comment/268853#Comment_268853

Just because .NET 4 is installed on your machine it doesn't mean that Logos uses it.

If it's using .NET anything, it's using .NET 4 since that is all that is on my computer. If you have the latest Shibboleth, you must have .NET 4. See

http://www.logos.com/shibboleth

Just above the download button.

https://community.logos.com/discussion/comment/268855#Comment_268855

And Shibboleth is not Logos4 and Logos4 does not use .NET4. Yet.

Simply checking "Programs and Features" is not enough to determine which .NET frameworks you have installed. Try looking in these directories to find out which versions of the framework you have installed:

C:\Windows\Microsoft.NET\Framework
C:\Windows\Microsoft.NET\Framework64

For the last word posted from a Logos employee about their not releasing Logos 4.3 with .NET4 see the comment from Bradley Grainger: http://community.logos.com/forums/thread/233682.aspx

https://community.logos.com/discussion/comment/268922#Comment_268922

And Shibboleth is not Logos4 and Logos4 does not use .NET4. Yet.

Simply checking "Programs and Features" is not enough to determine which .NET frameworks you have installed. Try looking in these directories to find out which versions of the framework you have installed:

C:\Windows\Microsoft.NET\Framework

C:\Windows\Microsoft.NET\Framework64

For the last word posted from a Logos employee about their not releasing Logos 4.3 with .NET4 see the comment from Bradley Grainger: http://community.logos.com/forums/thread/233682.aspx

Then it apparently doesn't use .NET 3 or 3.5 either since they aren't shown as being installed.

https://community.logos.com/discussion/comment/268924#Comment_268924

Then it apparently doesn't use .NET 3 or 3.5 either since they aren't shown as being installed.

Well, if you looked in those directories and are convinced that you do not have the .NET 3/3.5 framework then the only thing I can say is that you must have a magical computer. Logos developers have said that Logos does not use .NET 4 yet. Additionally, I have previously tried to get Logos4 to use .NET 4 (had to hack some configuration information). But, unfortunately, since the program was not built against .NET 4 it got VERY unstable when using those libraries.

EDIT: Just checked again since it was a year ago I last tried .NET 4, and yep it still crashes spectacularly if you try and force Logos4 to use .NET 4.

https://community.logos.com/discussion/comment/269002#Comment_269002

Then it apparently doesn't use .NET 3 or 3.5 either since they aren't shown as being installed.

Well, if you looked in those directories and are convinced that you do not have the .NET 3/3.5 framework then the only thing I can say is that you must have a magical computer. Logos developers have said that Logos does not use .NET 4 yet. Additionally, I have previously tried to get Logos4 to use .NET 4 (had to hack some configuration information). But, unfortunately, since the program was not built against .NET 4 it got VERY unstable when using those libraries.

EDIT: Just checked again since it was a year ago I last tried .NET 4, and yep it still crashes spectacularly if you try and force Logos4 to use .NET 4.

I didn't say that I don't have .NET 3 or 3.5. What I said was that it apparently is not installed. In the Control Panel in which programs can be uninstalled or changed it shows .NET 4 but not .NET 3 or 3.5.

https://community.logos.com/discussion/comment/269006#Comment_269006

I didn't say that I don't have .NET 3 or 3.5. What I said was that it apparently is not installed. In the Control Panel in which programs can be uninstalled or changed it shows .NET 4 but not .NET 3 or 3.5.

Not all the software that is installed on your system will show up in "Programs and Features." If you have .NET 3 or .NET 3.5 in the C:\Windows\Microsoft.NET\Framework or C:\Windows\Microsoft.NET\Framework64 directory then it is installed on your system. That is what Logos 4 is using. And Logos4 will most likely crash if you try and get it to use .NET 4.

https://community.logos.com/discussion/comment/268813#Comment_268813

I wouldn't call that Biblical Studies. We are in an era of darkness.

ROTFL

I didn't meant that it is the era of Biblical Studies, but was referring to what we call Biblical Studies in this era [:)]

https://community.logos.com/discussion/comment/269010#Comment_269010

I understood you perfectly. It is because we use the term biblical studies to describe a field that has nothing more to do with philology or science, that we live in a dark era.

For me, a feminist reader of the genealogical list in Chronicles is not a biblical study. It could be folklore, gender studies, whatever but it is not biblical studies. A "researcher" of the OT who is not well versed in Biblical Hebrew should not be part of what we term Biblical Studies in the academic world. Unfortunately some of the most renowned scholars of the day are as proficient in Biblical Hebrew as my beloved cat Jotham. I can smell them a mile away....

We need to pay close attention to what we term Biblical Studies lest it all become a sham.

MJ. Smith

https://community.logos.com/discussion/comment/269032#Comment_269032

whatever but it is not biblical studies.

Trying to ruin my fun? Next thing I know you'll be diss'ing Giovanni Pico della Mirandola as a Bible scholar[:D]

(My sincere apologies if I offend any forum members who are disciples of Giovanni - I truly thought there would be no one to be offended)[H]