supervertaler 1.9.132__tar.gz → 1.9.166__tar.gz

{supervertaler-1.9.132 → supervertaler-1.9.166}/CHANGELOG.md

@@ -2,7 +2,589 @@
 
 All notable changes to Supervertaler are documented in this file.
 
-**Current Version:** v1.9.132 (January 20, 2026)
+**Current Version:** v1.9.166 (January 27, 2026)
+
+## v1.9.166 - January 27, 2026
+
+### 🐛 Bug Fixes
+
+- **CRITICAL: TM Write Checkbox Now Works**: Fixed confirmed translations going to "project" TM instead of user-designated TM. The Write checkbox (not Read) now determines where segments are saved. ([#126](https://github.com/michaelbeijer/Supervertaler/issues/126))
+  - **Root Cause**: `save_segment_to_activated_tms()` was using `get_active_tm_ids()` which only returns TMs with the Read checkbox enabled, ignoring the Write setting entirely.
+  - **Fix**: Added new `get_writable_tm_ids()` method that checks for TMs with Write enabled (`read_only = 0`), and updated save logic to use it.
+  - **Now**: Enabling Write checkbox alone (without Read) will save confirmed segments to that TM.
+
+---
+
+## v1.9.165 - January 27, 2026
+
+### ✨ New Features
+
+- **Settings Panel Font Scaling**: Added UI Font Scale setting (80%-200%) in View Settings for better readability on high-DPI/4K displays. Especially useful for macOS users with Retina displays. Click "Apply" for instant preview or save to persist. ([#128](https://github.com/michaelbeijer/Supervertaler/issues/128))
+
+---
+
+## v1.9.164 - January 26, 2026
+
+### 🐛 Bug Fixes
+
+- **macOS/Linux Compatibility**: Fixed `ModuleNotFoundError: No module named 'keyboard'` on non-Windows platforms. The `keyboard` module is Windows-only and is now imported conditionally with graceful fallback. ([#124](https://github.com/michaelbeijer/Supervertaler/issues/124))
+
+---
+
+## v1.9.163 - January 26, 2026
+
+### 🐛 Bug Fixes
+
+- **DOCX Import**: Fixed paragraph style bold/italic not being captured. Headings using styles like "Title" or "Subtitle" now correctly export as bold. Previously only direct run-level formatting was detected.
+- **Termview Font Settings**: Fixed spinbox up/down buttons not visible. Fixed font size changes only applying to bottom Termview, not Match Panel Termview.
+- **View Settings Dialog**: Fixed "Settings Saved" dialog not closing when clicking OK.
+
+---
+
+## 🧪 Cache Kill Switch & Performance Improvements (v1.9.155-162) - January 26, 2026
+
+**Experimental Cache Bypass for Faster Grid Navigation**
+
+This release includes a series of performance optimizations and a new experimental feature for testing grid responsiveness.
+
+### 🧪 NEW: Cache Kill Switch (v1.9.162)
+
+Added experimental setting to bypass all caching systems:
+
+- **Location**: Settings → General → 🧪 Experimental Performance
+- **Option**: "Disable all caches (for testing responsiveness)"
+- **What it does**: Bypasses translation_matches_cache, termbase_cache, prefetch workers
+- **Result**: Direct SQLite lookups - may actually be faster due to no lock contention!
+
+Use this setting to test whether caching is helping or hurting your workflow.
+
+### ⚡ Performance Optimizations (v1.9.155-161)
+
+**Ctrl+Enter Speed Improvements:**
+- Reduced verbose logging overhead (15-20 fewer log calls per navigation)
+- Preview tab now skips TM/glossary lookups entirely (faster reviewing)
+- Idle prefetch system loads matches while you type (Ctrl+Enter feels instant)
+- Direct termbase lookups in prefetch worker (no more race conditions)
+
+**TM Matching Fixes:**
+- Fixed missing fuzzy matches when using multiple TMs (increased FTS5 candidate pool)
+- Fixed crashes when no TMs activated or only "Write" enabled
+- Fixed wrong dictionary key in TM exact match lookups
+
+**Proactive Grid Highlighting (v1.9.161):**
+- Glossary terms now highlight in UPCOMING segments while you work on current one
+- See terms in segments 255, 256, 257 while editing segment 254
+- No more waiting for highlighting after navigation
+
+### 🔧 Bug Fixes
+
+- Fixed batch translation crashes with empty TM lists
+- Fixed TM pre-translation SQLite threading errors (now runs on main thread)
+- Fixed retry pass variable scope issues in batch translate
+- Fixed various logging and debug output issues
+
+---
+
+## 🎯 Match Panel Consolidation (v1.9.154) - January 25, 2026
+
+**Streamlined Right Panel UI**
+
+Replaced the Compare Panel with a more focused Match Panel that combines glossary terms and TM matches in one convenient view.
+
+**What Changed:**
+- **Compare Panel removed**: Was redundant with Translation Results panel
+- **Match Panel introduced**: Combines Termview (glossary) + TM Source/Target boxes
+- **Green TM boxes**: TM matches display with green background (#d4edda) for easy identification
+- **Zoom shortcuts work**: Ctrl+Alt+= and Ctrl+Alt+- now zoom the Match Panel TM boxes
+- **Cleaner tab structure**: Fewer tabs = less switching during translation
+
+**New Right Panel Tabs:**
+1. Translation Results (TM/MT/Glossary matches in list view)
+2. Match Panel (Termview + TM Source/Target side-by-side)
+3. Preview (document preview)
+4. Segment Note
+5. Session Log
+
+**Benefits:**
+- ✅ Less tab clutter - removed redundant Compare Panel
+- ✅ Glossary terms and TM matches visible together in Match Panel
+- ✅ Green highlighting makes TM boxes easy to spot
+- ✅ Keyboard zoom shortcuts work on TM boxes
+
+---
+
+## 📐 Tab Layout Reorganization (v1.9.153) - January 23, 2026
+
+**Better Workflow Organization**
+
+Redesigned the tab layout to consolidate resources and improve translation workflow:
+
+**What Changed:**
+- **Termview stays under grid**: Original position preserved for quick glossary access
+- **Second Termview in right panel**: Duplicate instance so you can see terms while viewing other tabs
+- **Segment Note moved**: Now in right panel alongside Compare Panel and Preview
+- **Session Log moved**: Also in right panel for better organization
+- **Simultaneous updates**: Both Termview instances update together automatically
+
+**New Tab Structure:**
+- **Left panel**: Grid + Termview (collapsible)
+- **Right panel**: Translation Results, Compare Panel, Preview, Segment Note, Session Log, Termview (6 tabs)
+
+**Benefits:**
+- ✅ All reference materials (TM, glossary, notes) in one location
+- ✅ Grid area cleaner - just grid + glossary
+- ✅ Two Termview instances let you see terms while using other tabs
+- ✅ Ctrl+N shortcut still works to jump to Segment Note tab
+
+**Implementation:**
+- New helper method: `_update_both_termviews()` - updates both instances simultaneously
+- Updated 5 locations where Termview gets updated
+- Modified tab creation code to reorganize layout
+- Updated Ctrl+N shortcut to find tab by name (works regardless of tab visibility)
+
+**Future Enhancement (Phase 2):**
+User requested advanced docking: ability to drag tabs to dock them vertically in the right panel (like VS Code). This would require QDockWidget architecture - a significant refactor planned for future version.
+
+---
+
+## ⚡ Instant Glossary Updates (v1.9.152) - January 23, 2026
+
+**Lightning-Fast Term Addition Performance**
+
+Adding terms to glossaries is now instant! The 5-6 second delay when using Alt+Shift+Up/Down shortcuts has been eliminated.
+
+**The Problem:**
+- Users experienced 5-6 second delays after adding glossary terms during translation
+- Long patent sentences with 50+ words required 50+ individual database searches
+- The app was searching for ALL words again just to find the ONE term we just added
+
+**The Solution:**
+- **Direct cache update**: New term added directly to cache instead of full segment re-search
+- **Immediate TermView update**: Display updates instantly using cached matches
+- **Smart highlighting**: Source cell highlighting updated via direct function call
+- **Zero database searches**: We already know what we added - no need to search for it!
+
+**Result:**
+- ✅ TermView shows new term instantly (< 0.1 seconds)
+- ✅ Source highlighting updates instantly
+- ✅ Smooth, responsive workflow for building glossaries
+- ✅ Perfect for intensive patent translation workflows
+
+**Technical Implementation:**
+- Modified `_quick_add_term_with_priority()` to create match entry directly from added term
+- Bypasses expensive `find_termbase_matches_in_source()` database search
+- Calls `highlight_source_with_termbase()` directly with updated cache
+- Maintains all existing functionality while eliminating performance bottleneck
+
+**Files Modified:**
+- `Supervertaler.py` - Optimized glossary quick-add workflow (~60 lines modified)
+
+**🛡️ Exit Crash Fix:**
+- Enhanced `_cleanup_web_views()` method to prevent Python crash on program exit
+- Now properly stops all WebEngine page loading/rendering before cleanup
+- Processes events multiple times and adds delay to ensure Qt finishes cleanup
+- No more "Python has stopped working" dialog when using File → Exit
+
+---
+
+## 🔧 TM Pre-Translation Fixed (v1.9.151) - January 23, 2026
+
+**Critical Fix:** "Pre-translate from TM" batch operation now correctly finds TM matches!
+
+**What Was Broken:**
+- Running Edit → Batch Operations → Pre-translate from TM found 0 matches
+- Even when a 100% TM match was clearly visible in the Compare Panel
+- Issue: SQLite databases cannot be shared across threads
+
+**Root Cause:**
+The `PreTranslationWorker` ran in a background thread, but SQLite connections created in the main thread cannot be used in other threads. This caused a `sqlite3.ProgrammingError`.
+
+**The Fix:**
+- TM pre-translation now runs **on the main thread** (same as the Compare Panel)
+- Uses `QProgressDialog` to show progress and keep UI responsive
+- Uses the **exact same database methods** that work for segment navigation
+- No more SQLite threading errors!
+
+**Before:** "Pre-translate from TM" → 0 matches found
+**After:** "Pre-translate from TM" → Correctly finds all TM matches
+
+## 🔍 Superlookup Language-Aware Search Enhancement (v1.9.149-beta) - January 22, 2026
+
+**Major Enhancement:** Superlookup TM search now intelligently handles language filters!
+
+**What Changed:**
+- **Intuitive Language Filters**: "From: Dutch → To: English" now means "Search FOR Dutch text and show me English translations"
+- **Smart Column Detection**: Searches ALL TMs regardless of their stored direction (NL→EN or EN→NL)
+- **Automatic Swapping**: Finds text in either column and automatically presents results in the correct order
+- **More Powerful Than Traditional CAT Tools**: Unlike memoQ/Trados that only search one TM direction, Supervertaler finds matches everywhere
+
+**How It Works:**
+1. Set "From: Dutch → To: English"
+2. Search for Dutch text
+3. System searches both NL→EN TMs (source column) AND EN→NL TMs (target column)
+4. Results automatically shown with Dutch in source, English in target
+
+**UI Simplification:**
+- **Removed Direction radio buttons** (Both/Source/Target) - always searches both columns now
+- Cleaner, faster interface for translators
+- Language dropdowns are all you need
+
+**UI Polish:**
+- **Renamed "QuickMenu" tab to "Prompt Manager"** - Better clarity for new users looking for translation prompts
+- **Sub-tab renamed**: "Library" → "Prompt Library"
+- Resolves confusion about where to find prompts for single-segment and batch translation
+
+**Technical Details:**
+- Language filters no longer restrict which TMs are searched
+- Post-processing validates search text is in the correct language column
+- Smart swapping ensures results always match user's requested language direction
+
+**Files Modified:**
+- `modules/database_manager.py` - Smart language-aware concordance search
+- `modules/superlookup.py` - Column name handling
+- `Supervertaler.py` - Removed Direction controls, simplified UI, renamed QuickMenu to Prompt Manager
+- `modules/unified_prompt_manager_qt.py` - Updated tab and header labels
+
+---
+
+## 📁 User-Choosable Data Folder Location (v1.9.148-beta) - January 21, 2026
+
+**Major Enhancement:** Users now choose where to store their data on first run!
+
+**What Changed (from v1.9.147):**
+- v1.9.147 stored data in hidden AppData folders - users couldn't easily find/backup their data
+- v1.9.148 uses visible, accessible locations that users control
+
+**The New System:**
+
+| Platform | Default Location |
+|----------|------------------|
+| **Windows** | `C:\Users\Username\Supervertaler\` |
+| **macOS** | `~/Supervertaler/` |
+| **Linux** | `~/Supervertaler/` |
+
+**Key Features:**
+- **First-run dialog** lets users choose their data folder location
+- **Default is visible** in home folder - easy to find and backup
+- **Settings → General** includes "Change..." button to relocate data anytime
+- **Auto-recovery** if config pointer is deleted but data exists at default location
+- **Unified system** - ALL users (pip, EXE, dev) use the same approach
+
+**How It Works:**
+1. On first run, a dialog asks where to store data
+2. User choice is saved to a small config pointer file:
+   - Windows: `%APPDATA%\Supervertaler\config.json`
+   - macOS: `~/Library/Application Support/Supervertaler/config.json`
+   - Linux: `~/.config/Supervertaler/config.json`
+3. This pointer just contains: `{"user_data_path": "C:\\Users\\John\\Supervertaler"}`
+4. If pointer is deleted, app auto-recovers by checking the default location
+
+**Benefits:**
+- ✅ Data is visible and easy to find
+- ✅ Easy to backup (just copy the folder)
+- ✅ User has full control over location
+- ✅ Can use cloud folders (OneDrive, Dropbox, etc.)
+- ✅ Survives pip upgrades
+- ✅ Works identically for all installation types
+
+---
+
+## 📁 Persistent User Data Location (v1.9.147) - January 21, 2026
+
+*Note: v1.9.148 improves on this by using visible locations and adding user choice.*
+
+**Major Enhancement:** User data (API keys, TMs, glossaries, prompts, settings) now persists across pip upgrades!
+
+**The Problem:**
+- When users ran `pip install --upgrade supervertaler`, their data was wiped
+- This happened because user_data/ was stored inside the pip package directory
+- pip replaces the entire package directory on upgrade, deleting all user files
+
+---
+
+## 🔑 Gemini/Google API Key Alias Fix (v1.9.146) - January 21, 2026
+
+**Bug Fix:** Fixed "Gemini API Key Missing" error when users had `google=...` instead of `gemini=...` in their api_keys.txt file.
+
+**The Problem:**
+- Users could use either `google=YOUR_KEY` or `gemini=YOUR_KEY` in api_keys.txt
+- Some code paths only checked for `gemini`, others only for `google`
+- This caused confusing "API Key Missing" dialogs even when keys were properly configured
+
+**The Solution:**
+- Added **automatic normalization** in `load_api_keys()` - if either `google` or `gemini` is set, both keys are now populated
+- Users can use either name interchangeably
+- Fixed 6+ locations where the alias wasn't being handled correctly:
+  - Single segment translation (Ctrl+T)
+  - Batch translation
+  - QuickMenu prompts
+  - Async LLM fetch for Translation Results panel
+  - Proofreading (also fixed `anthropic` → `claude` provider name bug)
+
+**For Users:**
+- Both `google=YOUR_KEY` and `gemini=YOUR_KEY` now work identically
+- No action needed - existing api_keys.txt files will continue to work
+
+---
+
+## ✨ memoQ-Style Track Changes in Compare Panel (v1.9.145) - January 20, 2026
+
+**Improvement:** Changed Compare Panel diff highlighting to match memoQ's "Track changes view" style.
+
+**New Styling (memoQ-style):**
+- **Deletions**: Red text + strikethrough (~~deleted~~)
+- **Insertions**: Red text + underline (<u>inserted</u>)
+- **Unchanged**: Normal text
+
+This is cleaner and more familiar to translators who use Word's track changes or memoQ.
+
+**Example:**
+```
+Current: In een derde aspect betreft de huidige uitvinding het gebruik van een dichtingskit...
+TM:      In een tweede aspect betreft de huidige uitvinding een dichtingskit...
+
+Compare Panel shows:
+In een ~~tweede~~ derde aspect betreft de huidige uitvinding het gebruik van een dichtingskit...
+        ^^^^^^^^  ^^^^^^                                      ^^^^^^^^^^^^^^^^
+        red+strike red+under                                  red+underline
+```
+
+---
+
+## ✨ Enhanced Compare Panel Diff Highlighting (v1.9.144) - January 20, 2026
+
+**Improvement:** The Compare Panel now shows a complete diff with additions, deletions, and changes - matching what professional CAT tools display.
+
+**Before:**
+- Only showed text that was **different** (in red)
+- Didn't show what was **added** in the current segment
+- Hard to understand what changed between TM source and current source
+
+**After:**
+- **Red with strikethrough**: Text in TM that was changed/deleted in current segment
+- **Green background**: Text in current segment that was added (not in TM)
+- **Normal text**: Identical text in both
+
+**Example:**
+```
+Current: In een derde aspect betreft de huidige uitvinding het gebruik van een dichtingskit...
+TM:      In een tweede aspect betreft de huidige uitvinding een dichtingskit...
+
+Compare Panel now shows:
+In een [tweede→derde] aspect betreft de huidige uitvinding [+het gebruik van] een dichtingskit...
+```
+
+**Technical:**
+- Changed from character-level to word-level diffing for better readability
+- Additions shown inline in green where they would appear
+- Deletions shown with strikethrough so you can see what was removed
+
+---
+
+## 🐛 Fix: Deleting Glossary Entry from Termview (v1.9.143) - January 20, 2026
+
+**Bug Fix:** Deleting glossary entries via right-click in Termview failed with an error.
+
+**Error in Logs:**
+```
+✗ Error deleting glossary entry from database: 'DatabaseManager' object has no attribute 'get_connection'
+```
+
+**Root Cause:**
+- The delete handler was trying to call `db_manager.get_connection()` which doesn't exist
+- Was using raw SQL instead of the existing `termbase_mgr.delete_term()` method
+
+**The Fix:**
+- Changed to use `self.termbase_mgr.delete_term(term_id)` which already exists and works correctly
+
+---
+
+## 🐛 Fix: Error When Editing Glossary Entry from Termview (v1.9.142) - January 20, 2026
+
+**Bug Fix:** After editing a glossary entry via right-click → Edit in Termview, an error would occur preventing proper refresh.
+
+**Error in Logs:**
+```
+Error refreshing segment matches: SupervertalerQt.on_cell_selected() missing 2 required positional arguments: 'previous_row' and 'previous_col'
+```
+
+**Root Cause:**
+- The `_refresh_current_segment_matches()` method was calling `on_cell_selected(current_row, 2)` with only 2 arguments
+- But `on_cell_selected()` requires 4 arguments: `current_row`, `current_col`, `previous_row`, `previous_col`
+
+**The Fix:**
+- Simplified `_refresh_current_segment_matches()` to use the targeted `_refresh_termbase_display_for_current_segment()` method
+- This method already handles termbase cache clearing and display refresh correctly
+
+---
+
+## 🐛 Fix: Termview Blank After Adding Glossary Term (v1.9.141) - January 20, 2026
+
+**Bug Fix:** After adding a term to a glossary via Alt+Down (or similar shortcuts), the Termview pane would go blank and stay blank until navigating to another segment.
+
+**Error in Logs:**
+```
+Error updating termview: list index out of range
+```
+
+**Root Cause:**
+- The `_refresh_termbase_display_for_current_segment()` method (added in v1.9.140) was using incorrect dictionary keys
+- `find_termbase_matches_in_source()` returns dict with keys `source` and `translation`
+- But the refresh method was looking for keys `source_term` and `target_term`
+- This resulted in empty strings being passed to the termview, causing the index error
+
+**The Fix:**
+- Changed `match.get('source_term', '')` → `match.get('source', '')`
+- Changed `match.get('target_term', '')` → `match.get('translation', '')`
+- Applied same fix to Translation Results panel update section
+
+---
+
+## 🐛 Fix: Adding Glossary Term No Longer Triggers TM Search (v1.9.140) - January 20, 2026
+
+**Performance Fix ([#118](https://github.com/michaelbeijer/Supervertaler/issues/118)):** Adding a term to a glossary was unnecessarily triggering a full Translation Memory search, causing delays.
+
+**The Problem:**
+- When adding a term via Ctrl+E, Ctrl+Q, or Ctrl+Shift+1/2, the app cleared BOTH caches and called `on_cell_selected()`
+- This triggered a complete TM search even though adding a glossary term doesn't change the source/target text
+
+**The Fix:**
+- Created new targeted method `_refresh_termbase_display_for_current_segment()`
+- Only clears the termbase cache (not TM cache)
+- Updates TermView widget with fresh glossary matches
+- Updates Translation Results panel's Termbases section only
+- Re-highlights termbase matches in source cell
+- TM results remain untouched
+
+**Also in this release:**
+- 🎤 Renamed "Voice OFF/ON" button to "Voice Commands OFF/ON" for clarity
+- 🎤 Renamed "Dictate" button to "Dictation"
+
+---
+
+## 📐 Auto-Sizing Segment Number Column (v1.9.138) - January 20, 2026
+
+**Grid UX Improvement:** The segment number column (#) now automatically sizes itself based on:
+- The current font size (scales when you zoom in/out)
+- The number of segments in the project (fits 3-digit, 4-digit numbers, etc.)
+
+Uses Qt font metrics to calculate the exact pixel width needed. No more truncated numbers or wasted space!
+
+**Also in this release:**
+- Status column made slightly narrower (70px → 60px)
+
+---
+
+## 🏷️ Termview Punctuated Terms Fix (v1.9.138) - January 20, 2026
+
+**Fixed: Glossary terms with punctuation now appear in Termview**
+
+Glossary entries like "ca." (with period) or "typisch" (when appearing in parentheses as "(typisch)") were found by the termbase search (grid showed green highlighting) but did NOT appear in the Termview pane.
+
+**Root Cause - Key Mismatch:**
+- `matches_dict` keys were built using the raw source term: `"ca."` (with period)
+- But lookup stripped punctuation from tokens: `"ca."` → `"ca"`
+- Result: `matches_dict.get("ca")` returned nothing because the key was `"ca."`
+
+**The Fix:**
+- When building `matches_dict`, keys are now normalized by stripping punctuation
+- Both the dictionary keys and lookup keys now use the same normalization
+- Added brackets `()[]` to punctuation chars so "(typisch)" matches "typisch"
+
+**Files Modified:**
+- `modules/termview_widget.py` - Normalize punctuation in `matches_dict` keys and lookup
+
+---
+
+## 🔧 Termview Race Condition Fix (v1.9.137) - January 20, 2026
+
+**Fixed: Glossary terms now appear in Termview pane**
+
+When navigating to a segment, the Termview pane showed "No glossary matches" even though:
+- The grid highlighted terms in green (glossary highlighting worked)
+- Force Refresh (F5) would then show the terms correctly
+
+**Root Cause - Timing/Race Condition:**
+- `update_tab_segment_editor()` was called EARLY in the cell selection process
+- It tried to read from `termbase_cache[segment_id]` to update Termview
+- But the termbase search (`find_termbase_matches_in_source()`) hadn't run yet!
+- Result: Termview called with empty list before matches were found
+
+**The Fix:**
+1. Removed premature Termview update from `update_tab_segment_editor()` 
+2. Termview is now updated ONLY after the termbase search completes in `_on_cell_selected_full()`
+3. Also fixed: Termview now updates even when no matches found (shows "No matches" state)
+
+**Files Modified:**
+- `Supervertaler.py` - Removed premature Termview update, fixed condition to always update Termview
+- `modules/termview_widget.py` - Removed debug logging
+
+---
+
+## 📚 Glossary Matching Fix for Punctuation (v1.9.136) - January 20, 2026
+
+**Fixed: Glossary terms with trailing punctuation now match correctly**
+
+Glossary entries like "ca." (with period), "psi", and "typisch" were not being found in the Termview window when they appeared in source text like "ca. 2,2 (270 psi)".
+
+**Root Cause:**
+- When tokenizing source text, punctuation was stripped from words ("ca." → "ca")
+- The database search then looked for "ca" but the glossary had "ca." — no match
+- Short terms in parentheses like "(psi)" were also affected
+
+**The Fix:**
+1. Now searches for BOTH the stripped word AND the original word with punctuation
+2. Database query enhanced with reverse matching: finds glossary terms where the search word matches the term with trailing punctuation stripped
+3. Handles entries like "ca.", "gew.%", "psi", etc.
+
+**Files Modified:**
+- `Supervertaler.py` - Enhanced `find_termbase_matches_in_source()` to search with original punctuation
+- `modules/database_manager.py` - Enhanced `search_termbases()` with punctuation-tolerant matching
+
+---
+
+## 🔍 Filter Now Searches Entire Document (v1.9.135) - January 20, 2026
+
+**Fixed: Filter Source/Target boxes now search across ALL pages**
+
+Previously, the Filter Source and Filter Target boxes above the grid would only search within the currently visible page. If the text you were looking for was on a different page, it wouldn't be found.
+
+Now, filtering searches through the **entire document** regardless of pagination. When a filter is active, ALL matching rows are displayed (pagination is temporarily ignored). When you clear the filter, normal pagination resumes.
+
+**Files Modified:**
+- `Supervertaler.py` - Fixed `_apply_pagination_to_grid()` to show all filter matches
+
+---
+
+## 🔊 Fuzzy TM Match Sound Effect (v1.9.134) - January 20, 2026
+
+**New sound effect option: "Fuzzy TM match found"**
+
+Plays when navigating to a segment and a fuzzy TM match (50-99%) is found, but NO 100% match exists.
+
+**Access:** Settings → General → Sound Effects → "Fuzzy TM match found"
+
+Disabled by default (set to "None"). Works with the same sound options as other effects.
+
+---
+
+## 🔊 New Sound Effects (v1.9.133) - January 20, 2026
+
+**Two new sound effect options added:**
+
+1. **Segment confirmed** - Plays when you confirm a segment with Ctrl+Enter
+2. **100% TM match alert** - Plays when navigating to a segment and a 100% TM match is found and auto-inserted
+
+**Access:** Settings → General → Sound Effects
+
+Both sounds are disabled by default (set to "None"). Users can configure them to any of the available Windows system sounds:
+- OK, Asterisk, Exclamation, Hand, Question
+- Windows .wav files: Restore, Navigation Start, Speech Disambiguation, etc.
+
+**Files Modified:**
+- `Supervertaler.py` - Added sound effect options and trigger points
+
+---
 
 ## 🐛 Ctrl+K Superlookup Shortcut Fix (v1.9.132) - January 20, 2026
 

{supervertaler-1.9.132 → supervertaler-1.9.166}/FAQ.md

@@ -1136,9 +1136,9 @@ Michael Beijer, a professional translator, created Supervertaler to:
 - **Google Gemini:** Check current API terms for data retention
 
 **Local Storage:**
-- Projects: `user_data/Projects/`
-- TMs: `user_data/tm/`
-- Termbases: `user_data/termbases/`
+- Projects: `user_data/projects/`
+- TMs: `user_data/resources/`
+- Termbases: `user_data/resources/`
 - All data remains on your machine
 
 **No Telemetry:**