[TRANSLATE-3246] Fixed naming scheme for OKAPI config entries - translate5 JIRA issue tracker

Type: Improvement
Resolution: Fixed
Fix Version/s: translate5 - 6.1.0
Affects Version/s: None
Component/s: file format settings

Urgency:
High
ChangeLog Description:
Fixed naming scheme for Okapi Service Configuration Entries. In the frontend, no name must be defined anymore
Checklist:

Empty

show more show less

The naming-scheme of OKAPI service entries has changed and now is fixed, see https://bitbucket.org/mittagqi/translate5/pull-requests/734

The realm of this issue is, to make sure, the Frontend editing of the Configs (editor_Plugins_Okapi_DbConfig_OkapiConfigType)

and the commands to manage OKAPI service entries (OkapiUpdateCommand, OkapiAddCommand) respect the adjusted service structure.

It should not be possible to add other Okapi-versions than defined in editor_Plugins_Okapi_Init::SUPPORTED_OKAPI_VERSION other then for DEV purposes

relates to

TRANSLATE-2063 Enable parallele use of multiple okapi versions to fix Okapi bugs

Done

TRANSLATE-2574 Enhance okapi-driven error message with defect docx-files coming from Google

Open

TRANSLATE-3202 Adopt File Format Settings for OpenXML to Okapi version 1.4.7

Done

Assignee:: Axel Becher

Reporter:: Axel Becher

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 14/Mar/2023 05:14

Updated:: 09/May/2024 09:53

Resolved:: 15/Apr/2023 02:30