Basic architecture

• beo-transit-classes should be used and translate5-License and beo-copyright included in them (code contribution of beo). Also a note of changes made by MittagQI should be included.
• task-data-plugins are introduced for the different subtasks of TRANSLATE-303 (TRANSLATE-306, TRANSLATE-311, TRANSLATE-309). They should be a category of plugins, which allow to modify task data. They should be callable by other plugins or by the GUI (later on). They may contain a GUI-part later on, which is hooked into task management window.
• This should be done along the new plugin architecture, wich should be implemented as far as it does only add little effort to the needed issues. This should be documented in MD-files.

Import

• for all transit-Segments, which have the status "locked in RefMat" or "notTranslated" this status is set in translate5 as custom segment-alternative-attribute. For "notTranslated" the name of the custom segment-alternative-attribute is "notTranslatedTransitAttribute".
• for all segments with empty target the custom segment-alternative-attribute "notTranslatedOnImport" is set. This can be done for all import formats.
• Import will mainly be used for RefMat-Extracts. For this purpuse we should generate a RefMat-Extract by ourselfs for testing purposes.
• Import has to ensure, that the fileformat of the skeleton-file is identical to the original transit file format. Since the beo-transit-classes rewrite the complete file instead of simply replacing only certain parts (as we usually do it in translate5) this has to be ensured by a postprocessing. The process should be:
  • get segments for the import
  • replace imported segments with a placeholder and rewrite/save the file
  • postprocess the file to restore the transit-xml-syntax, as we did it in beo-2. It is important that no chars are replaced by entities or vice versa. And it is important, that empty tags are in the format <seg></seg>, because transit can not handle empty <seg/> tags (reported by Eva at 19.11.2014; Eva said,
    <Seg ([^/]*)/> replace with <Seg \1></Seg> ).
  • save the thus created skeleton file to translate5
  • use this skeleton file with placeholders in the normal way for the export (replace the placeholders and do not use beo-transit-classes again)

After Import

TermTagging

• TermTagger worker is started (TRANSLATE-22)

lock segments which should not be edited

This is done after termTagging is finished:

• task-data-plugin "identify segments with 'red marked' terms" is called (TRANSLATE-323), if this is configured in the system-config
• Task-Data-Plugin of TRANSLATE-306 is called to lock segments, if this is configured in the system-config. For beo-1 plugin is configured to lock all segments with the custom segment-alternative-attributes "locked in RefMat", "notTranslatedTransitAttribute", "notTranslatedOnImport" - and in addition segments which do NOT have the attribute "missingTargetTermOnImport".

Export

• manual-set segment status (not autostate) and used terminology should be included in "Notizfeld" of target language of transit. Same is true for terms found in a source or target segment. (see translate-310)