modifying stop-words list -- is it possible?

[pvz]

I'm looking for a way to modify the "Stop-Words" list that Flare uses in Webhelp output.

What I'd like to do is add a few words that are specific to our software (the app name, for example). I've been working to refine/improve the results returned by the Webhelp search, and have discovered that our app name is essentially "noise" when doing a Help search. The context of the application is assumed, so even though a user might include the app name while searching in our webhelp, I'd like the search to ignore that name.

As it now stands, a search using "searching <app>" returns a confusing list of results, none of which relate to searching w/in our app. All the top topics are loaded with the app name rather than having anything to do with the concept of searching. Users don't understand why this might be.

I'm hoping there's a file I can modify... but I've found no reference to one.

thanks, in advance,

paul

[pvz]

For anyone who is interested -- I just heard from Madcap Support that this is not currently possible.

They did enter a feature request (32343) for this capability.

best regards,

paul

[heatherbrh]

Hello - does anyone know if it's possible to modify the stop words list these days?

[Paul Griffiths]

I'm guessing there's been no progress on this?

Our application includes commands like WHAT and WHERE, but WebHelp Search can't find the topics that describe them!

[Andrew]

I *believe* (but am not sure) you can modify the stop words list if you use SQL Server for your WebHelpPlus search (requires IIS server and setup). SQL Server does have a list of stop words for its full text search engine that you can modify.

[NorthEast]

I'm guessing there's been no progress on this?

Our application includes commands like WHAT and WHERE, but WebHelp Search can't find the topics that describe them!

You can always set the target to include stop-words in search (on Performance tab); of course that means the results don't exclude any stop-words, so you'll need to test if the benefits outweigh the drawbacks.

[Paul Griffiths]

Thanks Dave. I have in fact done just that.

[Username_password]

Hi all - 4 years later...

I got this tip from MadCap but have not investigated myself if successful. Someone want to try? Drawbacks? (originally we wanted help to have a stop list for other languages)

Background info:
Hello XX
We have a work-around for this issue.
Through the use of Language skins, you can insert your own list of stop words. This can also be done with other languages as well.
Attached is a zip file that contains an English language skin (fllng). We have populated it with all the current stop words for English projects.
To install this language skin and other language skins:
In Flare click Tools > Manage Language Skins
Scroll down and select "English"
Click "Open File For Editing"
Close this file in Flare - We just need to open it so we can create the file in the local users appdata folder.
Browse to the following location:
C:\Users[USER NAME]\AppData\Roaming\MadCap Software\Flare\Language Skins
Unzip the attached file and place it in this folder.
Open the en.fllng file in a text editor and notice how the stop words are set up in the XML. The tags are case sensitive.
Open a project in Flare
Open the target and click on the Language tab
Select "English"
Build and test.
Using these same steps, you can build stop words for other languages as well. Because the language skins are stored in the users local folders, each person building with Flare will need to copy these files into the same location.
*Note – Be sure the proper language is set in the target so it will use the proper language skin.
This topic talks about how to create language skins. It says it’s not supported in HTML5, but for stop words – it is supported.
http://webhelp.madcapsoftware.com/flare ... _Skins.htm