to discuss with Arle:

• ability to add files to a project later on (and therefore possibly add new alternatives for this file). This will be selectable in task-preference window. If a file with the same name is imported as an already existing file, the new file is renamed with an added number. An alignment (adding new alternatives to an existing file in translate5) is not possible. What does happen with not matching MIDs, not existing MIDs will not be imported; It's not allowed to add alternatives to ranking tasks
• see TRANSLATE-110
• depending on first discussion point:
  • It's not allowed to add alternatives to ranking tasks
  • if ranking has been done and the workflow is changed to another workflow still it will not be possible to add alternatives to the task
• completly cancel the point "Import of alternatives through file-system-structure column mapping / SDLXLIFF-Import for alternative-target versions", because it adds to much effort

Import

create task with unzipped single file

• Import is changed, that in addition to the standard-zip-package it is possible just to select a csv- or sdlxliff-file. If done so, the new task will only contain the contents of this one file. Marking of terminology, attaching of reference-files, using of the relais/pivot-feature will not be possible this way
• The standard import via the current zip-package stays as is. It stays the only way to mark terminology, attach reference-files or use a relais-/pivot-language
• The import shows an error-message, if no zip, sdlxliff- or csv-file is selected

CSV-Import with all alternative columns inside one csv-file-structure

• the logic of csv-import is changed:
  • In the future the order of columns has to be fixed: The first column must be "mid" and the second must be "source". if not an error is thrown on import time and the error message is shown to the user. The same will happen with all other import errors in the future.
  • Which string can be used for "mid" and "source" can still be changed on per installation base in application.ini.
  • All following columns will be handled as alternative target columns, if their header contains something else than an empty string.
  • This non-empty-string will be used as column-label for this alternative-target-column inside translate5:
    • It will be used in GUI-translation process, therefore can be translated by the normal translate5 GUI-xliff translation procedure
    • The column label of the not editable alternative-target-column will be the string from csv
    • The column label of the editable alternative-target-column will be "labelFromCsv: edited" (edited will of course be translated through translate5 GUI-xliff translation procedure)
• if there are several CSV-Files in the task,
  • the alternative-target-columns are matched by label
  • if there are in one CSV-Files more/different alternative-target-columns, than in the other, the missing translations of one file stay empty
  • the autostate is "translated" if at least one alt trans is present. If no alt trans exists and the source was set, the autostate will be "untranslated"
• this CSV-file can be uploaded unzipped (as described above) or inside the proofRead-folder of a normal translate5-zip-package
• MQM Information in the CSV files is imported also. The format is like the already defined export format.

general alternative-target-definitions

• for every alternative-target translate5 will provide on database- and on frontend-level 2 columns. One will store the not changeable alternative-target as it has been imported, one will store the editable alternative-target.
• the visibility of the not editable alternative-target can be defined in the task preferences and in application.ini (for the default)
• in CSV export all alternatives are exported

changes to standard editor

implications on columns

• all available alternative-columns are editable, when the editor is open
• if target-column-labels should not be shown to a user according to the task-preferences, the columns are labeled "target A", "target B", etc.
• otherwhise the columns are labeled as described in the csv-import-changes-definitions. If on standard sdlxliff-import there is no label-definition available, the current labels are shown for the target and the edited columns
• according to available target-columns and definitions in the task preferences alternative-target columns and not editable target-columns are shown or not shown.
• in the ergonomic view always the source column (or if available the editable source column) and the first editable target column are shown by default (in addition to segmentNr and autostate-columns). All other columns are hidden by default.

implications on segment-navigation in segment-metadata-panel

• the current arrow-navigation (right-arrow: save current and open next segment; left arrow: save current and open previous segment) will be extended in the following way:
  • right-arrow opens the next available alternative-target of the currently open segment (the one next to the right of the currently edited alternative). If there is no next in the currently open segment, the first alternative-target of the next segment will be opened
  • left-arrow opens the previous available alternative-target of the currently open segment. If there is no previous in the currently open segment, the last alternative-target of the previous segment will be opened
  • arrow-down opens the alternative-target of the same column as the currently edited one in the next segment.
  • arrow-up opens the alternative-target of the same column as the currently edited one in the previous segment.
• if the source is editable, it will be included in this logic
• if there is only one editable target and no editable source, everything stays as it is before this feature spec. (right-arrow for opening next, left-arrow for previous)

implications on repetition editor

as I understood, DFKI does not need the repetition editor, even more it should be disabled for the work DFKI needs translate5 for. Therefore the following will be the easiest regarding alternative-targets:

• if there is more than one target in the task, the repetition editor will be disabled automatically completely. The user gets a message about this, when he opens the task
• furthermore it will be possible to disable the repetition editor completely on per installation basis by ACL-rights.