No,

I had some difficult to build libexif-0.6.18 and I needed only exif-0.6.18 for testing of a new translation.

Ok, I'll try to build libexif-0.6.18 also and those two error messages surely will disappear.

Br,

Jorma K.
2009/10/12 Jan Patera <patera@pictview.com>
Jorma,

are you building against libexif-0.6.18?
EXIF_DATA_TYPE_UNKNOWN & exif_loader_get_buf were added in this release.

 -- Jan

> I found two missing msgids in exif-0.6.18
>
> First is exif/actions.c:224
>
> "Adding entry..."
>
> The second is in exif/main.c:
>
> {"set-value", '\0', POPT_ARG_STRING, &p.set_value, 0,
> N_("Value of tag"), NULL},
>
> it should be
>
> {"set-value", '\0', POPT_ARG_STRING, &p.set_value, 0,
> N_("Value of tag"), N_("STRING")},
>
> also, I got error messages about this line:
>
> ed = exif_get_data_opts(l, log, 0, EXIF_DATA_TYPE_UNKNOWN)
>
> This EXIF_DATA_TYPE_UNKNOWN was really unknown and I added the
> following lines at the beginning of exif/main.c to workaround:
>
> #ifndef EXIF_DATA_TYPE_UNKNOWN
> #define EXIF_DATA_TYPE_UNKNOWN 254
> #endif
>
> Then in the exif/utils.c file I made the following workaround change:
>
>  //exif_loader_get_buf (loader, &buf, &buf_size);
>  memcpy( buf, loader, buf_size );
>
> I got error message about a nested exif_loader_get_buf here and
> replaced it with a notorious memcpy.
>
> BTW, line "Report-Msgid-Bugs-To: \n" in the po/exif.pot file should
> contain some email address.
>
> Best regards,
>
> Jorma Karvonen




------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
libexif-devel mailing list
libexif-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libexif-devel