Quick questions :\n\nPlaying with exiftool to learn.\n\nI noticed that iPhone photos are stored as .jpegs in big endian format.\nAnd so are Nikon .NEF images\n\nI know that big endian tiff and others was de-facto standard (despite\nTIFF supporting both) because the Macintosh was big endian and it was\nTHE machine for image processing in the early days.\n\nI had expected that little endian would have become de facto standard by\nnow, with basically all desktops being little endian. In fact, I have\nbeen scanning my slides little endian to tiff.\n\nSince the iPhone/IOS are little endian, I was surprised to see it\ngenerate big endian .jpegs since that would involve a lot of byte swas\nwhich consumed more CPU/battery.\n\nI have been scanning slides little endian, thinking it was the new de\nfacto standard.Is it better to keep those .TIFFs big endian for\nconsistency with rest of industry (even though both are supported) ?\n\n\n\nSecondly, on a totally different tangent:\nImage date-time (Created date) appears to be the local time, and the\noptional GMT offset which can be specified appears to be just a\nconvenience. (not present in iPhone photos, but preset in my Nikon DSLR)\n\nBecause scanned slides do not have a real date of the shot, I have to\nmanually set those (I know the dates, but not the times). For pictures\nin south pacific/asia, I want to make sure that specifying a date of\nmar-7-1995 with GMT offset of +10 will always show up as Mar-7th and not\nmarch 6th.\n\nIs there a recommended time to provide when you don't have the time of\nimage ? noon (12:00) or midnight (00:00) ?