Details
-
Improvement
-
Resolution: Unresolved
-
None
-
None
-
Medium
-
OKAPI now is the default CSV-parser
-
OKAPI now is the default Parser for CSV files and the translate5 internal parser has to be enabled in the config if it shall be used instead
Description
So far translate5's own CSV parser is used, when a CSV file is imported.
This makes sense, if you want to do multi-target-column MT evaluation with MQM.
But in all other cases the possibilities Okapi offers make much more sense.
Therefore we should by default send CSV to Okapi, but keep the old mechanism and make it possible to switch it on via system config (overwriteable on client and import level.
To all CSV related existing system configs a hint should be added:
- This config is only used, if the config xyz is activated
Attachments
Issue Links
- is blocked by
-
TRANSLATE-3914 Change visual wget test data location
- Selected for dev
