Uploaded image for project: 'Zanata'
  1. ZNTA-421

Reverse the compare order for TM diffs, remove strikeout

    Details

    • Type: Bug
    • Status: Closed (View workflow)
    • Priority: unspecified
    • Resolution: Ready for Release
    • Affects Version/s: None
    • Fix Version/s: platform-4.0.0
    • Component/s: Logic
    • Labels:
    • Sprint:
      16.20, 16.21, 16.19
    • Story Points:
      2

      Description

      User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0
      Build Identifier:

      Whenever a particular string is selected for translation at the editor, the corresponding translation memory suggestions that are displayed on the TM window always shows the entry that is to be inserted to make it a 100% match for the target string as "strike out" and red in colour and the entry to be removed in blue colour. To elaborate, if a TM suggestion is giving 96% match and requires only a single word to be removed and a new word to be inserted in it's place to make it a 100% match, the word to be inserted is shown as "strike out" and red in colour and the word to be removed is shown in blue colour whereas it should have been the other way around, i.e, "strike out" and red for the entry to be removed and blue for the one to be inserted to make it a 100% match. I will attach a screenshot after this bug is filed so that the issue can be understood better.

      Zanata version: 2.0.3

      Reproducible: Always

      Steps to Reproduce:
      1. Login into Zanata
      2. Open a project and go to the editor.
      3. Select a string a look for TM suggestions which are less than 100% match.
      4. Look for the entries that need to be inserted or removed to make a 100% match.
      Actual Results:
      The entry to be inserted is shown as "strike out" and red in colour and the entry to be removed is shown in blue colour.

      Expected Results:
      The entry to be inserted should be shown in blue and the entry to be removed as "strike out" and red in colour.

      This issue has been there in earlier versions too. I have provided the version as 2.0 owing to the current version that I am using which is 2.0.3. If the version number needs to be changed for this bug, kindly do the same.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                aeng Alex Eng
                Reporter:
                ngoswami@redhat.com ngoswami@redhat.com
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: