Bug 834136

Summary:	[Translation Memory] - disappears when the files are renamed
Product:	[Retired] Zanata	Reporter:	Yuko Katabami <ykatabam>
Component:	Usability	Assignee:	Runa Bhattacharjee <runab>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ding-Yi Chen <dchen>
Severity:	high	Docs Contact:
Priority:	high
Version:	1.6	CC:	ankit, ccheng, damason, mospina, zanata-bugs
Target Milestone:	---
Target Release:	1.6.2
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	1.6.2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-19 01:16:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 2 Manuel Ospina 2012-06-21 00:08:14 UTC

The Translation Memory shows the old strings (from the 3.0 version), but the strings that were translated for 3.1 disappeared when the new pushed was done. They should appear in the TM at least.

In the meanwhile, is there anyway to retrieve those translations from the Database?

Comment 4 David Mason 2012-06-22 00:14:47 UTC

If the filename is changed, Zanata does not assume that the new file is the same as the old one. Copytrans is designed to pick up translations from other versions of the same project, but I think it is too strict at the moment to pick up translations from a moved file. We have a few features in development that will help with this, but at the moment the most effective way to re-use the translations would be to pull all translations before moving the file, move the file and its translations, then push the new source file with all the existing translations.

I have a database backup from Tuesday, so if the move was done after Tuesday I should be able to recover translations from before the backup was made. I'm not sure about recovering anything between the backup and the move.

Comment 7 David Mason 2012-07-19 01:16:15 UTC

This is likely a side-effect of memory issues in https://bugzilla.redhat.com/show_bug.cgi?id=835457

Closing as the fix to memory issues is already deployed to production.