Please. Reading Syriac would be so much easier.
Thanks!
James - I fail to understand what you are asking or stating. Some things might help. First, when creating a new thread, don't leave crucial information in the subject line! Include it in the thread.
What does: "Logos 4.5 and .NET 4 - Please. Reading Syriac would be so much easier" mean?
James - I fail to understand what you are asking or stating. Some things might help. First, when creating a new thread, don't leave crucial information in the subject line! Include it in the thread. What does: "Logos 4.5 and .NET 4 - Please. Reading Syriac would be so much easier" mean?
It means that .NET 3.5 which Logos is built upon cannot display Syriac correctly. Moving Logos 4 to .NET 4 would fix the display problems. BUT, the developers have said that there are bugs in .NET 4 that they have to work around or be fixed by MS before it can happen.
Thanks Kevin. It would have been much easier to understand if the OP had said "please move to .NET4." As a side note... Every now and then I hear grumblings on "my side" of the forums (Mac) about .Net and mono. Is the lack of compatibility with Mac one of the reasons for not upgrading?
Hi Alabama
No, I don't believe this has anything to do with Mac compatibility - this is a pure Windows framework issue.
Graham
I LOVE that I have no idea what you are talking about... No need to explain... [Windows] ignorance is bliss. [:)]
I think James was speaking to the developers, and both he and they know exactly what the issue is (though Alabama24 is correct; it takes a few seconds to catch up).
Personally, I think James is just somewhat ahead of his time (I obviously don't know him; just his posts).
The non-greek/hebrew languages have tremendous 'clues' concerning the text. When I went to Bible college, 'greek' and 'hebrew' were 'the' languages. The argument was that those were the 'original languages'.
And that's true as far as it goes. But if one is familiar with the manuscripts, we don't really 'have' the original languages (nor the text). What we have is a series of later generations of text, among which are MANY languages ... latin, coptic, syriac, armenian, and so forth.
And with software like Logos with its high inter-connectedness, the ability of 'normal' people to explore the Biblical text in those other languages is growing significantly.
With the Gorgias collection, I now have syriac translations on my left, coptic and latin in the middle and then the two major greek textforms on the right. And as I move from verse to verse, I'm impressed with how the text (and concepts) seems to 'grow'. It tells me a lot about what early believers found valuable.
Already, Logos has a really good LXX/MT interconnectness that really helps to follow the OT text development. Now for the NT!
A recent thread was discussing the ins/outs of greek diagramming. Certainly very useful. But once you start looking at those other parallel languages , the 3rd/4th century greek textforms simply become players in a much larger world.
So, my 'hat' is off to James and his continuing efforts to 'grow' the syriac support in Logos.
Now if we can find a 'latin' champion to push that area as well (we have Matthew with his coptic; we're covered there).
Yes, I was primarily speaking to the developers and I am sure they are tired of hearing about this issue. They know the problems that not moving to .NET4 cause, and they also know the problems that moving to .NET4 would cause. I really do not want to push them too much because I am a software developer (and have been for more than 30 years). But the fact that Logos 4 does not properly display pointed Syriac really is a major problem and has been for about two years. And the developers have said the problem would be addressed in a future release. I am just reminding them that the problem still exists and needs to be addressed and hope that if I am consistent with reminding them without bringing the subject up too often I might just get a version of Logos 4 that has the problem fixed. I'd be happy just knowing when it would be fixed, and elated if it was fixed before the Leiden Peshitta was released. But, please, don't delay the Leiden just to get the bug fixed first. I cOUld COnTiNue tO HanDlE rEadInG sYRiaC LiKE thIs if I could get he Leiden earlier
I'll see if I can interest my daughter in that task [:D]
.NET 4.5 is in beta test with Visual Studio 11 development environment, roughly coinciding with Windows 8 release. We can be hopeful for fixes and stability for Logos 4 on it. Sadly, that's probably a full year away. I am hopeful Logos can at least keep us apprised of their progress in testing it, i.e. does it look more stable for them or not. If it is not more stable/less buggy, you can probably forget about the .NET 3.5 bug fixes being resolved fin Logos or a VERY long time. Which will be sad, that basically says the Logos product is trapped on the .NET 3.5 platform (making one wonder about the wisdom of the decision to use it, but we won't go there for now :-))
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
