Bild für Projekt hochgeladen: 'translate5'
  1. translate5
  2. TRANSLATE-2432

Make default bconf path configurable

    XMLWordAusdruckbar

    Details

    • Urgency:
      High
    • Important release notes:
      Ausblenden
      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.
      Anzeigen
      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.
    • ChangeLog Description:
      More flexible configuration for Okapi import/export .bconf files changeable per task import.
    • Reporter issue no.:
      -

      Beschreibung

      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.

        Anhänge

          Aktivität

            Personen

            Bearbeiter:
            aleksandar Aleksandar Mitrev
            Autor:
            tlauria Thomas Lauria
            Stimmen:
            0 Für Vorgang stimmen
            Beobachter verwalten:
            1 Vorgang beobachten

              Daten

              Erstellt:
              Aktualisiert:
              Erledigt: