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

[Libexif-devel] New Romanian PO file for 'exif' (version 0.6.18)

[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 Romanian team of translators.  The file is available at:

    http://translationproject.org/latest/exif/ro.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 supports Tiff?

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

On Fri, Jan 08, 2010 at 10:25:54AM -0600, Ou, Yech wrote:
> Hi,
> I'm new to the metadata/exif. I would like to add  Exif tags to both the jpeg
> and tiff files (and may be PNG) that might already have some Exif tags in them.
> I have these questions:
> 
> 1) all libexif samples are shown with jpeg format. Since the same exif tags can
> be contained in the tiff file, will I be able to use the libexif library to add
> tags into the tiff file (or png)?

libexif has only been used on EXIF files, to my knowledge. It only knows about
tags from the EXIF specs and not general TIFF tags, so you'll need to clear the
EXIF_DATA_OPTION_FOLLOW_SPECIFICATION and EXIF_DATA_OPTION_IGNORE_UNKNOWN_TAGS
options. It should be possible to extract the TIFF tag block from the
file and pass it in to exif_data_new_from_data() in order to use libexif.
An enhancement request has already been created for this feature:
http://sourceforge.net/tracker/?func=detail&aid=1957916&group_id=12272&atid=112272

> 2) Does the libexif library support adding new exif tags to a jpeg or tiff file
> that is already have some others or same exif tags? The sample write_exif.c
> mentioned that libjpeg may be used for existing jpeg instead of the libexif?
> I'm not sure the difference between these two: the libexif and libjpeg.

Yes, libexif allows adding tags to an existing JPEG file. See the action_set_value()
code path in the exif front-end to see how that's done. libjpeg (which is included
in the exif source code) is only used to insert the new EXIF tag block into the
right location in the JPEG data stream of the original file.  write-exif.c
deliberately avoids writing to an existing file both to simplify the example and
because libjpeg is included with exif and write-exif.c is part of libexif.

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

[Libexif-devel] libexif supports Tiff?

[Ou, Y. <Ye...@in...>]

Hi,
I'm new to the metadata/exif. I would like to add  Exif tags to both the
jpeg and tiff files (and may be PNG) that might already have some Exif
tags in them. I have these questions:
1) all libexif samples are shown with jpeg format. Since the same exif
tags can be contained in the tiff file, will I be able to use the
libexif library to add tags into the tiff file (or png)?
2) Does the libexif library support adding new exif tags to a jpeg or
tiff file that is already have some others or same exif tags? The sample
write_exif.c mentioned that libjpeg may be used for existing jpeg
instead of the libexif? I'm not sure the difference between these two:
the libexif and libjpeg. 
Thank you.
Yech



This message is intended only for the named recipient. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of this information is strictly prohibited.

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

[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 'exif' (version 0.6.18)

[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...>

Re: [Libexif-devel] [PATCH] pkg-config: private part for libm

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

On Tue, Dec 15, 2009 at 08:48:31PM +0100, Mathieu SCHROETER wrote:
> -lm should be used only for static linking. The patch moves
> the flag in Libs.private part of the pkg-config file.

Applied--thanks.

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

[Libexif-devel] New Swedish PO file for 'libexif' (version 0.6.19)

[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 Swedish team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/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/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] [PATCH] pkg-config: private part for libm

[Mathieu S. <mat...@ga...>]

Hello,

-lm should be used only for static linking. The patch moves
the flag in Libs.private part of the pkg-config file.


Regards,

Mathieu SCHROETER

Re: [Libexif-devel] User tag example

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

On Tue, Dec 08, 2009 at 07:10:28PM -0800, Dan Fandrich wrote:
> I'll update the write-exif.c code when an example like this when I get
> a chance.

FYI, I've checked in an update to the write-exif.c example program to show
how to create a new tag from scratch.

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

Re: [Libexif-devel] User tag example

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

On Tue, Dec 01, 2009 at 01:07:19PM +0200, Thomas Andrews wrote:
> Can anyone possibly share an example of how to use EXIF_TAG_USER_COMMENT

The example program contrib/examples/write-exif.c shows generally how to 
create tags in a file, but it "cheats" and only writes tags that are
created with default values in libexif. Changing the contents of an
existing tag is trivial, but creating one from scratch is trickier.
Unfortunately, EXIF_TAG_USER_COMMENT is one that isn't recognized by
exif_entry_initialize() so it falls into the "trickier" category.

You'll have to basically do this: Create an ExifEntry using
exif_entry_new_mem, providing your own ExifMem allocator. You can't use
exif_entry_new because you'll need access to the allocator to create
space for the entry. Next, use that allocator to create a memory block
and store the pointer in the "data" field of the ExifEntry you created.
Fill in the rest of the public ExifEntry members describing the data
(tag, format, etc.) and use exif_content_add_entry to attach the entry
to an IFD.  Finally, you can actually store the data you're interested
in, namely the comment.  Don't forget that the Exif standard specifies
a specific format for EXIF_TAG_USER_COMMENT, including the character
set used.

I'll update the write-exif.c code when an example like this when I get
a chance.

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

[Libexif-devel] User tag example

[Thomas A. <tan...@gr...>]

Hi,

Can anyone possibly share an example of how to use EXIF_TAG_USER_COMMENT

Many thanks,
Thomas

[Libexif-devel] New Danish PO file for 'libexif' (version 0.6.19)

[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 Danish team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/da.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 Japanese PO file for 'libexif' (version 0.6.19)

[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 Japanese team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/ja.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...>

Re: [Libexif-devel] R: Configure libexif in windows

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

> If you hand-craft a config.h file (using the MSYS-created one as a
> template), you should be able to compile under VS pretty easily by just
> creating a project with all the .c files in it.  libexif is very
> portable, so it shouldn't be more difficult than that.  If that doesn't
> work, please let us know.

It definitely does work.

 -- Jan

[Libexif-devel] New Danish PO file for 'libexif' (version 0.6.19)

[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 Danish team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/da.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...>

Re: [Libexif-devel] R: Configure libexif in windows

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

On Tue, Nov 24, 2009 at 07:56:24PM +0100, Michele Sottile wrote:
> Thank you for support, it really helped!
> I downloaded MSYS ( I thought I had it with Mingw; instead, they are two
> completely different things).
> I followed the instructions and all the commands have been executed.
> Using QtCreator I compiled everything.

Glad to see you had success.

> I guess I have no chances to compile libexif with Visual Studio 2008...:(

If you hand-craft a config.h file (using the MSYS-created one as a
template), you should be able to compile under VS pretty easily by just
creating a project with all the .c files in it.  libexif is very portable,
so it shouldn't be more difficult than that.  If that doesn't work,
please let us know.

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

[Libexif-devel] R: Configure libexif in windows

[Michele S. <m.s...@al...>]

Thank you for support, it really helped!
I downloaded MSYS ( I thought I had it with Mingw; instead, they are two
completely different things).
I followed the instructions and all the commands have been executed.
Using QtCreator I compiled everything.
I guess I have no chances to compile libexif with Visual Studio 2008...:(

Thank you all.
Michele Sottile

-----Messaggio originale-----
Da: Dan Fandrich [mailto:da...@co...] 
Inviato: lunedì 23 novembre 2009 22.18
A: lib...@li...
Oggetto: Re: [Libexif-devel] Configure libexif in windows

On Mon, Nov 23, 2009 at 08:06:12PM +0100, Michele Sottile wrote:
> Hi everybody,
> 
> I?m newbee and I?m interested in using libexif in my c++ software
(platform
> used: Windows XP service pack 3).
> 
> I?m using two editors, QtCreator and VisualStudio 2008, but I can?t find
any
> instructions to how configure libexif on Windows.
> 
> I downloaded libexif-0.6.19.zip, linked all the files in my program, but,
of
> course, the linker don?t find some .h file like config.h.
> 
> This because I didn?t configure the library.
> 
> Someone can tell me how I have to?
> 
> Thank you very much.

Windows build instructions are in the file README-Win32.txt, but it seems
this file isn't included in the source distribution. You can read it at
http://libexif.cvs.sourceforge.net/viewvc/libexif/libexif/README-Win32.txt?v
iew=markup
Basically, it says to use a MinGW32/MSYS environment and use the normal
configure process.

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

----------------------------------------------------------------------------
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus
on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
libexif-devel mailing list
lib...@li...
https://lists.sourceforge.net/lists/listinfo/libexif-devel

[Libexif-devel] [Fwd: Re: config.h file]

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

Michele,

I am forwarding you one older mail, hopefuly it helps you to get started
with config.h.

 -- Jan

-------- Původní zpráva --------
Předmět: Re: [Libexif-devel] config.h file
Od: Dan Fandrich <da...@co...>
Datum: 4 Březen 2009, 9:20
Komu: lib...@li...

On Wed, Feb 25, 2009 at 10:08:26PM -0800, Benny Smith wrote:
> Can you send me a copy of an example config.h file?  Perhaps I can use
> it as a template to create one for my application that can be
> #included in the libexif files where necessary.

Here's one generated for libexif on Linux. Naturally, you'll have to
add/remove the #defines/#undefs to match your platform. libexif's is
pretty simple compared to the config.h files generated for many other
projects.

> Since Dev-C++ and GCC (Gnu C) are apparently closely related, any
> config.h file that I create should work with either.

It's not just the compiler but the standard C library that define many
of the entries in the file.

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

Re: [Libexif-devel] Configure libexif in windows

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

On Mon, Nov 23, 2009 at 08:06:12PM +0100, Michele Sottile wrote:
> Hi everybody,
> 
> I?m newbee and I?m interested in using libexif in my c++ software (platform
> used: Windows XP service pack 3).
> 
> I?m using two editors, QtCreator and VisualStudio 2008, but I can?t find any
> instructions to how configure libexif on Windows.
> 
> I downloaded libexif-0.6.19.zip, linked all the files in my program, but, of
> course, the linker don?t find some .h file like config.h.
> 
> This because I didn?t configure the library.
> 
> Someone can tell me how I have to?
> 
> Thank you very much.

Windows build instructions are in the file README-Win32.txt, but it seems
this file isn't included in the source distribution. You can read it at
http://libexif.cvs.sourceforge.net/viewvc/libexif/libexif/README-Win32.txt?view=markup
Basically, it says to use a MinGW32/MSYS environment and use the normal
configure process.

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

[Libexif-devel] Configure libexif in windows

[Michele S. <m.s...@al...>]

Hi everybody,

I'm newbee and I'm interested in using libexif in my c++ software (platform
used: Windows XP service pack 3).

I'm using two editors, QtCreator and VisualStudio 2008, but I can't find any
instructions to how configure libexif on Windows.

I downloaded libexif-0.6.19.zip, linked all the files in my program, but, of
course, the linker don't find some .h file like config.h.

This because I didn't configure the library.

Someone can tell me how I have to? 

Thank you very much.

 

Michele Sottile

[Libexif-devel] New Japanese PO file for 'libexif' (version 0.6.19)

[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 Japanese team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/ja.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 template for 'libexif' 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 'libexif' has been made available
to the language teams for translation.  It is archived as:

    http://translationproject.org/POT-files/libexif-0.6.19.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/project/libexif/libexif/0.6.19/libexif-0.6.19.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...>

[Libexif-devel] New Italian PO file for 'exif' (version 0.6.18)

[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 Italian team of translators.  The file is available at:

    http://translationproject.org/latest/exif/it.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] libexif project security advisory

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

libexif project security advisory
November 12, 2009

PROBLEM DESCRIPTION

A flaw in libexif was discovered that causes a heap buffer to overflow
when certain invalid EXIF images are processed. The flaw occurs in the
tag fixup routine which attempts to convert in place an array of 8-bit
integers into 16-bit integers. This fixup is performed by default after
reading an image and until version 0.6.18 there was no easy way to disable
it, so it is likely that nearly all applications using libexif to read
images are vulnerable.

AFFECTED VERSIONS

Only libexif version 0.6.18 is affected by this flaw. Version 0.6.17 and
previous and 0.6.19 and later are not affected.

SOLUTION

Upgrade to version 0.6.19.

CHECKSUMS

Here are the MD5 sums of the released files:

75f0dd6f9f2d128261721c0896e0b324  exif-0.6.19.tar.bz2
c3928b8382b081cec9f5da862b15de9c  exif-0.6.19.tar.gz
56144a030a4c875c600b1ccf713f69f7  libexif-0.6.19.tar.bz2
986741d9e5e0cbf9642eb2893c885e8a  libexif-0.6.19.tar.gz
43ec0c469c3b17f3424fda7ddde0014d  libexif-0.6.19.zip

Here are the SHA1 sums of the released files:

1eeae082c60f2db36f289b80eaa7f7a68eedd266  exif-0.6.19.tar.bz2
3cbde4bf858053fc42668d681ccfb618ae1eaac1  exif-0.6.19.tar.gz
820f07ff12a8cc720a6597d46277f01498c8aba4  libexif-0.6.19.tar.bz2
ce669ea945beb9cd636f0dd8f723d006138aa13c  libexif-0.6.19.tar.gz
85f6a16b5e7fb2712ea57ec767fffdbb8477eef2  libexif-0.6.19.zip

REFERENCES

http://libexif.sf.net

[Libexif-devel] libexif and exif 0.6.19 released

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

This release fixes a security vulnerability found in libexif 0.6.18, plus
manages to squeeze in a substantial performance improvement. Also included
are new translations for be, en_GB, it, ja, pt, sq and zh_CN locales. Here
are a few more details:

libexif-0.6.19 (2009-11-12):
  * New translations: be, en_GB, it, ja, pt, sq, zh_CN
  * Updated translations: da, sv, vi
  * Now using a binary search to make searching through the tag table faster
  * Fixed a heap buffer overflow during tag format conversion

exif-0.6.19 (2009-11-12):
  * New translations: fi, ja
  * Updated translations: sv, vi, zh_CN
  * Fixed alignment of --list-tags header with --width

Here are the MD5 sums of the released file:

75f0dd6f9f2d128261721c0896e0b324  exif-0.6.19.tar.bz2
c3928b8382b081cec9f5da862b15de9c  exif-0.6.19.tar.gz
56144a030a4c875c600b1ccf713f69f7  libexif-0.6.19.tar.bz2
986741d9e5e0cbf9642eb2893c885e8a  libexif-0.6.19.tar.gz
43ec0c469c3b17f3424fda7ddde0014d  libexif-0.6.19.zip

Here are the SHA1 sums of the released file:

1eeae082c60f2db36f289b80eaa7f7a68eedd266  exif-0.6.19.tar.bz2
3cbde4bf858053fc42668d681ccfb618ae1eaac1  exif-0.6.19.tar.gz
820f07ff12a8cc720a6597d46277f01498c8aba4  libexif-0.6.19.tar.bz2
ce669ea945beb9cd636f0dd8f723d006138aa13c  libexif-0.6.19.tar.gz
85f6a16b5e7fb2712ea57ec767fffdbb8477eef2  libexif-0.6.19.zip

>>> Dan