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

Make default bconf path configurable

    XMLWordPrintable

Details

    • High
    • Hide
      The default okapi bconf files now can be defined as config:
       - runtimeOptions.plugins.Okapi.import.okapiBconfDefaultName
       - runtimeOptions.plugins.Okapi.export.okapiBconfDefaultName
      All bconf files defined in the Okapi/data folder, will be listed as selectable config value.
      Show
      The default okapi bconf files now can be defined as config:  - runtimeOptions.plugins.Okapi.import.okapiBconfDefaultName  - runtimeOptions.plugins.Okapi.export.okapiBconfDefaultName All bconf files defined in the Okapi/data folder, will be listed as selectable config value.
    • More flexible configuration for Okapi import/export .bconf files changeable per task import.

    Description

      Currently the bconf to be used for Okapi Import is hardcoded to the default bconf.

      This should be configurable, so that the users are able to choose a different bconf file from the folder. Important: Only the local bconf folder should be searchable, and no path separators should be allowed for security reasons.

      The config should be overwriteable on task-import and client level, so that for different clients different bconfs can be predefined. Not a perfect but a pragmatic solution.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: