Keep match boundaries for exempt glossary names
This commit is contained in:
@@ -49,10 +49,11 @@ nonempty, unique `id` identifies a record in evidence. Each record may override
|
||||
Explicit empty lists and null list selections clear a selection.
|
||||
|
||||
Each entry receives its selected context and independent protection. Glossary
|
||||
correction exempts active recognized spellings from protection for that entry;
|
||||
other protected spellings remain protected. A glossary correction must have at
|
||||
least one selected entry at processing preflight. Empty definitions and empty
|
||||
protection remain valid configuration.
|
||||
correction exempts active recognized spellings from protection for that entry.
|
||||
A longer exempt name still takes precedence over a shorter protected spelling
|
||||
inside it. A glossary correction must have at least one selected entry at
|
||||
processing preflight. Empty definitions and empty protection remain valid
|
||||
configuration.
|
||||
|
||||
## Settings
|
||||
|
||||
|
||||
@@ -416,6 +416,8 @@ prepared sibling file, and failed delivery cleans up that file.
|
||||
|
||||
## R12 — P2: Preserve Longest-Match Context for Glossary Exemptions
|
||||
|
||||
**Status:** Completed. Active spellings remain longest-match boundaries without contributing protected identities. Tests cover full-name and span edits, standalone and longer protected terms, stage isolation, and apply-time agreement.
|
||||
|
||||
**Category**
|
||||
|
||||
The new Stage 11 exemption changes how the existing matcher identifies
|
||||
|
||||
Reference in New Issue
Block a user