When .NET4?

I know this has been
brought up multiple times. And not just by me. But it has been more than
a year since a bug covering the display of final forms of Syriac
letters was first reported. So I don't believe that I am being too
impatient. See:

http://community.logos.com/forums/thread/39747.aspx

The report back from
Logos was that it was a problem with .NET3.5 that would be fixed in
.NET4. However, since then Logos has found a problem in WPF, as shipped with .NET4, displaying "OldStyle" text
that consists only of numeric and punctuation characters. Actually,
according to MS, the problem is in a binary that is part of Windows
rather than a problem that is part of WPF. That was reported by the MS WPF group to the MS Windows group and the
issue closed by MS more than 5 months ago. See:

https://connect.microsoft.com/VisualStudio/feedback/details/545921/old-style-numerals-are-not-rendered-for-runs-containing-only-numbers

So, is the display
problem with text styled with "OldStyle" significant enough to continue
delaying the proper display of an entire language?

Especially since,
according to MS, a hotfix to the OS (if/when one is released) would fix
the problem? Logos could release a version of the software engine that
was linked against .NET4 so that Syriac displayed properly and the software
would automatically have the "OldStyle" textual display problem fixed
as soon as MS released a hotfix. If ever.

Is it too much to ask for such a release? Maybe it could be a specialized release over a new update channel so that only those who really needed the proper
display of Syriac would update to that release?

At
this time it is not (yet) absolutely critical for me as I have developed other
methods (and in some ways superior to Logos) for displaying, searching, and analyzing the NT Peshitta. But I
have 21 other resources (commentaries, grammars, etc) where this causes
a problem trying to read Syriac text. And this will become critical as
soon as the Leiden Peshitta is released.

I hate to sound like a squeaky wheel when I know that the Logos team tries their very best to please their customers. So...

Thanks and God Bless you and your efforts.

Find more posts tagged with

Comments

Ron

I believe there were a few other issues (font and display) that Bob said that .NET 4 would fix too, though I'm not able to go dig up the threads at the moment.

DMB

James ... a couple of days ago I was reading one of your threads from about a year ago ... and then you returned! I have a question for you, since you seem to have quite a bit of expertise in this area. I use both L3 and L4. In L3, Targum Lexicon can operate in parallel with my hebrew lexicons. In other words, a left or right arrow can move from HALOT to Targum Lexicon (which I like since TA shows the equiv's in a list). In L4, that doesn't happen nor can you assign a cross-resource link. But if you simply copy the hebrew from HALOT to Targum Lexicon, it'll do the lookup (recognizing TA's normal lookup would be in aramaic).

Can I assume the Targum Lexicon problem I've described is related to some of your previous thread (or this one, though here you're talking syriac)? Or is there something L3 did that L4 can't do? Or is the L4 version of Targum Lexicon likely the problem?

Thank you for any comments you might have.