BUG: text comparison with Hebrew

something I missed when I originally posted - seems to only occur for the second text compared.

anyone else have this behavior? Is it only me? [:(] Is it Mac only? [:S]

Rosie Perera

Must be Mac only. I can't reproduce this on Windows using Logos 5.0b SR-1.

https://community.logos.com/discussion/comment/468749#Comment_468749

Must be Mac only. I can't reproduce this on Windows using Logos 5.0b SR-1.

Thanks!

No matter which Hebrew text is placed first in text comparison the font rendered is smaller

I see it too, but not just on the first verse, but on verses 1,4 and 7 (Gen 1:1). Except when the first 'verse' is just a Qumran reference without any actual verse; then it's 3 and 6 instead (Gen 5:5). And if I place BHS before the collection in the latter case it becomes 1,3 and 6.[^o)]

Haven't yet seen your second issue, though.

EDIT: Added to the Feature Parity list:

PC Text Comparison in Hebrew displays correctly, while Mac displays some verses with smaller font.

https://community.logos.com/discussion/comment/468817#Comment_468817

No matter which Hebrew text is placed first in text comparison the font rendered is smaller

I see it too, but not just on the first verse, but on verses 1,4 and 7 (Gen 1:1). Except when the first 'verse' is just a Qumran reference without any actual verse; then it's 3 and 6 instead (Gen 5:5). And if I place BHS before the collection in the latter case it becomes 1,3 and 6.

Haven't yet seen your second issue, though.

EDIT: Added to the Feature Parity list:

PC Text Comparison in Hebrew displays correctly, while Mac displays some verses with smaller font.

Thanks fgh!

https://community.logos.com/discussion/comment/468817#Comment_468817

I can replicate and have filed a case for this.

For anyone interested, this is a bug, not a parity issue.

https://community.logos.com/discussion/comment/468878#Comment_468878

I can replicate and have filed a case for this.

Thanks.

For anyone interested, this is a bug, not a parity issue.

I guess I should remove it from the list again then, but Rosie said (and showed) she didn't see it on Windows.

https://community.logos.com/discussion/comment/468881#Comment_468881

I guess I should remove it from the list again then, but Rosie said (and showed) she didn't see it on Windows.

We don't consider differing behavior a parity issue in most cases. If see something out of the ordinary operating on the Mac (or Windows) and not the other--like this issue--then reporting it with BUG in the title is a good way of letting us know.

https://community.logos.com/discussion/comment/468878#Comment_468878

I can replicate and have filed a case for this.

Thanks!

https://community.logos.com/discussion/comment/468906#Comment_468906

Ah, I thought you were saying the bug does show up on Windows after all, but you were just talking about your internal terminology.

For the purpose of that Wiki page, however, all Mac specific bugs tend to count as 'feature parity issues', which is a good thing for those of us on Mac. Since KS4J started adding them to that list, they have gotten fixed several months faster than they did before, and generally faster than bugs that occur on both platforms.

https://community.logos.com/discussion/comment/468920#Comment_468920

For the purpose of that Wiki page, however, all Mac specific bugs tend to count as 'feature parity issues', which is a good thing for those of us on Mac. Since KS4J started adding them to that list, they have gotten fixed several months faster than they did before, and generally faster than bugs that occur on both platforms.

Ok, sounds good. :-)

https://community.logos.com/discussion/comment/468920#Comment_468920

Similar bug in BSL: BUG: bible sense lexicon.

NB.Mick

For the purpose of that Wiki page, however, all Mac specific bugs tend to count as 'feature parity issues', which is a good thing for those of us on Mac. Since KS4J started adding them to that list, they have gotten fixed several months faster than they did before, and generally faster than bugs that occur on both platforms.

Actually it's a bad thing for those of you on the Mac. You (as a group) lobby Logos into fixing small display anomalies and thereby taking scarce development resources from fixing more relevant functional bugs that - as you said - affect both platforms. Thus you hurt yourself, if you end up with a Logos application that looks and behaves like the Windows version but e.g. returns questionable search results.

https://community.logos.com/discussion/comment/469735#Comment_469735

Most Mac specific bugs and issues aren't "small display anomalies", and believe me, I'm not even close to having "a Logos application that looks and behaves like the Windows version". When I open Logos it's one long endless fight with bugs and issues of various kinds. If I'm stupid enough to actually try to do something in it, it takes me on average 2-3 hours to get 5 minutes work done, and then another 6-10 to report all the new bugs I've found. I must have hundreds of bugs affecting me, and I find new ones far faster than the devs fix them. I haven't even dared to open most of the new L5 features. I don't have time to deal with all the bugs I'll find if I do.

Besides, "small display anomalies" aren't necessarily small. Not if they make the text too small to read.

NB.Mick

https://community.logos.com/discussion/comment/469751#Comment_469751

believe me, I'm not even close to having "a Logos application that looks and behaves like the Windows version". When I open Logos it's one long endless fight with bugs and issues of various kinds.

fgh,

I did not want to address you personally - what we consistently hear about your installation is a pity - but just comment on the logic of whether it's good for Mac users that Logos seemingly put more effort into fixing parity issues than into fixing bugs that affect Mac users without being parity issues, that's all.

No harm and no Mac vs Win dogfight intended.

Mick

https://community.logos.com/discussion/comment/469705#Comment_469705

Similar bug in BSL: BUG: bible sense lexicon.

Thanks for referencing this post.

https://community.logos.com/discussion/comment/468878#Comment_468878

I can replicate and have filed a case for this.

Using Logos 5.1 Beta 2 on OS X 10.8.3 can also replicate Hebrew Text Comparison font size differences:

Puzzled by different font sizes when all panels are set to 100 %. Text Comparison is noticeably smaller. Also noted smaller font size in LHI.

Keep Smiling [:)]

Bump

any word on this?

https://community.logos.com/discussion/comment/483688#Comment_483688

When it is confirmed fixed in a beta release (or upcoming beta release) this thread will be udpated.

https://community.logos.com/discussion/comment/472580#Comment_472580

Using Logos 5.1 Beta 2 on OS X 10.8.3 can also replicate Hebrew Text Comparison font size differences:

Logos 5.1 Beta 5 on OS X 10.8.3 looks the same so not (yet) fixed.

Keep Smiling [:)]

Brisa Davis

This issue will be fixed in 5.1 Beta 7 for beta users, and in general when 5.1 ships to the stable channel.

https://community.logos.com/discussion/comment/486608#Comment_486608

This issue will be fixed in 5.1 Beta 7 for beta users, and in general when 5.1 ships to the stable channel.

sorta fixed in RC1... see below for what still needs resolving.

Brisa Davis

https://community.logos.com/discussion/comment/497022#Comment_497022

I am able to reproduce the issue of "difference" being displayed backwards on Mac for BHS SESB 2.0. I will report this issue to Development.

https://community.logos.com/discussion/comment/486608#Comment_486608

This issue will be fixed in 5.1 Beta 7 for beta users, and in general when 5.1 ships to the stable channel.

Sorry, but I'm still seeing it in RC1, when I use a collection with all my Hebrew Bibles:

https://community.logos.com/discussion/comment/497640#Comment_497640

Sorry, but I'm still seeing it in RC1, when I use a collection with all my Hebrew Bibles:

Using Logos 5.1 RC 1 on OS X 10.8.3 can replicate smallish font in two resources plus another difference:

Keep Smiling [:)]