While I was trying to port the corrections for [#675] to OmegaT 3.6, I discovered a new bug which, indeed, is also here in OmegaT 4.1
I was using the same case as for ticket [#898]. "Replace all" worked correctly. But then I rolled by project back and tried interactive search.
If I go to a segment which contains two adjacent matches, and try to replace interactively, when I click on "Replace Next", the first match is replaced correctly but then the cursor moves immediately to the match coming after the adjacent match (in other terms, the second match is totally ignored, even if it appeared as selected)
Diff:
Related
Bugs:
#675Bugs:
#898Fixed in trunk, [r10293].
Related
Commit: [r10293]
Fixed in the released version 4.1.4 of OmegaT.
Didier
Backported to branches/release-3-6, [r10345].
Related
Commit: [r10345]
Fixed in the released version 3.6.0 update 10 of OmegaT.
Didier