When using the ezxmltext to richtext conversion tools on older databases, you might experience content objects which the conversion tool is not able to convert automatically. One reason for that is for instance lack of validation in ezxmltext, so it is possible to store ezxmltext which contains errors.

As there is no GUI for editing archived versions, the conversion tool should be able to dump invalid ezxmltext to files. User may then edit those text files manually in an editor and then use a script to import them back to the db

So, the conversion tool should have a new param:
--export-dir .... Path to store ezxmltext which the conversion tool is not able to convert. filenames in given directory will have given pathname :

ezxmltext_[contentobject_id]_[contentobject_attribute_id]_[version]_[language].xml

A file with the validation errors will be written to

ezxmltext_[contentobject_id]_[contentobject_attribute_id]_[version]_[language].txt

A new tool should then be able to import such files

bin/console ezxmltext:import-xml --export-dir corrections/ [--dry-run] [--test-content-object 123]