Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-2117

LanguageResources: update & query segments with tags

    XMLWordPrintable

Details

    • High
    • -

    Description

      Currently, NEC-TM "saves only segments with tags". The problem is:

      The results are not found after updating because the query looks for a different string than the update handles:

      • query:
        • currently with with prepareDefaultQueryString():
          across tags outside from mrk test
        • we also could use getQueryString():
          <div class="single 70682069643d2231222061783a656c656d656e742d69643d2230223e266c743b705f696e2667743b3c2f7068 internal-tag ownttip"><span title="<ph id="1" ax:element-id="0"><p_in></ph>" class="short"><1/></span><span data-originalid="4be77c53486417926f2569a91ee0626a" data-length="-1" class="full"><ph id="1" ax:element-id="0"><p_in></ph></span></div>across tags outside from mrk test
        • GENERAL SOLUTION: use tags in the same format as we got them in the import, e.g. <x id="1"/>
      • update:
        • Current handling for NEC-TM: <x id="1"/>
          GENERAL SOLUTION: use tags in the same format as we got them in the import, e.g. <x id="1"/>

      There seems to be a similar problem with PangeaMTs (TRANSLATE-2118).

      So with this issue please ensure, that for NEC-TM the query and update calls and for PangeaMT the query calls are always done with internal tags in the format, that they had in the imported xliff (see comment below for an idea).

      Do not implement the solution for each Service separately, but handle as much as possible in general!

      Attachments

        Issue Links

          Activity

            People

              aleksandar Aleksandar Mitrev
              Ines-Paul Ines-Paul Baumann (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: