| Summary: | Spellcheck for subtitles places corrections at the end | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | Jarno van der Kolk <jarno> |
| Component: | Title Clips & Subtitles | Assignee: | Ron <kdenlive-bugs> |
| Status: | CONFIRMED --- | ||
| Severity: | minor | CC: | kdenlive-bugs |
| Priority: | NOR | ||
| Version First Reported In: | 23.08.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Jarno van der Kolk
2023-10-22 01:46:10 UTC
I can't reproduce this with current plasma. Right clicking on "check spelling" gives me a dialog with a 'replace' option, which if clicked correctly replaces the word that was checked. Do you still see this with current releases? Yes that method you are using works for me too. However, what I was referring to was the automatic spellcheck. If you enable that, you will get red underlined words for misspelled words. When you right click on one of those words, it will list a bunch of suggestions. Choosing one of those suggestions causes the original misspelled word to remain and the corrected word will be appended to the end of the text. For completeness sake, I'm now on Kdenlive version 25.04.1. KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Ah, thanks for the clarification. I can confirm that. Though it also doesn't always do it ... at least not in the code in my dev branch which does already have other changes to the subtitle editor, including a few regarding cursor position. Sometimes it replaces the word as expected, and sometimes it places the correction at the end. Will look into it, thanks for catching and reporting this. Interesting. Yeah you maybe already caught some if then. For me, I get it 100% of the time. It did for me at first too, until I started poking at correcting words in the middle of a sentence and moving where the text cursor was when the correction was made - and I didn't see an immediately obvious pattern as to when this bug did or didn't trigger. There's some fancy footwork that goes on in the background which moves the cursor around internally for various reasons, so my first blind guess is it's something to do with it being in the wrong place when this fires. |