Topic Guide Weirdness

I tried following the examples in the "What's New" video to see it for myself, and the Topic Guide is not producing expected results.

I tried Lord's Supper a few times as the topic, and a couple of times it took me to "Jude" and another time it took me to "Servant of the Lord". And sometimes it doesn't take me anywhere at all with this topic query.

Lord's Supper doesn't appear in the match list at all when entering Lord's, but it does when entering Supper.

And the dropdown list (when typing the first couple of chars) is a real jumble of words and phrases with no apparent sorting order.

The shine is beginning to disappear off my 12 hour old purchase already. Two features tried and two lots of unexpected behaviour, and far too many crashes Using Win 7x64.

Thanks
Richard

Find more posts tagged with

Comments

David Thomas

I tried Lord's Supper a few times as the topic, and a couple of times it took me to "Jude"

I'm not having crashes, but I can replicate this result on my Win7 64 bit

Maybe the OP should edit the title of the Thread to begin with BUG:

Mark Smith

I tried Lord's Supper a few times as the topic, and a couple of times it took me to "Jude" and another time it took me to "Servant of the Lord". And sometimes it doesn't take me anywhere at all with this topic query.

Some things are not set up in the obvious fashion, and I think Logos will need to work on it.

As you found, Supper gets you there, and so does Communion. Why you can't just type in Lord's Supper is beyond me.

So, in this tool we need to wait for the drop-down menu and make our selection. If that doesn't work, think of a related word. Menu items are the only ones that work. Not the best but this is new and I'm sure Logos will benefit from feedback.

crashes Using Win 7x64.

Sorry to hear that. I have Win7 and have had no trouble.

The shine is beginning to disappear off my 12 hour old purchase already.

Well, I hope you'll still find lots of use for these tools. I already value L5 over L4 a great deal.

Richard Lyall

https://community.logos.com/discussion/comment/427279#Comment_427279

I tried Lord's Supper a few times as the topic, and a couple of times it took me to "Jude"

I'm not having crashes, but I can replicate this result on my Win7 64 bit

Maybe the OP should edit the title of the Thread to begin with BUG:

I'm growing less and less sure about what's a bug and what's intended behaviour with the new features I've tested so far!

Richard Lyall

https://community.logos.com/discussion/comment/427280#Comment_427280

Well, I hope you'll still find lots of use for these tools. I already value L5 over L4 a great deal.

I'm sure I will in time, after some refinement - perhaps having been a beta tester on L4, going through a long process of working with a work in progress, but not having been a tester on L5 I came in expecting L5 to feel more finished\polished.

Yes I think this is me coming down to earth with a bump!

MJ. Smith

https://community.logos.com/discussion/comment/427294#Comment_427294

This is a regression - for me there appears to be a pattern - I also tried with Aaron's rod which had not originally worked but I thought the bug was fixed:

If you stop typing before the apostrophe and let it populate, everything is as expected:

If you include the apostrophe, you get Jude because of the parenthetic identifier (I'm not fond of this aspect of the feature) ... but it is unable to search beyond Jude

Then, of course, you can type in the entire title, hit enter, go get a cup of coffee, read the newspaper, open your mail ... all on the clock 'cause you're just waiting for Logos to respond.[C]

Seriously, I only have problems when there is an apostrophe. And the behavior is predictable.

NB.Mick

https://community.logos.com/discussion/comment/427583#Comment_427583

If you stop typing before the apostrophe and let it populate, everything is as expected:

Just a thought here from looking at your screenshot picture - could it be the apostrophe character that's the problem? In your typing, the apostrophe is straight - same as in "Lord's Brother", whereas the apostrophe in the pre-populated words is curved like a comma.

NB.Mick

https://community.logos.com/discussion/comment/427589#Comment_427589

When i think over this, it seems to me the most logical explanation of the issue. Logos may use what is called "typographic apostrophe" (on purpose, or because they use a word-processor to pre-edit content and those have become notorious fo changing apostrophes along with quotation marks and other things), and of course we usually type the "typewriter apostrophe" from our keyboards.

I'm not on my Logos 5 machine currently, but could someone try to do the above searches using a typographic apostrophe (Alt-0146 on numeric keypad, see below for details) to verify?

This would then be the necessary workaround until Logos puts the content into a reduced coding (we all don't want to start searching for things with typing diacritical marks, tremas and what else in the future) or automatically replaces typewriter apostrophes with typographic ones.

Mick

--- details for entering the typographic apostrophe on various platforms, just copied, not tested! ---

Wikipedia says:

More recently, the correct use of the typographic apostrophe is becoming more common on the Web due to the wide adoption of the Unicode text encoding standard, higher-resolution displays, and advanced anti-aliasing of text in modern operating systems. Because typewriter apostrophes are now often automatically converted to typographic apostrophes by wordprocessing and desktop-publishing software (see below), the typographic apostrophe does often appear in documents produced by non-professionals.

How to enter typographic apostrophes on a computer
Unicode	(Decimal)	Macintosh	Windows-1252 Alt code	Linux/X	HTML entity
U+2019	8217	`⌥ Option`+`⇧ Shift`+`]`	`Alt`+`0146` on number pad	`AltGr`+`⇧ Shift`+`B` or `Compose`+`'`+`>`	`’`

XML

Richard Lyall

https://community.logos.com/discussion/comment/427636#Comment_427636

Yes the typographer's quote (ANSI 0146) is used in the topic list and it does locate "Lord's Supper" properly when using it. On Win 7 x64

NB.Mick

https://community.logos.com/discussion/comment/427686#Comment_427686

Yes the typographer's quote (ANSI 0146) is used in the topic list and it does locate "Lord's Supper" properly when using it. On Win 7 x64

Good that you found it!

I created a bug report in Desktop Beta Forum which hopefully will be brought to the developer's attention: http://community.logos.com/forums/t/60171.aspx

Mark Smith

https://community.logos.com/discussion/comment/427695#Comment_427695

Nice detective work, everyone.

NB.Mick

https://community.logos.com/discussion/comment/427826#Comment_427826

And a fast fix from Logos: This is solved in RC1. Entering a straight "typewriter apostrophe" will bring up the search results with comma-like "typographic apostrophe"

This works also for other instances, such as "Aaron's rod". Thanks!