When update-mime-database reads a magic pattern from freedesktop.org.xml, it
takes into account the value of the "type" tag when it parses the "value" tag to
generate a value with the wanted endianness
However, when the "mask" tag is being read, the endianness specified in "type"
isn't taken into account. This leads to unnatural behaviour with patterns like:
<match value="0x0000081a" type="little32" offset="0" mask="0x8080ffff"/>
where value is matched as a little endian value, but is masked with "mask" taken
as a big endian value.