pyexiv2-developers team mailing list archive

[Olivier Tilloy <olivier@xxxxxxxxxx>]

On 2010-02-19, Damien Moore <damienlmoore@xxxxxxxxx> wrote:
> bug for the build issue is at: https://bugs.launchpad.net/pyexiv2/+bug/523858
Thanks for the report!

> couple of other things...
>
> 1/ I converted phraymd across with only minor issues so far (not yet
> in the repo). The biggest issue is figuring out how to handle the type
> inconsistencies between 0.1 and 0.2 in order to keep the cache files
> compatible. (a bunch of shorts were being stored as strings in 0.1)
0.2 gives you access to the type information, which should help.
If you mean that the EXIF/IPTC type of some given tags changed between 
O.1 and O.2, the change is in libexiv2 itself, most likely because the 
type was previously wrong. I'm afraid you'll have to perform hardcoded 
conversions for those.
> 2/ What is the deal with the "charset=***" contained in some of the
> Exif text tags? Is there any support for correctly translating these
> into usable strings in v0.2?
Not yet, but it's definitely something I want to implement (although 
probably not in 0.2.0, I don't see it as a show stopper for a first 
release). A related request is tracked by 
https://bugs.launchpad.net/pyexiv2/+bug/461847.
Could you please file a new bug report for EXIF text tags, including as 
much information as possible (what tags are concerned, example 
images/values)?
Cheers,

Olivier