Bug 491782

Summary:	Translation Memory fails to process Czech Summit translation files
Product:	[Applications] lokalize	Reporter:	Vit Pelcak <vit>
Component:	translation memory	Assignee:	Simon Depiets <sdepiets>
Status:	RESOLVED DUPLICATE
Severity:	minor	CC:	aacid, shafff
Priority:	NOR
Version First Reported In:	24.05.2
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Vit Pelcak 2024-08-16 09:22:54 UTC

SUMMARY
I translate KDE to Czech in Lokalize. I used PO Summit to translate all branches easily.

STEPS TO REPRODUCE
1. Have Czech project in patch .../kde/trunk/l10n-support/cs/summit/messages
2. In Lokalize go to translation Memory -> "Manage translation memories" and delete all the translation memories
3. Create -> Give it some name -> OK
4. In Translation Memory tab -> Rescan project files

In my case it thinks that it scanned all files already and will jump right to 100% and won't ever finish.

I clicked Cancel wend back to "Manage translation memories" and noticed that besides the TM I created there is a new one kde-messages. If I delete that one, the whole thing with 100% right from the start and "kde-messages" repeats.

So I decided to delete the one I created and keep kde-messages. Then I ran "Rescan project files" again.

OBSERVED RESULT
The scan started at 0%, added all the files, reached 100% and never finished (at least not after tens of minutes).

Later I noticed that search in TM provided limited results. That suggests some files are not properly saved into TM.

EXPECTED RESULT
After reaching 100% the Rescan normally finishes and search results find all strings.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20240813
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
I noticed there is not Lokalize directory in my HOME dir as I moved to new laptop and copied just configs. Maybe Lokalize fails to save the file because of that. Then I would expect Lokalize to recreate the directory.

Comment 1 Albert Astals Cid 2024-08-17 10:17:11 UTC

4. In Translation Memory tab -> Rescan project files

Did you do add Data before that? Otherwise the translation memory doesn't know where to pick the translations from, no?

Comment 2 Vit Pelcak 2024-08-20 10:09:06 UTC

(In reply to Albert Astals Cid from comment #1)
> 4. In Translation Memory tab -> Rescan project files
> 
> Did you do add Data before that? Otherwise the translation memory doesn't
> know where to pick the translations from, no?

I clicked "Add data". It still creates "kde-messages" but this time empty.

Anyway, core issue - adding files/rescanning - never finishes and translation memory is rather erratic (not being able to find words like "layout").

Comment 3 Albert Astals Cid 2024-08-24 21:21:23 UTC

Besides having to press cancel at the end, seems to work for me

https://youtu.be/Et-c3hLl6g0

You are using 24.05.2, right?

Do you get any output if run from the commandline?

Comment 4 Vit Pelcak 2024-08-26 10:25:45 UTC

There are no suspicious messages in CLI when running Lokalize and refresh of TM.
My issue was, that I was not able to find some strings when searching in TM, the search was not able to find some results.

So I took it that TM data are not saved properly as Lokalize struggles with po parsing.

If it is not the case and it is just cosmetic issue, it is still a bug that you need to cancel adding the data, but with low severity for sure.

Comment 5 Vit Pelcak 2024-08-26 10:26:52 UTC

Forgot to resetthe status. Sorry.

Comment 6 Albert Astals Cid 2024-08-26 22:48:12 UTC

> So I took it that TM data are not saved properly as Lokalize struggles with po parsing.

Does it? What do you mean?

> translation memory is rather erratic (not being able to find words like "layout").

i can find layout just fine https://i.imgur.com/0YWOdoc.png

Comment 7 Vit Pelcak 2024-08-27 07:38:52 UTC

(In reply to Albert Astals Cid from comment #6)
> > So I took it that TM data are not saved properly as Lokalize struggles with po parsing.
> 
> Does it? What do you mean?

That's how I understood it. If it is not the case, fine by me. I have no problem marking the bug as low severity and cance;l the processing of the files after 100% was reached.

> > translation memory is rather erratic (not being able to find words like "layout").
> 
> i can find layout just fine https://i.imgur.com/0YWOdoc.png

Strange. I was not able to do so, but now I can.

Anyway, if TM is processed fine and it is just about to click cancel after reaching 100%, although it is a bug, I am OK with it to stay as low severity.

Comment 8 Albert Astals Cid 2024-08-27 20:22:36 UTC

The not finishing bug is 451461

*** This bug has been marked as a duplicate of bug 451461 ***