Details
-
Improvement
-
Resolution: Unresolved
-
None
-
None
-
Critical
-
File Format Settings: General compatibility with Okapi 1.4.7, improved Pipeline handling
-
Empty show more show less
Description
- Basework for improved Pipeline handling: Verify Pipeline in the Backend "Step by Step" (the Steps in a Loop)
- Since we will have Import (pipeline.pln) and Export (export-pipeline.pln) Pipelines (see: https://jira.translate5.net/browse/TRANSLATE-4200) we need two step-models in content.json, "importSteps" and "exportSteps"
- Classes for Steps in /Okapi/Bconf/Step/
- Step-Classnames equal step in Pipeline: net.sf.okapi.steps.rainbowkit.creation.ExtractionStep => ExtractionStep
- Validation per step: All steps valid -> Pipeline valid
- [Perspectively: Frontend shall make steps editable & addable]
- OKAPI 1.4.7 compatibility: Check all FPRMs for changes (-> ask Axel how to extract the 1.4.7 ones via Rainbow)
- Amend added & remove obsolete settings for the ones editable in t5
- Integrate Pipeline into general "versioned upgrade" mechanism like SRX and FPRM
- Change "writerOptions.escapeGT.b=false" to true in the "ExtractionStep" for the t5 default BCONF & all inheriting bconfs (ask Axel about details)
- Remove obsolete "runtimeOptions.plugins.Okapi.import.okapiBconfDefaultName" config & adjust "E1340" ecode message
Attachments
Issue Links
- blocks
-
TRANSLATE-3647 Okapi integration: Enable down- and upload of fprm and pln files and pre-parsing of xliff by Okapi
- Selected for dev
- is blocked by
-
- Final pull request
- is parent of
-
TRANSLATE-3429 Special white-space chars in IDML are protected as tags in Okapi - no match with whitespace in translate5
- Selected for dev
-
- Selected for dev
