• Type: Bug
• Resolution: Unresolved
• Fix Version/s: None
• Affects Version/s: None
• Component/s: Import/Export

[TRANSLATE-2434] file extension ODT can not be handled - odt can

Collapse comment: Marc Mittag [Administrator] added a comment - 04/Mar/2021 07:13, Edited by Thomas Lauria - 08/Mar/2021 01:28

Marc Mittag [Administrator] added a comment - 04/Mar/2021 07:13 - edited

tlauria it is definitely an okapi problem, that probably could be solved by mapping all file types that okapi supports in the bconf to all versions of upper case and lower case in the file extension.

Yet this is a lot of effort and error prone.

Much better is, to implement in translate5 (in core, independant from okapi) that we always convert the fileextension to lower case before sending it to okapi (it is ok, if it is lower case also in the translate5 export then).

Since I think, this should also be a fast fix, I put this to the top of your pipeline

Expand comment: Marc Mittag [Administrator] added a comment - 04/Mar/2021 07:13, Edited by Thomas Lauria - 08/Mar/2021 01:28

Marc Mittag [Administrator] added a comment - 04/Mar/2021 07:13 - edited tlauria it is definitely an okapi problem, that probably could be solved by mapping all file types that okapi supports in the bconf to all versions of upper case and lower case in the file extension. Yet this is a lot of effort and error prone. Much better is, to implement in translate5 (in core, independant from okapi) that we always convert the fileextension to lower case before sending it to okapi (it is ok, if it is lower case also in the translate5 export then). Since I think, this should also be a fast fix, I put this to the top of your pipeline