Skip to content

BUG: Added Latin1 encoding specification to saved MRML file

Csaba Pinter requested to merge github/fork/cpinter/fix-xml-encoding-latin1 into master

In case special characters (e.g. in the patient name) ended up being saved in the MRML file, loading the MRML failed due to an XML reading error. These special characters were valid in Slicer, as they were produced by slicer.util.toVTKString. If the character set is specified in the MRML file, then loading is successful.

Merge request reports