https://bugs.documentfoundation.org/show_bug.cgi?id=171336
Bug ID: 171336
Summary: The search dialog should display number of matches
found
Product: LibreOffice
Version: 26.2.1.2 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: [email protected]
Reporter: [email protected]
Currently, the Search dialog does not show the number of matches found. When we
scroll through the matches, the dialog does not show x/y counter.
This is a useful feature, as shown below:
1. Document Assessment and Scoping
Gauging Frequency: The user can immediately assess how often a specific term,
concept, or name appears throughout the document. This is useful for
determining if a term is overused or underutilized. In legal documents, it
shows how many times a specific term/concept is mentioned.
Estimating Workload: Before performing a "Replace All" operation, the user can
see the exact number of matches to estimate the scope and potential impact of
the changes.
2. Accuracy in Search and Replace
Verification Before Replacement: It allows the user to verify that the search
term appears the expected number of times before clicking "Replace All." If the
count is unexpectedly high or low, it may indicate an error in the search term
(e.g., accidentally searching for a common letter instead of a specific word).
Partial Replacements: When navigating through matches manually (using "Find
Next" or "Find Previous"), the x/y counter provides crucial context. The user
knows they are on match 3 of 12, allowing them to make informed decisions about
which specific occurrences to replace without losing track of their progress.
3. Navigation and Orientation
Progress Tracking: The x/y format provides a clear sense of progress when
reviewing search results. The user knows exactly how far they are in the
document relative to the total matches.
Avoiding Repetition: It assures the user that they have seen all instances.
When they reach match 12/12, they know they have reviewed the entire set and
can stop searching.
Contextual Awareness: It helps the user maintain orientation within a long
document. Knowing they are viewing the last match (e.g., 45/45) provides a
different navigational cue than knowing there are 45 more matches ahead.
4. Editing and Proofreading
Consistency Checking: Authors and editors can ensure consistent usage of
terminology. For example, searching for "color" to ensure it is used 15 times
and "colour" is used 0 times in an American English document.
Quality Assurance: When updating a specific name or fact (e.g., a client's name
in a contract), the user can confirm that every instance has been successfully
updated by performing a second search and seeing the count drop to zero.
5. Academic and Technical Writing
Citation and Reference Management: A user can verify that every citation in the
text has a corresponding entry in the bibliography by searching for citation
markers (e.g., "@" or "(Author, Year)") and comparing the count to the number
of bibliography entries.
Indexing: When creating an index, the user needs to know exactly how many times
a term appears to decide if it is significant enough to warrant an index entry.
6. User Confidence and Interface Transparency
System Feedback: It provides immediate, clear feedback that the search function
is working correctly. It confirms that the search completed and didn't freeze
or encounter an error.
Reducing Guesswork: It eliminates the ambiguity of a simple "Not found" message
by providing a positive count, or by quantifying how many items were found,
turning a binary result into useful data.
---------------------
Version: 26.2.1.2 (X86_64)
Build ID: 620(Build:2)
CPU threads: 8; OS: Windows 11 X86_64 (build 26200); UI render: Skia/Vulkan;
VCL: win
Locale: en-IN (en_IN); UI: en-US
Calc: threaded
--
You are receiving this mail because:
You are the assignee for the bug.
