Re: [Exist-open] search term highlighting not working properly

[Michael B. <mbe...@mb...>]

>Can someone explain me how to achieve search term highlighting for
> elements AND attributes?

There appears to be some inconsistency here, I suspect in the implementation
as well as in the documentation. When match tagging was first introduced it
was controlled by a configuration setting  "highlight-matches" with the
possible values "elements", "attributes" or "both".  But this appears to
have been ?replaced /?supplemented/ ?superseded by separate serializer
configuration attributes "match-tagging-attributes" and
"match-tagging-values". Presumably the equivalent of  the "both" value on
"highlight-matches" would be to set both "match-tagging-attributes" and
"match-tagging-values" to "yes".  I don't know whether setting
"highlight-matches" to "both" is supposed then internally to set
"match-tagging-attributes" and "match-tagging-values" to "yes", but it
apparently doesn't do so.

I notice that in recent builds, neither the setting for "highlight-matches"
I have in client.properties, nor the values of
match-tagging-values/attributes in conf.xml  has any effect whatsoever when
I use the command-line client in embedded mode. No matter what combination
of settings I use, I never get match tagging when connecting to a local
instance via that client.. However, match tagging does work (and follows the
setting in conf.xml) when using the REST interface. Since that's my normal
way of using eXist, I hadn't noticed the command-line client problem until
now.

>I've asked this question a couple of times already but got no reply.

It looks like we are all the victim of the pretty awful Sourceforge mailing
list service. Probably due to overload, but also I think to some would-be
clever anti-spam stuff that backfires badly at times. But it is putting the
usability of this list, and therefore also effective exchanges between eXist
users and developers, under considerable strain.

Michael Beddow