another weird problem

[alexramsay]

Following my last post, I tried converting the NEF files to DNG. Lo and behold Iview could sync annotations back to these, no problem. Then I tried syncing back to a TIFF (a scanned image). Now Photoshop won't open the TIFF, saying that it's 'not compatible with this version of Photoshop'. What's going on?

[peterkrogh]

Alex,
Do you have another copy of the file?
Do you have any other programs to try to open the file?
I'd contact iview and see what they say.
Peter

[alexramsay]

Dear Peter,
Thanks for answering. Unfortunately I deleted the corrupted file and replaced it with a backup copy, and I've been unable to replicate the sequence of events. It may have been to do with over-writing a template made in v2 with one made in v3?
While I'm here, why does version 3 put an odd symbol in front of the ©, while version 2 does not? Can this be avoided?

Regards,
Alex

[roberte]

Hi Alex,

IIRC this is an issue with unicode. Do a search on the iView forums and you'll find several posts. As explained elsewhere Nikon only supports older IPTC specs so NEF files aren't designed to work with unicode.

From here it gets a little hazy as the final specs for IPTC IIM did allow for unicode but it's hard to find any practical implementation of it. Most vendors went to unicode only after the XMP and/or IPTC Core specs were released. iView isn't alone as there are many apps having issues supporting the latest IPTC Core and legacy specs. One answer is to abandon legacy support which iView briefly did only to receive a wave of complaints. They very quickly reversed that decision which was a good example of iView listening to their customers.

We need legacy IPTC support because not every app and operating system has updated to IPTC Core and nor have have many of our clients. There's no use only writing IPTC Core if the information can't be read further down the pipeline. IPTC Core is not even three years old and like anything new it will take time to be widely supported.