Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Feature: Enhance Version Merge feature

Description

Implementation for https://zanata.atlassian.net/browse/ZNTA-1839#icft=ZNTA-1839

  • Explaination of what threshold of percentage means, example string

PLUS Version TM Design:

This will be a version based TM merge, which uses lucene search.
For that we will need to update the UI component to include
1) Threshold selection
2) All the existing options in editor TM Merge except for "On Project Name mismatch". Below is the old TM merge screen and I believe Kathyrn have put up a newer version, we should just based off from the newer one.
Inline image 2

The existing version merge will remain the same.
The existing TM merge in editor will remain the same.

Notes

  • If no project version is selected, this will not copy from internal TM

  • New option of "Copy from all projects" to allow user to copy from internal TM

  • Test case for tm merge of pluralforms from TMX

  • Clean up story component for this modal (update it if its reusable, remove if its only mockup)

Attachments

4
  • 24 Jul 2017, 03:12 am
  • 19 Jul 2017, 03:58 am
  • 01 Jun 2017, 03:50 am
  • 22 May 2017, 09:10 am

Activity

Show:

Former user 1 June 2017 at 03:53
Edited

and

The description says it would contain all options from editor TM merge except "from different project". In the new version TM design, there is only percentage threshold there. What do we do with "context mismatch", "document mismatch" and "from imported TM"? Do we assume the options to "downgrade to fuzzy"? Note the context mismatch will contradict the other new option "if context match but content doesn't, copy as fuzzy".

Sean Flanigan 23 May 2017 at 00:39

Looks good!

Sean Flanigan 22 May 2017 at 06:59

With the first paragraph in the dialogue:

This feature copies existing translations from similar documents in other projects and versions into this project version. The Translation state will be preserved (Translated or Approved).

[x] If metadata matches but source string does not, copy as Fuzzy.

This doesn't explicitly state what happens if the metadata and source string both match. I think we need to append "if the source text and metadata both match" to the first sentence.

This feature copies existing translations from similar documents in other projects and versions into this project version if the source text and metadata both match. The Translation state will be preserved (Translated or Approved).

[x] If metadata matches but source string does not, copy as Fuzzy.

We could also consider replacing the word "metadata" with "context" (two places), and change "source string" -> "source text".

Former user 19 May 2017 at 07:43
Edited


Version TM mockups as discussed via email

1.1 - current project shown by default

Preview unavailable

1.2 - versions of current project selected, version 2.0 selected for dragging

Preview unavailable

2.1 - search results shown

Preview unavailable

2.2 - tooltip shown

Former user 11 May 2017 at 02:09

No problem, shall update the mockups

Ready for Release

Details

Assignee

Reporter

Labels

Tested Version/s

Story Points

Components

Sprint

Fix versions

Priority

More fields

Created 11 April 2017 at 21:33
Updated 27 June 2018 at 02:15
Resolved 20 July 2017 at 07:23
Configure

Flag notifications