The thing is Exifography is not parsing anything as far as the camera model is concerned and neither is WordPress. WordPress has EXIF import already enabled for some fields and my plugin just adds extra fields that WP didn’t already do and then displays it all. To import the camera model WordPress is using the native PHP EXIF module (https://php.net/manual/en/book.exif.php). So if anything is having trouble with the data it is PHP, which is installed at a server level.
It’s entirely possible that this is the problem, in fact I think that is the problem. Since other software like ExifTool and Preview etc can all read the data, my suspicion is that there’s an invisible character in the camera make that is messing up the PHP parsing it, but not messing up these other programs. However, it’s also my belief that whatever that character or issue might be, it’s originating in Lightroom, because images processed in other ways work fine in WordPress.
So, it seems to be a problem with PHP, not WordPress or Exifography. The only thing we can do about that is try upgrading our servers’ PHP and see if that helps, but I was testing on PHP 5.6.2, which is fairly recent. Or we can try to bypass the problem, by excluding the make field from the image export.
We could test further by using a plain PHP script independent of WordPress that reads the EXIF from this image and see what it turns up. There is even one written here: https://www.dzone.com/snippets/php-exif-reader-demo I might try it in the morning (bit too tired now), but that’s looking for a much longer term solution.