[mailto:b...@sagehill.net]
Gesendet: Sonntag, 13. November 2016 23:05
An: Fekete, Róbert <robert.fek...@balabit.com>;
docbook-apps@lists.oasis-open.org
Betreff: Re: [docbook-apps] WebHelp search - anybody working on improving?
I would be willing to help with this effort, but not lead it. If s
I would be willing to help with this effort, but not lead it. If
someone were willing to evaluate better alternatives and integrate the
code into DocBook's webhelp, I could write the XSL templates that
generate the index files.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
On
Hi,
A quick google search shows lunr.js (https://github.com/olivernn/lunr.js ),
and a possibly improved for of it called elasticlunrjs (
http://elasticlunr.com/). Does anyone have an idea about how to integrate
one of these into webhelp? (Specifically, how to generate the index file
form the
On 2016-11-10 Janice Manwiller wrote:
>
> The WebHelp search is a source of frustration, mostly because it does
> not support phrase searches...
>
> Has there been any effort to improve the search? Has anyone else
> implemented a custom search that supports phrase searches?
>
In the current
Current versions of Lucene are capable of finding single words or
phrases and can use various operators such as 'AND', 'NOT' etc. (See
https://lucene.apache.org/core/2_9_4/queryparsersyntax.html.) So the
search packaged with Webhelp is either an old version of Lucene or not
Lucene at all. Other
Actually, it looks like I get the same results with or without the quotes.
I'm not sure the quotes are enforcing phrase searching.
The results list for either source connectors or "source connectors" is
divided into the following sections:
Results for: connectors, source
Results for: source
Of course, using quotes around “source connectors” does enforce phrase
searching. But you’re right that having that become more automatic as in Google
searches would be wonderful.
As I remember DocBook WebHelp ends up with Apache Lucene as its search engine,
and Lucene is quite good. But,
We've been facing the issue too, and any tip will be appreciated.
The issue is that people are used to Google Search, and doing that on
the client side is not easy ;-)
Cheers,
NeoDoc
Camille Bégnis
Gérant
cami...@neodoc.fr
Tél: 04.42.52.24.20
http://www.neodoc.fr/
789, rue de la gare
F-13770
I use DocBook source with the docbkx Maven plugin to generate PDFs,
WebHelp, and some HTML.
The WebHelp search is a source of frustration, mostly because it does not
support phrase searches. So if you search for "source connectors", it looks
for topics that have either the word source or the word
