libexif-devel — This is the place where your questions about libexif will be answered.

[Libexif-devel] [PATCH] usercomment modification in exif utils

[matthieu c. <cas...@fr...>]

Hi,

I need to change exif usercomment. I update the exif tools to do that.
See the attached patch for cvs.

I try this patch on 0.6.15-5 exif tools (I don't manage to build cvs)
and it works, put all the exif data are rewritten and are different from
the original picture.
This shouldn't happen because I only update usercomment without changing
the tag size.

Why libexif change the exif tags.


Matthieu

Re: [Libexif-devel] Fuji makernote

[Michele B. <mic...@pu...>]

On Thu, 2008-04-24 at 17:58 +0200, Jan Patera wrote:
> > Hi!  Just catching up on this group.
> > Not an OO.o developer but wouldn't mind helping out.
> > Anyway ...  What does OO.o do with EXIF info?
> 
> what is OO.o?

OpenOffice.org :)

Gotta love acronyms!

ciao,
Michele

[Libexif-devel] [Fwd: [Bug 466044] JPEG plug-in crashes while opening image with Olympus MakerNote (bug in libexif)]

[Jan P. <pa...@pi...>]

FYI.

 -- Jan

-------- Původní zpráva --------
Předmět: [Bug 466044] JPEG plug-in crashes while opening image with
Olympus MakerNote (bug in libexif)
Od: "GIMP (bugzilla.gnome.org)" <bug...@bu...>
Datum: 5 Květen 2008, 16:40

If you have any questions why you received this email, please see the
text at the end of this email. Replies to this email are NOT read,
please see the text at the end of this email. You can add comments to
this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=466044

  GIMP | Plugins | Ver: 2.2.x

------- Comment #35 from Sven Neumann  2008-05-05 14:40 UTC ------- This
is ridiculous. Even though the problem has been fixed in libexif about
nine months ago, there is still no libexif release that contains this
fix. I just checked and the version that is in debian unstable is still
affected by this bug. libexif 0.6.16 still seems to be the latest
upstream release.

Re: [Libexif-devel] Fuji makernote

[Jan P. <pa...@pi...>]

Hi,

> Back in December of 2007, Jan Patera wrote:
>
>> I was cleaning up my HDD and I found out the old libmnote had a
>> skeleton for FUJI makernotes. Apparently that part was not merged to
>> libexif when the rest was.
>> Therefore I finished the code, adapted to the current structuring,
>> updated tags using
>> http://homepage3.nifty.com/kamisaka/makernote/makernote_fuji.htm and
>> tested on images mainly from http://www.steves-digicams.com/
>
> Hi!  Just catching up on this group.
> Not an OO.o developer but wouldn't mind helping out.
> Anyway ...  What does OO.o do with EXIF info?

what is OO.o?

> And, any expectation that it will do anything with IPTC info?

If "it" is "libexif" then the answer is nothing special - it will be ignored.
If "it" is "OO.o" then I don't know...

>
> -- Kenn

Re: [Libexif-devel] Fuji makernote

[Kenn G. <ysl...@sn...>]

Back in December of 2007, Jan Patera wrote:

> I was cleaning up my HDD and I found out the old libmnote had a skeleton
> for FUJI makernotes. Apparently that part was not merged to libexif when
> the rest was.
> Therefore I finished the code, adapted to the current structuring,
> updated tags using
> http://homepage3.nifty.com/kamisaka/makernote/makernote_fuji.htm
> and tested on images mainly from http://www.steves-digicams.com/

Hi!  Just catching up on this group.
Not an OO.o developer but wouldn't mind helping out.
Anyway ...  What does OO.o do with EXIF info?
And, any expectation that it will do anything with IPTC info?

-- Kenn

[Libexif-devel] New Slovak PO file for 'exif' (version 0.6.16-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'exif' has been submitted
by the Slovak team of translators.  The file is available at:

    http://translationproject.org/latest/exif/sk.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/exif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/exif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Slovak PO file for 'libexif' (version 0.6.17-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'libexif' has been submitted
by the Slovak team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/sk.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/libexif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/libexif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Slovak PO file for 'libexif' (version 0.6.17-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'libexif' has been submitted
by the Slovak team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/sk.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/libexif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/libexif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Chinese (simplified) PO file for 'exif' (version 0.6.16-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'exif' has been submitted
by the Chinese (simplified) team of translators.  The file is available at:

    http://translationproject.org/latest/exif/zh_CN.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/exif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/exif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Vietnamese PO file for 'exif' (version 0.6.16-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'exif' has been submitted
by the Vietnamese team of translators.  The file is available at:

    http://translationproject.org/latest/exif/vi.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/exif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/exif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] Failing test suite

[Dan F. <da...@co...>]

The recent round of changes to exif/libexif have made the test suite fail.
The root cause seems to be that the IFD no longer defaults to "0".  Adding
the --ifd=0 parameter to a couple of exif invocations in
tests/check-general-images.sh makes it work again, but that shouldn't be
necessary.

>>> Dan
-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved

Re: [Libexif-devel] [libexif-cvs] libexif/libexif exif-content.c, 1.22, 1.23 exif-data.c, 1.107, 1.108

[Jan P. <pa...@pi...>]

> On Fri, 2008-02-15 at 08:04 +0100, Jan Patera wrote:
>> to be absolutely correct, you should not update *ds if the realloc
>> fails.
>
> Does this mean a failure of realloc is not recoverable at all? I assumed
> realloc will be a no-op in case of failure...

Perhaps you shouldn't have deleted the code snippet.
*ds is supposed to contain the size of the allocated memory.
Before your changes, in case of failed realloc, *ds contained the new
(expected) size, but the pointer became NULL -> likely crash folowing
soon.
If not, then memory leak occured.

After your changes, *ds contains the new expected size, but the pointer
actually points to the original block of smaller size.
-> likely reading from non-allocated area (->possible crash) and
likely writing beyond allocated area (-> crash or memory corruption
causing troubles anytime later -> hard to track down).

 -- Jan

Re: [Libexif-devel] [libexif-cvs] libexif/libexif exif-content.c, 1.22, 1.23 exif-data.c, 1.107, 1.108

[Jan P. <pa...@pi...>]

Lutz,

to be absolutely correct, you should not update *ds if the realloc
fails. Then the code can easily touch memory beyond allocated area...
(IMHO harder to find than eventually touching NULL.)
Similarly in *most* your fixes (I wouldn't bother *much* when actually
decreasing the allocated size).

> file: /cvsroot/libexif/libexif/libexif/exif-data.c,v
>  		if (s & 1)
>  			(*ds)++;
> -		*d = exif_mem_realloc (data->priv->mem, *d, *ds);
> -		if (!*d) {
> +		t = exif_mem_realloc (data->priv->mem, *d, *ds);
> +		if (!t) {
>  			EXIF_LOG_NO_MEMORY (data->priv->log, "ExifData", *ds);
>  		  	return;
>  		}
> +		*d = t;

 --- Jan

[Libexif-devel] [Brian.Cameron@Sun.COM: Re: [gphoto-devel] Schedule for a version release?]

[Marcus M. <ma...@je...>]

hi folks,

this is more for you I guess.

Ciao, Marcus

----- Forwarded message from Brian Cameron <Bri...@Su...> -----

Date: Mon, 11 Feb 2008 13:02:54 -0600
From: Brian Cameron <Bri...@Su...>
To: gph...@li...
Cc: ki...@ba...
Subject: Re: [gphoto-devel] Schedule for a version release?


gphoto team:

If we are going to do new gphoto2/libgphoto2 releases, would it be 
possible to also do a libexif-gtk release.  Fixes for the following
bugs are upstream, but there hasn't been a new release of this module
since October, 2004.

#1616317 (need to remove GDK_DEPRECATED)
#1616320 (empty structs cause build failure on Solaris)
#1643242 (need for uninstalled.pc files)
#1394423 (libexif-gtk 0.3.5 doesn't build with libexif 0.6.13)

It would be nice if we could start building libexif-gtk without needing
to apply so many patches to get it to build.

Brian

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Gphoto-devel mailing list
Gph...@li...
https://lists.sourceforge.net/lists/listinfo/gphoto-devel


----- End forwarded message -----

[Libexif-devel] New Swedish PO file for 'exif' (version 0.6.16-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'exif' has been submitted
by the Swedish team of translators.  The file is available at:

    http://translationproject.org/latest/exif/sv.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/exif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/exif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Dutch PO file for 'exif' (version 0.6.16-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'exif' has been submitted
by the Dutch team of translators.  The file is available at:

    http://translationproject.org/latest/exif/nl.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/exif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/exif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

Re: [Libexif-devel] [libexif-cvs] libexif/libexif exif-entry.c, 1.115, 1.116 exif-tag.c, 1.38, 1.39

[Jan P. <pa...@pi...>]

Hi Dan,

Thank you for the explanations. I don't have gettext ;)
I was curious because your changes really looked unnecessary.

 -- Jan

> On Thu, Jan 31, 2008 at 03:11:25PM +0100, Jan Patera wrote:
>> this is weird. Can you specify "strangely"? How come we didn't have
>> such problems in the past?
>
> It's a documented "bug" in gettext: "When an empty string is used for
> msgid, the functions may return a nonempty string."  I suspect it was
> added in a misguided attempt to be a feature, because the nonempty
> string it returns is actually the header from the .po file listing the
> translator, translation date, etc.   You can see if by reverting the
> patch and running
>
>   exif --tag=InteroperabilityVersion --ifd=Interoperability -s
>
> I saw it in gtkam, too, before this patch.
>
> I'm not completely positive why it didn't show up before.  Now that you
> mention it, the description in cases like this used to duplicate the
> title instead--now it's blank.  I'm not sure where that behaviour has
> changed.
>
>>>> Dan

Re: [Libexif-devel] [libexif-cvs] libexif/libexif exif-entry.c, 1.115, 1.116 exif-tag.c, 1.38, 1.39

[Dan F. <da...@co...>]

On Thu, Jan 31, 2008 at 11:16:48AM -0800, I wrote:
> I'm not completely positive why it didn't show up before.  Now that you
> mention it, the description in cases like this used to duplicate the title
> instead--now it's blank.  I'm not sure where that behaviour has changed.

The problem was displaying the description string was completely broken in
the previous version of exif. e.g. compare "exif --tag=Make -s"
with the old version and the CVS version.  This was probably due to reusing
a static buffer (in the "C" macro) in a printf.

>>> Dan
-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved

Re: [Libexif-devel] [libexif-cvs] libexif/libexif exif-entry.c, 1.115, 1.116 exif-tag.c, 1.38, 1.39

[Dan F. <da...@co...>]

On Thu, Jan 31, 2008 at 03:11:25PM +0100, Jan Patera wrote:
> this is weird. Can you specify "strangely"? How come we didn't have such
> problems in the past?

It's a documented "bug" in gettext: "When an empty string is used for
msgid, the functions may return a nonempty string."  I suspect it was
added in a misguided attempt to be a feature, because the nonempty string
it returns is actually the header from the .po file listing the translator,
translation date, etc.   You can see if by reverting the patch and running

  exif --tag=InteroperabilityVersion --ifd=Interoperability -s

I saw it in gtkam, too, before this patch.

I'm not completely positive why it didn't show up before.  Now that you
mention it, the description in cases like this used to duplicate the title
instead--now it's blank.  I'm not sure where that behaviour has changed.

>>> Dan
-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved

Re: [Libexif-devel] [libexif-cvs] libexif/libexif exif-entry.c, 1.115, 1.116 exif-tag.c, 1.38, 1.39

[Jan P. <pa...@pi...>]

Dan,

this is weird. Can you specify "strangely"? How come we didn't have such
problems in the past?

 -- Jan

> Modified Files:
> 	exif-entry.c exif-tag.c
> Log Message:
> GNU gettext behaves strangely when given an empty string, so make sure
> not to do that.
>
>
> Index: exif-tag.c
>
>  	if (ifd >= EXIF_IFD_COUNT) return NULL;
>  	for (i = 0; ExifTagTable[i].description; i++)
> -		if ((ExifTagTable[i].tag == tag) && RECORDED) break;
> -	return _(ExifTagTable[i].description);
> +		if ((ExifTagTable[i].tag == tag) && RECORDED) {
> +			/* GNU gettext acts strangely when given an empty string */
> +			if (!*ExifTagTable[i].description)
> +				return "";
> +			return _(ExifTagTable[i].description);
> +		}
> +	return NULL;
>  }

[Libexif-devel] New Dutch PO file for 'exif' (version 0.6.16-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'exif' has been submitted
by the Dutch team of translators.  The file is available at:

    http://translationproject.org/latest/exif/nl.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/exif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/exif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Czech PO file for 'libexif' (version 0.6.17-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'libexif' has been submitted
by the Czech team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/cs.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/libexif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/libexif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Dutch PO file for 'libexif' (version 0.6.17-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'libexif' has been submitted
by the Dutch team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/nl.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/libexif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/libexif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New Polish PO file for 'exif' (version 0.6.16-pre1)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'exif' has been submitted
by the Polish team of translators.  The file is available at:

    http://translationproject.org/latest/exif/pl.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/exif/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/exif.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>

[Libexif-devel] New template for 'exif' made available

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.  (If you have
any questions, send them to <coo...@tr...>.)

A new POT file for textual domain 'exif' has been made available
to the language teams for translation.  It is archived as:

    http://translationproject.org/POT-files/exif-0.6.16-pre1.pot

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

Below is the URL which has been provided to the translators of your
package.  Please inform the translation coordinator, at the address
at the bottom, if this information is not current:

    http://downloads.sourceforge.net/libexif/exif-0.6.15.tar.bz2

We can arrange things so that translated PO files are automatically e-mailed
to you when they arrive.  Ask at the address below if you want this.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>