Yes i have this problem that once i have entered iptc data with Xnview it does not show in my Photoshop 7.0
Can anyone tell me why and what can i do that it will be shown?
Iptc does not show in Photoshop ??
Moderators: helmut, XnTriq, xnview
Re: Iptc does not show in Photoshop ??
I think that Photoshop use XMP metadata and not IPTClasse997 wrote:Yes i have this problem that once i have entered iptc data with Xnview it does not show in my Photoshop 7.0
Can anyone tell me why and what can i do that it will be shown?
Pierre.
Re: Iptc does not show in Photoshop ??
I am currently battering my head against this, trying to decide on the most efficient approach.lasse997 wrote:Yes i have this problem that once i have entered iptc data with Xnview it does not show in my Photoshop 7.0
Can anyone tell me why and what can i do that it will be shown?
According to this chart : http://www.controlledvocabulary.com/ima ... mapped.pdf PS 7 does support some fields.
IPTC say the shipped code with PS 7.0.1 and CS is buggy: http://www.iptc.org/IPTC4XMP/ and provide updates. I use CS (with those updates), so I'm not sure about v7, but my current findings are as follows:
IPTC data can be stored in the older tagged format in the APP13 block. This is called the IIM format and is what most programs (incl xnview) support. The new format is XMP: an xml-style text, which you can see in xnview info panel, if some is present in the image file.
Take a fresh jpeg, save IPTC information with xnview, and load with PS CS. Some IPTC fields are shown in the PS file info boxes (author (byline), caption (description), headline, title (object name) are all shown. A few are not.
However, if you start by using PS to edit any IPTC data then it saves as IIM plus XMP format plus a few exif fields as well. It duplicates much of the content in each place. From then on, the XMP fields take priority, and if you use xnview, or any other program to change the IIM content, then it will not see it. What a mess!
Re: Iptc does not show in Photoshop ??
IPTC unmessed ;-)
In fact it is quite simple. There is one IPTC standard. As far as I know is the most recent one Revision 13. On IPTC.org is all of the documentation available/downloadable. Like the countrycodes, the newscodes and so on.
If I understood it well there is also room for specific fields in the metafile. So some organisations or manufacturers can add fields. If they are readable depends on the viewer.
However, in my opinion it is important, for sake of compatibility, to use the fields specified by IPCT to make the information readable for everyone.
In Photoshop there's the possibility to add IPTC information with RAW (DNG) files. But rhey're stored ouside the file in a sidecarfile. So whem the file is moved, it is necessary to movge the sidecarfiles with the files. And it is not surprising that the only programs that can read those sidecarfiles are Adobe Bridge, Photoshop and Lightroom...
Apps wich don't have the ability to read/edit this information correctly don't use the IPTC standard. Simple as that. It is not forbidden, but the readability for no-users of these apps can be level zero.
When it comes to standards there's always confusion, think about color management, for example. A language is an agreement. So, when people agree to speak Patagonian they'll understand each other. Standards are also an agreement, everyone has to agree. When you don't agree there could be a mess... ;-)))
Another remark about Controled Vocabulary, they provide a lot of good information. But, why not contact the source of the information? I buy my bread at the bakery, not at the postoffice. So please smile and say: www.iptc.org .
Regards,
Jur
According to this chart : http://www.controlledvocabulary.com/ima ... mapped.pdf PS 7 does support some fields.
IPTC say the shipped code with PS 7.0.1 and CS is buggy: http://www.iptc.org/IPTC4XMP/ and provide updates. I use CS (with those updates), so I'm not sure about v7, but my current findings are as follows:
IPTC data can be stored in the older tagged format in the APP13 block. This is called the IIM format and is what most programs (incl xnview) support. The new format is XMP: an xml-style text, which you can see in xnview info panel, if some is present in the image file.
Take a fresh jpeg, save IPTC information with xnview, and load with PS CS. Some IPTC fields are shown in the PS file info boxes (author (byline), caption (description), headline, title (object name) are all shown. A few are not.
However, if you start by using PS to edit any IPTC data then it saves as IIM plus XMP format plus a few exif fields as well. It duplicates much of the content in each place. From then on, the XMP fields take priority, and if you use xnview, or any other program to change the IIM content, then it will not see it. What a mess!
[/code]
In fact it is quite simple. There is one IPTC standard. As far as I know is the most recent one Revision 13. On IPTC.org is all of the documentation available/downloadable. Like the countrycodes, the newscodes and so on.
If I understood it well there is also room for specific fields in the metafile. So some organisations or manufacturers can add fields. If they are readable depends on the viewer.
However, in my opinion it is important, for sake of compatibility, to use the fields specified by IPCT to make the information readable for everyone.
In Photoshop there's the possibility to add IPTC information with RAW (DNG) files. But rhey're stored ouside the file in a sidecarfile. So whem the file is moved, it is necessary to movge the sidecarfiles with the files. And it is not surprising that the only programs that can read those sidecarfiles are Adobe Bridge, Photoshop and Lightroom...
Apps wich don't have the ability to read/edit this information correctly don't use the IPTC standard. Simple as that. It is not forbidden, but the readability for no-users of these apps can be level zero.
When it comes to standards there's always confusion, think about color management, for example. A language is an agreement. So, when people agree to speak Patagonian they'll understand each other. Standards are also an agreement, everyone has to agree. When you don't agree there could be a mess... ;-)))
Another remark about Controled Vocabulary, they provide a lot of good information. But, why not contact the source of the information? I buy my bread at the bakery, not at the postoffice. So please smile and say: www.iptc.org .
Regards,
Jur
I am currently battering my head against this, trying to decide on the most efficient approach.CameronD wrote:lasse997 wrote:Yes i have this problem that once i have entered iptc data with Xnview it does not show in my Photoshop 7.0
Can anyone tell me why and what can i do that it will be shown?
According to this chart : http://www.controlledvocabulary.com/ima ... mapped.pdf PS 7 does support some fields.
IPTC say the shipped code with PS 7.0.1 and CS is buggy: http://www.iptc.org/IPTC4XMP/ and provide updates. I use CS (with those updates), so I'm not sure about v7, but my current findings are as follows:
IPTC data can be stored in the older tagged format in the APP13 block. This is called the IIM format and is what most programs (incl xnview) support. The new format is XMP: an xml-style text, which you can see in xnview info panel, if some is present in the image file.
Take a fresh jpeg, save IPTC information with xnview, and load with PS CS. Some IPTC fields are shown in the PS file info boxes (author (byline), caption (description), headline, title (object name) are all shown. A few are not.
However, if you start by using PS to edit any IPTC data then it saves as IIM plus XMP format plus a few exif fields as well. It duplicates much of the content in each place. From then on, the XMP fields take priority, and if you use xnview, or any other program to change the IIM content, then it will not see it. What a mess!
[/code]
Things that absolutely cannot happen will happen too...