Exact phrase search issue
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 152
- Joined: Fri Apr 24, 2015 12:28 pm
Exact phrase search issue
Hi,
We found that in the webhelp responsive search field, the search algorithm seems to handle phrases that include slashes (/) differently.
For example, if I search for -- activate/deactivate the xy option -- the result with the highest rating at the top is the correct match, but I find other topics that contain any of the words. This is a correct search result.
If I search for -- "activate/deactivate the xy option" -- which is the exact phrase, I get no result.
If I search for -- "activate deactivate the xy option" -- I get at least one match, but I have to leave out the slash to get it, but this is not the exact phrase.
Working with <oXygen/> XML Editor 19.0, build 2017042020.
Thanks,
Christina
We found that in the webhelp responsive search field, the search algorithm seems to handle phrases that include slashes (/) differently.
For example, if I search for -- activate/deactivate the xy option -- the result with the highest rating at the top is the correct match, but I find other topics that contain any of the words. This is a correct search result.
If I search for -- "activate/deactivate the xy option" -- which is the exact phrase, I get no result.
If I search for -- "activate deactivate the xy option" -- I get at least one match, but I have to leave out the slash to get it, but this is not the exact phrase.
Working with <oXygen/> XML Editor 19.0, build 2017042020.
Thanks,
Christina
oXygen XML Editor 27.1 build 2025041508
DITA OT 3.7.4
DITA OT 3.7.4
-
- Posts: 846
- Joined: Mon Dec 05, 2011 6:04 pm
Re: Exact phrase search issue
Hi Christina,
The "/" sign is currently considered as a word separator, helping users to search for just parts of the composed phrases.
However, I have just logged an improvement request in our internal improvement/issues tracking system to implement a fix in order to also consider the slash as part of the searched string.
The workaround is the one you already stumbled upon - using a space instead of "/" in your searches.
This will be analyzed by our development team and we will update this thread when the fix will get implemented.
Thank you for the feedback!
Regards,
Costin
The "/" sign is currently considered as a word separator, helping users to search for just parts of the composed phrases.
However, I have just logged an improvement request in our internal improvement/issues tracking system to implement a fix in order to also consider the slash as part of the searched string.
The workaround is the one you already stumbled upon - using a space instead of "/" in your searches.
This will be analyzed by our development team and we will update this thread when the fix will get implemented.
Thank you for the feedback!
Regards,
Costin
Costin Sandoi
oXygen XML Editor and Author Support
oXygen XML Editor and Author Support
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service