Submitter: [Sameh Ragab] Date: [1 August 2026] Product: Trados Studio 2026

Issue Summary

When performing a search in the Editor view using the "Regular Expressions" search mode, the application correctly identifies the segment containing the match but fails to visually highlight the specific text string within that segment that matches the pattern. This makes it extremely difficult to locate the match within long or complex segments. Normal "Find" operations (plaintext searches) do not have this issue.

Steps to Reproduce

1. Open any document for translation in the Studio 2026 Editor view.

2. Ensure the document has text appropriate for the test Regex, for example, a segment containing "(km)" or "(mile)".

3. Press Ctrl + F to open the "Find and Replace" window (or pane).

4. In the "Find what" field, enter the following valid Regex pattern for finding English letters or numbers in brackets: \([a-zA-Z0-9]+\)

5. Change the search type to Regular Expressions (via the dropdown menu or checkbox).

6. Click Find Next.

Expected Behavior

The Editor view should navigate to the next segment containing a match. Crucially, the specific string that matches the pattern (e.g., just the characters "(km)") within that segment should be clearly highlighted, typically with a yellow background, to allow immediate visual identification within the context.

Actual Behavior

The Editor view successfully navigates to the segment containing a match (the segment becomes active or is shown on screen). However, the exact matching text is not highlighted at all. The user is left to manually scan the entire segment text to determine where the match is located.

Business Impact

This defect significantly degrades productivity and usability. The purpose of a search tool is immediate location. Without visual identification of the matching string, users lose valuable time manually searching long or complex segments. This increases cognitive load and can lead to overlooking critical details that the search was intended to prevent, which is exactly why this feature is critical in professional translation workflows.

Additional Notes

This issue appears to be specific to the visual rendering in the Editor view when Regex is engaged. The search engine function is working (as it correctly identifies the segment), but the visual "Found" status for the specific text is not being reflected in the UI.

I hope this can be fixed soon.

Thanks a lot.

Sameh Ragab