Iptcinfo3

IPTCInfo now accepts 'inp_charset' keyword for setting input charset.

1.9.2-rc6: just PyLint-ed out some errors.

file objects to be file objects (he uses this on jpeg files stored in
databases as strings).
It modifies the module in order to look for a read method on the file
object. If one exists it assumes the argument is a file object, otherwise it
assumes it's a filename.

cStringIO on file save (to save the file without truncating it on Exception).

will overwrite the original image file (info.save()) only if everything goes
fine (so if an exception is thrown at writing, it won't cut your original
file).

This is a pre-release version: needs some testing, and has an unfound bug
(yet): some pictures can be enhanced with iptc data, and iptcinfo.py is able
to read them, but some other iptc data readers will spit on it.

The class IPTCInfo now has an inp_charset and an out_charset attribute - the
first is the read image's charset (defaults to the system default charset),
the second is the charset the writer will use (defaults to inp_charset).

Reader will find the charset included in IPTC data (if any, defaults to the
system's default charset), and use it to read to unicode strings. Writer will
write using IPTCinfo.out_charset (if it is not set, will not write charset
IPTC record).

With this, it is possible to read and write i18n strings correctly.

I haven't tested this functionality thoroughly, and that little test was only
on my WinXP box only, with the only other IPTC reader: IrfanView.