https://bugs.kde.org/show_bug.cgi?id=496278
            Bug ID: 496278
           Summary: Translation memory stops working plus Shortcut
                    Ctrl+Number doesn't work for Translation memory item
    Classification: Applications
           Product: lokalize
           Version: 24.08.3
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Keywords: regression
          Severity: normal
          Priority: NOR
         Component: translation memory
          Assignee: sdepi...@gmail.com
          Reporter: valterm...@gmail.com
                CC: aa...@kde.org, kde-i18n...@kde.org, sha...@ukr.net
  Target Milestone: ---

SUMMARY
During translation process, often the TM stops working and doesn't show the
correct suggestion, even if you are in a translated segment. Also, in this
case, if a memory item is shown in the Translation memory field, sometimes the
combination Ctrl+number of the item doesn't work and cannot insert the picked
item in the translation.

STEPS TO REPRODUCE
1. Open a Translation project in Lokalize with an already populated Translation
Memory
2. Navigate through the segment and work on them.
3. Check if, for translated segments, the suggestions are shown in bold at 100%

OBSERVED RESULT
If not shown in bold, and at 100%, then the TM suggestion is not working and
also the shortcut for insertion (Ctrl+1, Ctrl+2, etc.)

EXPECTED RESULT
The TM should be regularly loaded and work, if a segment is translated it
should show the 100% concordance.
Also, the shortcuts should insert the suggestions, whatever is its score
percentage.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.7-300.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Graphics Processor: NVE7

ADDITIONAL INFORMATION
Usually, if you reload the project, the TM restart working. But once you start
to translate, it stops again.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to