Error in IPTC from Photoshop to XnView

[KurtL]

When I describe Document-info (IPTC) in Adobe Photoshop, I can read this also in XnView. correct.

But when I describe new IPTC data in XnView they are not in Adobe Photoshop. The Document-info (IPTC) is empty.

When I describe Document-info (IPTC) in Adobe Photoshop, open the photo in XnView, and edit the information here, and again open the photo in Photoshop - the edited IPTC info from XnView is not edited in PS. Instead the old IPTC data from PS is still in the file.

When editing in XnView I - of course - press the buttom 'Write'. I use version 1.74.

Why is it so, and is it an error in XnView

Kurt L/ Denmark

[xnview]

When I describe Document-info (IPTC) in Adobe Photoshop, I can read this also in XnView. correct.

But when I describe new IPTC data in XnView they are not in Adobe Photoshop. The Document-info (IPTC) is empty.

When I describe Document-info (IPTC) in Adobe Photoshop, open the photo in XnView, and edit the information here, and again open the photo in Photoshop - the edited IPTC info from XnView is not edited in PS. Instead the old IPTC data from PS is still in the file.

When editing in XnView I - of course - press the buttom 'Write'. I use version 1.74.

Why is it so, and is it an error in XnView

Perhaps your photoshop configuration use XMP instead of old IPTC metadata.

[Guest]

Perhaps your photoshop configuration use XMP instead of old IPTC metadata.

In the help file for Adobe Photoshop (7.0) it is told, that it support NAA and IPTC standards.

So what it the/ my problem then?


Kurt L/ Denmark

[xnview]

Perhaps your photoshop configuration use XMP instead of old IPTC metadata.

In the help file for Adobe Photoshop (7.0) it is told, that it support NAA and IPTC standards.
So what it the/ my problem then?

Don't know, could you send me a sample with iptc readed by photoshop 7?

[Olivier_G]

Images can carry both IPTC (IIMv4.1) and XMP (Adobe's own implementation of metadada, that Photoshop call "IPTC" as well). They may be used in parallel... as in Photoshop.

It seems that Photoshop writes into both XMP and IPTC, but read only from XMP.
=> Create/Update in PS => IPTC updated in XnView as well.
=> Create/Update in XnView => no effect in PS.

I would call this a bad implementation of XMP/IPTC in Photoshop 7...

Olivier

[Carl]

Images can carry both IPTC (IIMv4.1) and XMP (Adobe's own implementation of metadada, that Photoshop call "IPTC" as well). They may be used in parallel... as in Photoshop.

It seems that Photoshop writes into both XMP and IPTC, but read only from XMP.
=> Create/Update in PS => IPTC updated in XnView as well.
=> Create/Update in XnView => no effect in PS.

I would call this a bad implementation of XMP/IPTC in Photoshop 7...

Olivier

It's exciting to note that that XnView's author has said that he will add XMP in a future version of XnView. It would be nice to have the choice of either IIMv4.1 or XMP in XnView.

[madn]

Hi guys,

I encountered exactly the same problem with Bridge CS2 - surprisingly, I got the correct information in Photoshop itself but not in Bridge: once I had updated the IPTC tables with XnView, I could't see the new values in Bridge, though it worked well with other programs for IPTC-tagging like ThumbsPlus.

The solution was to deactivate the "Keep original date/time attributes" in XnView, which is active by default. Obviously, Bridge needs an updated "last modified"-field to recognize any alteration in the metadata.

Perhaps that might help someone else.

Greetings
Malte

[Guest]

Great suggestion.... and a great find!
The obvious drawback about going against the default in XnView is that it will force the rewrite of the entire JPG file itself, which will cause another JPG conversion. I liked XnView because it did not force a re-conversion of the JPG but simply allowed rewrite of the IPTC data.

So, (to clarify) it seems that if we force a re-write of the file (update times), thus force a rewrite of the JPG, then Bridge or other programs like it will see the updated IPTC info.