AI Search Gap: Multi-Word Regular Expression Search in RadPdfProcessing - #808
Merged
Conversation
Decision
Recommend — Add a section and code sample to libraries/radpdfprocessing/features/search.md explaining multi-word search, regex options, whitespace and line-break normalization (" "), and page-boundary constraints.
Confidence: High
Gap: Incomplete content and missing examples
Why
Customer need: Clear instruction and examples for performing multi-word and regular expression searches in RadPdfProcessing, including reasons why visible phrases might not match and how whitespace is handled.
Current gap: The documentation at libraries/radpdfprocessing/features/search.md only presents API signatures in tables without demonstrating multi-word regex patterns or explaining that text within pages is normalized with space separators (" "), that searches are isolated per page, and that WholeWordsOnly modifies the regex pattern. AI Search fills this void by hallucinating incorrect reasons ("hidden formatting", "non-breaking spaces not matched by \s+").
Preferred approach: Update the existing authoritative article libraries/radpdfprocessing/features/search.md with a "Regular Expression and Multi-Word Search" section, code example, and technical notes on text extraction and page boundaries.
Not selected: Creating a separate KB article was rejected because search.md is already the primary authoritative documentation page for TextSearch and currently lacks narrative guidance.
YoanKar
approved these changes
Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Decision
Recommend — Add a section and code sample to libraries/radpdfprocessing/features/search.md explaining multi-word search, regex options, whitespace and line-break normalization (" "), and page-boundary constraints. Confidence: High
Gap: Incomplete content and missing examples
Why
Customer need: Clear instruction and examples for performing multi-word and regular expression searches in RadPdfProcessing, including reasons why visible phrases might not match and how whitespace is handled. Current gap: The documentation at libraries/radpdfprocessing/features/search.md only presents API signatures in tables without demonstrating multi-word regex patterns or explaining that text within pages is normalized with space separators (" "), that searches are isolated per page, and that WholeWordsOnly modifies the regex pattern. AI Search fills this void by hallucinating incorrect reasons ("hidden formatting", "non-breaking spaces not matched by \s+"). Preferred approach: Update the existing authoritative article libraries/radpdfprocessing/features/search.md with a "Regular Expression and Multi-Word Search" section, code example, and technical notes on text extraction and page boundaries. Not selected: Creating a separate KB article was rejected because search.md is already the primary authoritative documentation page for TextSearch and currently lacks narrative guidance.