It looks like a compile bug in that it re-encodes the already Unicode source with the encoding specified in the header … which does not make sense. Nevertheless, most combinations of loading the file and dumping it into compile work, so coverage might want to use a workaround.