problem

It happens from time to time in different contexts that an Okapi export fails due to invalid XML in the exported XLF file. Especially for file translation in instanttranslate this is bad since, there is no influence to repair single segments manually and automatically repaired content would be OK.

solution

On the export of XLF (to be discussed: all XML based formats) each segment and finally the whole file should be checked on export if the produced data is valid XML.

On segment level we can try to fix it automatically depending on the error. We do that already on connector level for language resources when using deepl but it makes sense to do that on a general manner on a latter step / level as on languageresource level.

On over all level that would mean the skeleton level is already invalid. How ever, handling such errors on translate5 level and preventing that Okapi must handle (crash the export) is always the better solution.