Copy link to clipboard
Copied
RoboHelp 2020.3 (Windows).
Received a request from our end users to be able to include/incorporate special characters in searches.
Thoughts?
Copy link to clipboard
Copied
I can confirm if I add * (asterisk) to the list, I get zero results when I search for a regular word.
I feel like maybe that setting doesn't do what we think.
For example:
I turned off the setting, generated and searched for "2". Results returned. [I'd have expected no results, given "2" seems to be considered a special character based on the default list that populates when the setting is on??]
I turned on the setting ("0;1;2" etc populated in the new field automatically), generated and searched for "2". Results returned. [The behaviour in this scenario wasn't any different from with the setting off.]
I added a - (hyphen) to the list, generated and searched for "2". Results returned.
I added a * (asterisk to the list, generated and searched for "2". No results returned.
I can't find any explanation of the setting in the help for the frameless preset. So I think either it doesn't work, or it's not doing what we think it should. I think this may need to go to Adobe for an explanation of the field, unless Peter has further information.
Copy link to clipboard
Copied
One further test.
I turned off the setting, generated and searched for "2". No results returned. [wtf??]
When I turned the setting back on, the previous list of characters that included the - and * was populated, so it looks like even when the setting is off, the list of chars is being applied/checked/used?
Copy link to clipboard
Copied
Yep, I can't figure it out either. Appreciate the testing.
I logged a bug - https://tracker.adobe.com/#/view/RH-8498
Copy link to clipboard
Copied
I have flagged this thread with Adobe and they will be responding.
________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information
Copy link to clipboard
Copied
Hi
It seems * is currently not supported in special characters list. Please remove this from the input characters list and tryout the search. We will be fixing this in future updates.