IPTC questions

[bazography]

Photo Mechanic Plus Version 6.0, build 7269 (b13242a)

I recently started getting an error I’ve never seen before:
“Some of the characters cannot be represented in the default encoding and will result in data loss.
Would you like to save in the Unicode format which will preserve all of your data?”

I figured out that checking “Write IPTC as Unicode” solved the issue, although I’m confused as to why this just started recently. I haven’t changed my IPTC preferences for a decade or so, and I don’t use accents or other odd characters. Did something change with the 7269 update that would account for this? Just trying to work out if something is wrong at my end.

Also, from what I read in the support forums it sounds like you no longer recommend writing IPTC at all since it’s obsolete.

Until now I had PM set to imbed IPTC into JPG and RAW files. Going forward, if I was to change my preferences to no longer imbed IPTC at all, what happens when I alter metadata in an older image with previously embedded IPTC? Does PM always keep old IPTC updated, regardless of the new settings?

[Kirk Baker]

Photo Mechanic Plus Version 6.0, build 7269 (b13242a)

I recently started getting an error I’ve never seen before:
“Some of the characters cannot be represented in the default encoding and will result in data loss.
Would you like to save in the Unicode format which will preserve all of your data?”

I figured out that checking “Write IPTC as Unicode” solved the issue, although I’m confused as to why this just started recently. I haven’t changed my IPTC preferences for a decade or so, and I don’t use accents or other odd characters. Did something change with the 7269 update that would account for this? Just trying to work out if something is wrong at my end.

It could be something as simple as 'smart quotes' being used instead of standard ASCII single and double quotes.

Also, from what I read in the support forums it sounds like you no longer recommend writing IPTC at all since it’s obsolete.

Yes, indeed.

Until now I had PM set to embed IPTC into JPG and RAW files. Going forward, if I was to change my preferences to no longer embed IPTC at all, what happens when I alter metadata in an older image with previously embedded IPTC? Does PM always keep old IPTC updated, regardless of the new settings?

Yes, if it is present, it is updated.  You can strip it if you want by using Tools->Delete Metadata and only choosing to delete the IPTC data.

-Kirk

[bazography]

Thanks for the info.

I did some further testing as I wanted to see if I was writing an odd character I didn't know about. Turns out the offending character is one created by PM itself.

When ingesting, I write all my camera info and some file info to one unused field. One of the things I write is {time}.

Lets say {time} writes "2:49:25 PM". The specific character that causes the error is the space between the number and the "5" and the "PM". I systematically deleted every metadata entry until the only thing left was that space, and I would still get the error. As soon as the space was deleted, no error.

As mentioned, “Write IPTC as Unicode” solved it, and it's easy enough for me to modify my template to use {hour}:{minute}:{second} {ampm} instead, which doesn't cause the error. But I figured you should know as it seems weird that it is coming from a variable. Again this only popped up recently and I've been using the same template for a few years now.

Might not be relevant, but in case this helps... at one point I copied the "2:49:25 PM" text into Apple's TextEdit and noticed that the offending space showed as being in Helvetica font, whereas the rest of the text was shown in the default font I have set for TextEdit.

[Kirk Baker]

Thanks for the info.

I did some further testing as I wanted to see if I was writing an odd character I didn't know about. Turns out the offending character is one created by PM itself.

When ingesting, I write all my camera info and some file info to one unused field. One of the things I write is {time}.

Lets say {time} writes "2:49:25 PM". The specific character that causes the error is the space between the number and the "5" and the "PM". I systematically deleted every metadata entry until the only thing left was that space, and I would still get the error. As soon as the space was deleted, no error.

As mentioned, “Write IPTC as Unicode” solved it, and it's easy enough for me to modify my template to use {hour}:{minute}:{second} {ampm} instead, which doesn't cause the error. But I figured you should know as it seems weird that it is coming from a variable. Again this only popped up recently and I've been using the same template for a few years now.

Might not be relevant, but in case this helps... at one point I copied the "2:49:25 PM" text into Apple's TextEdit and noticed that the offending space showed as being in Helvetica font, whereas the rest of the text was shown in the default font I have set for TextEdit.

I will investigate.  Thanks for your diligence.

-Kirk

[Kirk Baker]

PM on macOS uses the time formatting from your computer's System Settings (Language & Region).

I'm running macOS Ventura and it no longer allows changing the formatting of the time, though perhaps yours does.  I'm unable to reproduce the unexpected character that you're getting.  What does your Language & Region settings look like?  Use the 'Attachments and other options' link when you're composing your reply to this message and there you'll be able to upload your JPEG format screenshot.

Thanks,

-Kirk