Bug 305542

Summary:	take into account &bla-bla when showing results of a search in Translation Memory
Product:	[Applications] lokalize	Reporter:	Freek de Kruijf <freekdekruijf>
Component:	translation memory	Assignee:	Nick Shaforostoff <shafff>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	adrian
Priority:	NOR
Version First Reported In:	1.4
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	nl/messages/kdenetwork/kopete.po nl/docmessages/kdenetwork/kopete_jabber.po

Description Freek de Kruijf 2012-08-21 10:37:40 UTC

I have in trunk nl/docmessages/kdenetwork/kopete_jabber.po open. I press F7 to open TM and enter in Source "*Desired*", in File mask "*kopete*", both without the double quotes, I also check Wildcard and press Search. Now the display window shows Source and Target elements that are incomplete.
I.e. the source shows "Desired Jabber" however, right clicking on it and choosing "Copy source to clipboard" the real source "Desired Jabber &ID:" is shown. Also the target shows "Gewenste" where right clicking on it and choosing "Copy target to clipboard" gets "Gewenste Jabber-&ID:"

Reproducible: Always

Steps to Reproduce:
1. see above
2.
3.
Actual Results:  
Incomplete messages and translations are shown.

Expected Results:  
Complete messages and translations

Comment 1 Freek de Kruijf 2012-08-21 10:40:54 UTC

Created attachment 73348 [details]
nl/messages/kdenetwork/kopete.po

Comment 2 Freek de Kruijf 2012-08-21 10:45:19 UTC

Created attachment 73349 [details]
nl/docmessages/kdenetwork/kopete_jabber.po

Probably when putting these two files in a project and generating a TM from it, the problem can be reproduced. Will try later.

Comment 3 Freek de Kruijf 2012-08-22 14:10:34 UTC

I did try a lokalize project with these two files and its own TM database and got the same results.
I also did a search in the full TM with "Exclude from connect all" and found one match which was displayed as "E&xclude from", so apparently & is skipped in the match, which is very convenient. However I would expect the full text to be shown.

Comment 4 Adrián Chaves (Gallaecio) 2019-09-01 19:56:33 UTC

I cannot reproduce this issue in the latest version of Lokalize. The example string still exists, so the original steps can be reproduced as is, but I do get “Desired Jabber &ID:” in the source column and the complete translation in the target column.

Comment 5 Bug Janitor Service 2019-09-16 04:33:07 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Freek de Kruijf 2019-09-16 10:56:25 UTC

(In reply to Adrián Chaves (Gallaecio) from comment #4)
> I cannot reproduce this issue in the latest version of Lokalize. The example
> string still exists, so the original steps can be reproduced as is, but I do
> get “Desired Jabber &ID:” in the source column and the complete translation
> in the target column.

I tied to reproduce the bug. The first time lokalize just exited without any error message. Restarting it again was as if nothing strange had happened before. So I performed to reproduce again, and went OK. So I consider this resolved.