In some cases the dfxml file (which is generated by IsoBuster) will contain non-UTF8 characters, with the result that it cannot be parsed. I've seen this happen with one HFS image that someone sent. In this case the image contained files whose paths have illegal characters (which also result in reported encoding errors when the image is mounted).
Possible solution would be to check the dfxml for encoding errors in Iromlab and fix any errors in place (but the result will be that file paths in the Dfxml file might not match the actual paths in the image).
For legacy batches this could be dome as post-processing.
In some cases the dfxml file (which is generated by IsoBuster) will contain non-UTF8 characters, with the result that it cannot be parsed. I've seen this happen with one HFS image that someone sent. In this case the image contained files whose paths have illegal characters (which also result in reported encoding errors when the image is mounted).
Possible solution would be to check the dfxml for encoding errors in Iromlab and fix any errors in place (but the result will be that file paths in the Dfxml file might not match the actual paths in the image).
For legacy batches this could be dome as post-processing.