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

XLF translate no with different mrk counts lead to unknown mrk tag error

    • Medium
    • The combination of XLF translate = no and a different amount of mrk segments in source and target was triggering erroneously this error.

      problem

      A XLF trans-unit with translate="no" and a different amount of mrk segments in source and target lead to the misleading error:

      editor_Models_Import_FileParser_Xlf_Exception: E1195 - A trans-unit of file "iuiSMALL-de-es.xliff" contains MRK tags other than type=seg, which are currently not supported!

      reason

      This is an implementation error, since for translate=no segment it may happen that seg-source is segmented and target not. This is determined by comparing the node count in source and target - and since this is different in this case translate5 tries to import the whole target - including the mrk tags in the content triggering that error then.

          [TRANSLATE-2776] XLF translate no with different mrk counts lead to unknown mrk tag error

          There are no comments yet on this issue.

            tlauria Thomas Lauria
            tlauria Thomas Lauria
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: