Bug 993501 - TMX export contains significant duplication
TMX export contains significant duplication
Status: CLOSED WORKSFORME
Product: Zanata
Classification: Community
Component: Performance (Show other bugs)
development
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Sean Flanigan
Zanata-QA Mailling List
:
Depends On: 980659
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-06 01:13 EDT by Damian Jansen
Modified: 2014-11-19 00:22 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-11-19 00:22:51 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Example tmx (1.85 KB, text/plain)
2013-08-06 01:13 EDT, Damian Jansen
no flags Details
Example chopped tmx (1.07 KB, text/plain)
2013-08-06 01:14 EDT, Damian Jansen
no flags Details

  None (edit)
Description Damian Jansen 2013-08-06 01:13:08 EDT
Created attachment 783182 [details]
Example tmx

Description of problem:
Every translated string has its own copy of
<tu tuid="project:version:path:content.xml:id" srclang="en-us">
<tuv xml:lang="en-us"><seg>Source text</seg></tuv>
...
</tu>

This means that for every single line of $translations-1, there are three unnecessary ones. In characters, in a small file, this equated to more than a third of the entire file being duplication.

Version-Release number of selected component (if applicable):
Dev

How reproducible:
Moderate, always

Steps to Reproduce:
Pre:
- A project version with three languages, and three strings translated
- Signed in as admin
1. Go to project->project version
2. Click Export to tmx
3. Save the file
4. View the file

Actual results:
See tmx1.tmx

Expected results:
See tmx1_chopped.tmx

Additional info:
Comment 1 Damian Jansen 2013-08-06 01:14:05 EDT
Created attachment 783183 [details]
Example chopped tmx
Comment 2 Sean Flanigan 2013-08-06 02:24:36 EDT
I haven't been able to reproduce the problem easily on the tm-import branch, so I recommend testing again after tm-import is merged into master.  There have been some changes in the way we generate TMX, even for translations which weren't imported.
Comment 3 Sean Flanigan 2013-08-06 02:30:59 EDT
Actually, I haven't been able to reproduce the problem using the master branch either.

We need more information about the translation project which is being exported.
Comment 5 Damian Jansen 2014-11-19 00:22:51 EST
Retested, no longer an issue

Note You need to log in before you can comment on or make changes to this bug.