Weblate - missing suggestions from translation memory?

l10n
#1

Hi,

when translating new strings in Weblate, I encounter that the suggestions from translation memory are not reliable.

For instance, I have two Help strings [1] and [2] that were affected only by the change from "%PRODUCTNAME Macros" to "Application Macros" (this commit: [3]) - so I would expect that the previous translations for "%PRODUCTNAME" will be offered by the suggestions from translation memory.

It works perfectly for the string [1], whereas for the string [2], after a long time of loading (about few minutes, which is not acceptable anyway) no suggestion is received.

The workaround is clear: I have to go to old downloaded translated files, find the string there and copy the old translation - not needed to mention that the effectivness of the translation process is gone. I experience that this happens for longer, but also for too short strings.

Could anyone confirm this or look at it? I am afraid that this can waste many already translated strings that could be easily modified and used...

Thank you,
Stanislav

[1] https://translations.documentfoundation.org/translate/libo_help-master/textsbasicshared/cs/?sort_by=-priority%2Cposition&offset=3750

[2] https://translations.documentfoundation.org/translate/libo_help-master/textsbasicshared/cs/?sort_by=-priority%2Cposition&offset=3756

[3] https://github.com/LibreOffice/help/commit/e1da23a649197d960c8492373326e11286b3239e

#2

Hi Stan

Hi,

when translating new strings in Weblate, I encounter that the suggestions from translation memory are not reliable.

I also have very poor match from translation memory. When nothing comes out, or a poor match is thrown, I call Google translator to return better match for pt-BR, saving me a lot of typing effort.

In my case (pt-BR), machine translation supersedes weblate translation memory.

Regards

#3

Hi,

Dne 19. 02. 22 v 22:46 Olivier Hallot napsal(a):

Hi Stan

Hi,

when translating new strings in Weblate, I encounter that the suggestions from translation memory are not reliable.

I also have very poor match from translation memory. When nothing comes out, or a poor match is thrown, I call Google translator to return better match for pt-BR, saving me a lot of typing effort.

In my case (pt-BR), machine translation supersedes weblate translation memory.

yes, I agree that machine translation is powerful and this reminds me another idea: on hosted Weblate [1] (where also Collabora Online is hosted), also machine translations (from Google, Microsoft and my favourite DeepL) are shown in "Automatic suggestions".

Would it be possible to add this feature also to TDF's Weblate? Or - if it was already considered, what was the conclusion about it?

Best regards,
Stanislav

[1] https://hosted.weblate.org/

#4

Hi Stanislav,

Hi,

when translating new strings in Weblate, I encounter that the suggestions from translation memory are not reliable.

For instance, I have two Help strings [1] and [2] that were affected only by the change from "%PRODUCTNAME Macros" to "Application Macros" (this commit: [3]) - so I would expect that the previous translations for "%PRODUCTNAME" will be offered by the suggestions from translation memory.

It works perfectly for the string [1], whereas for the string [2], after a long time of loading (about few minutes, which is not acceptable anyway) no suggestion is received.

About the delay, I'm asking our infra team to have a look. Although for me Weblate is sometimes slow, I've never had such a long wait compared to your sting [2]. Does anybody else have such long delay in displaying automatic suggestions?

The workaround is clear: I have to go to old downloaded translated files, find the string there and copy the old translation - not needed to mention that the effectivness of the translation process is gone. I experience that this happens for longer, but also for too short strings.

Could anyone confirm this or look at it? I am afraid that this can waste many already translated strings that could be easily modified and used...

I don't experience the same, but it seems Olivier has the same feedback. I'll also ask infra team to have a look.

On adding other sources of suggestions, I'll add the topic to our team meeting tomorrow to discuss the possibilities.

Cheers
Sophie

#5

Hi Stanislav,

Hi,

when translating new strings in Weblate, I encounter that the suggestions from translation memory are not reliable.

For instance, I have two Help strings [1] and [2] that were affected only by the change from "%PRODUCTNAME Macros" to "Application Macros" (this commit: [3]) - so I would expect that the previous translations for "%PRODUCTNAME" will be offered by the suggestions from translation memory.

We discussed your issue yesterday during our team meeting and Cloph removed older projects from the search. For me now, string [2] displays automatic suggestions and in a reasonable delay. Could you have a look and tell me if it's better for you too?

Cheers
Sophie

#6

Hi Sophie

About the delay, I'm asking our infra team to have a look. Although for me Weblate is sometimes slow, I've never had such a long wait compared to your sting [2]. Does anybody else have such long delay in displaying automatic suggestions?

I have this ~10 seconds delay, and for information here is a list of sources returned by the memory translation of (1):

Weblate Translation Memory (Compartilhada: libo_help-7-0/textscalc01)
Weblate Translation Memory (Projeto: libo_help-master/textscalc01)
Weblate Translation Memory (Compartilhada: libo_help-master/textscalc01)
Weblate Translation Memory (Compartilhada: libo_help-7-1/textscalc01)
Weblate Translation Memory (Compartilhada: libo_help-7-2/textscalc01)
Weblate Translation Memory (Compartilhada: libo_help-7-3/textscalc01)

Unless there is a smart search that I missed, it seems to show a scan on 6 memories. Isn't that too much?

Regards
Olivier
(1) https://translations.documentfoundation.org/translate/libo_help-master/textswriter01/pt_BR/?&offset=3

#7

Hi Olivier,

Hi Sophie

About the delay, I'm asking our infra team to have a look. Although for me Weblate is sometimes slow, I've never had such a long wait compared to your sting [2]. Does anybody else have such long delay in displaying automatic suggestions?

I have this ~10 seconds delay, and for information here is a list of sources returned by the memory translation of (1):

Weblate Translation Memory (Compartilhada: libo_help-7-0/textscalc01)
Weblate Translation Memory (Projeto: libo_help-master/textscalc01)
Weblate Translation Memory (Compartilhada: libo_help-master/textscalc01)
Weblate Translation Memory (Compartilhada: libo_help-7-1/textscalc01)
Weblate Translation Memory (Compartilhada: libo_help-7-2/textscalc01)
Weblate Translation Memory (Compartilhada: libo_help-7-3/textscalc01)

Unless there is a smart search that I missed, it seems to show a scan on 6 memories. Isn't that too much?

We were talking about [2] in Czech as there are suggestions in French and it seems in Brazilian too but nothing in Czech (I think the search was abandoned). I'd like a first confirmation that we are heading in the good way, taking the same issue Stanislav met and reproduce it or not after tweaking different settings.
Cheers
Sophie

#8

Hi,

Dne 23. 02. 22 v 11:09 sophi napsal(a):

We discussed your issue yesterday during our team meeting and Cloph removed older projects from the search. For me now, string [2] displays automatic suggestions and in a reasonable delay. Could you have a look and tell me if it's better for you too?

thanks for the investigation, however for me it is still the same for the string [2] - it took too long (between 5 and 10 minutes) and no suggestion was shown.

Best regards,
Stanislav