Offer export of Trados-Style analysis xml

Next to the Excel export button a button to export "Trados style XML" is implemented.

The format of the file should look structurally like the attached one, except

• no file elements, since translate5 does not support a file specific analysis right now
• for the settings element the following values should be set: <settings reportInternalFuzzyLeverage="translate5Value" reportLockedSegmentsSeparately="no" reportCrossFileRepetitions="yes" minimumMatchScore="lowestFuzzyValueThatIsConfiguredToBeShownInTranslate5" searchMode="bestWins"/>
• the following Trados-specific attributes of the settings element are fully omitted:
  missingFormattingPenalty="1" differentFormattingPenalty="1" multipleTranslationsPenalty="1" autoLocalizationPenalty="0" textReplacementPenalty="0" fullRecallMatchedWords="2" partialRecallMatchedWords="n/a" fullRecallSignificantWords="2" partialRecallSignificantWords="n/a"
• In the batchTotal analysis section the following applies
  • For the following elements all numeric attributes are always set to "0", because they have no analogon currently in translate5:
    • locked
    • perfect
    • repeated (we only have crossFileRepeated)
    • newBaseline (this is specific to SDL MT)
    • newLearnings (this is specific to SDL MT)
  • the number and definitions of fuzzy elements will reflect the fuzzy ranges as defineable with TRANSLATE-2076
  • all MT matches will always be counted within "new"
  • crossFileRepeated are translate5s repetitions (which are represented by 102% matches)
  • exact are 100% and 101% and 104%-Matches from translate5, since Trados does not know our 101 and 104%-Matches
  • inContextExact are 103%-Matches from translate5
  • The following attributes will always have the value "0", since translate5 does not support them right now:
    • characters="0" placeables="0" tags="0" repairWords="0" fullRecallWords="0" partialRecallWords="0" edits="0" adaptiveWords="0" baselineWords="0"
  • The following attributes will be ommitted, because translate5 does not support them so far:
    • segments

The above definitions (what we count in where) should always be explained within an xml comment within each exported Trados-like xml analysis file.