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

[Libexif-devel] New Malay PO file for 'exif' (version 0.6.21)

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

    http://translationproject.org/latest/exif/ms.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 says good-bye to CVS

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

At long last, libexif has moved into the 21st century and has switched its
source code from CVS to git. The move was ultimately helped along by
Sourceforge's decision to shut down its CVS service by the end of this month,
but we can all reap the benefits of a much more modern and powerful source code
control system. The code now lives on Github at https://github.com/libexif/
with the home page moving to https://libexif.github.io.

The code in the repository hasn't been touched, which means some cleanups are
still to come to remove references to CVS and Sourceforge.  We'll also have to
decide how much of Sourceforge's infrastructure we'll continue to use (e.g.
mailing lists, the bug tracking system, etc.) but in the meantime, that will
remain as it is. However, pull requests are now possible, so feel free to take
advantage of that.

A couple of technical notes on the migration: the m4m module containing m4
macros used to be shared between the various CVS modules under the libexif
umbrella. Those have simply been copied into each git repo separately, rather
than trying to continue to share them using git submodules or other mechanisms.
The macros will now need to be kept in sync manually, when necessary. I was
able to contact almost all the individual authors who had a chance to select
the e-mail addresses to use to identify their contributions in git instead of
their Sourceforge username, so their contributions in the git history will be a
bit friendlier than before.  Finally, the CVS comments were in a mix of ISO
8859/1 and UTF-8 character encodings; I attempted to automatically convert
these into a consistent UTF-8, and spot checks seem to show that it worked.

This move lays down a welcome mat to a generation of programmers that perhaps
doesn't appreciate, um, the raw definitude of CVS. I look forward to more
contributions to help bring libexif itself back to the bleeding edge.

Dan

Re: [Libexif-devel] anyone alive?

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

Hi Dan,

Are you planning for a new release?

Ciao, Marcus
On Tue, Jul 25, 2017 at 04:42:56AM +0000, Dan Fandrich wrote:
> On Mon, Jul 24, 2017 at 01:25:11PM +0200, Marcus Meissner wrote: > > Anyone of the libexif admins/devs still alive?
> > 
> > I saw Dan committing things some weeks ago, but not much more :)
> 
> I am indeed alive.
> 
> > It needs some security fix work where I could help a bit.
> 
> Indeed. I've managed to find an occasional day to dedicate to libexif recently,
> and I'm starting to look at those issues. The trick is to investigate the
> issues, propose fixes, test them all and prepare it for release, all without
> making them public. But it's coming.
> 
> > A CVS -> GIT conversion might be needed too, libexif might
> > be one of the last CVS repos :/
> 
> That would be very nice, and would solve some of the issues above, but I think
> it would be better to wait until after the next release.
> 
> >>> Dan
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> libexif-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libexif-devel

Re: [Libexif-devel] anyone alive?

[Kostya S. <kc...@go...>]

Please also consider integrating libexif with OSS-Fuzz (service
for continuous fuzzing).
https://github.com/google/oss-fuzz
https://opensource.googleblog.com/2017/05/oss-fuzz-five-months-later-and.html
https://www.google.com/about/appsecurity/patch-rewards/

--kcc

On Mon, Jul 24, 2017 at 9:42 PM, Dan Fandrich <da...@co...>
wrote:

> On Mon, Jul 24, 2017 at 01:25:11PM +0200, Marcus Meissner wrote:
> > Anyone of the libexif admins/devs still alive?
> >
> > I saw Dan committing things some weeks ago, but not much more :)
>
> I am indeed alive.
>
> > It needs some security fix work where I could help a bit.
>
> Indeed. I've managed to find an occasional day to dedicate to libexif
> recently,
> and I'm starting to look at those issues. The trick is to investigate the
> issues, propose fixes, test them all and prepare it for release, all
> without
> making them public. But it's coming.
>
> > A CVS -> GIT conversion might be needed too, libexif might
> > be one of the last CVS repos :/
>
> That would be very nice, and would solve some of the issues above, but I
> think
> it would be better to wait until after the next release.
>
> >>> Dan
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> libexif-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libexif-devel
>

Re: [Libexif-devel] anyone alive?

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

Hi,

On Tue, Jul 25, 2017 at 06:42:56AM +0200, Dan Fandrich wrote:
> On Mon, Jul 24, 2017 at 01:25:11PM +0200, Marcus Meissner wrote:
> > Anyone of the libexif admins/devs still alive?
> > 
> > I saw Dan committing things some weeks ago, but not much more :)
> 
> I am indeed alive.
> 
> > It needs some security fix work where I could help a bit.
> 
> Indeed. I've managed to find an occasional day to dedicate to libexif recently,
> and I'm starting to look at those issues. The trick is to investigate the
> issues, propose fixes, test them all and prepare it for release, all without
> making them public. But it's coming.

I will see that I take on some of them. :)

Ciao, Marcus

Re: [Libexif-devel] anyone alive?

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

On Mon, Jul 24, 2017 at 01:25:11PM +0200, Marcus Meissner wrote:
> Anyone of the libexif admins/devs still alive?
> 
> I saw Dan committing things some weeks ago, but not much more :)

I am indeed alive.

> It needs some security fix work where I could help a bit.

Indeed. I've managed to find an occasional day to dedicate to libexif recently,
and I'm starting to look at those issues. The trick is to investigate the
issues, propose fixes, test them all and prepare it for release, all without
making them public. But it's coming.

> A CVS -> GIT conversion might be needed too, libexif might
> be one of the last CVS repos :/

That would be very nice, and would solve some of the issues above, but I think
it would be better to wait until after the next release.

>>> Dan

Re: [Libexif-devel] anyone alive?

[<jc...@gm...>]

On 24 July 2017 at 12:25, Marcus Meissner <ma...@je...> wrote:
> Anyone of the libexif admins/devs still alive?

Hi Marcus, I'm not a libexif dev or admin, but I would be happy to
help with maintenance if I can.

I use libexif for my image processing library and safety with
untrusted files is important to me.

John

[Libexif-devel] anyone alive?

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

Hi,

Anyone of the libexif admins/devs still alive?

I saw Dan committing things some weeks ago, but not much more :)

It needs some security fix work where I could help a bit.

A CVS -> GIT conversion might be needed too, libexif might
be one of the last CVS repos :/

Ciao, Marcus

[Libexif-devel] New Friulian PO file for 'exif' (version 0.6.21)

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

    http://translationproject.org/latest/exif/fur.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 Spanish PO file for 'libexif' (version 0.6.22-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 Spanish team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/es.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 Swedish PO file for 'libexif' (version 0.6.22-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 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] New Danish PO file for 'libexif' (version 0.6.22-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 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 Vietnamese PO file for 'libexif' (version 0.6.22-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 Vietnamese team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/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/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 'libexif' (version 0.6.22-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 Polish team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/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/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 Ukrainian PO file for 'libexif' (version 0.6.22-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 Ukrainian team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/uk.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 French PO file for 'libexif' (version 0.6.22-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 French team of translators.  The file is available at:

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

    https://sourceforge.net/projects/libexif/files/libexif/prerelease/libexif-0.6.22-pre1.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...>

Re: [Libexif-devel] ECCN number for libexif

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

Hi,

as libexif does not contain or consume cryptographic code ... It probably does not need such a number
or this magic one you mentioned.

Ciao, Marcus
On Fri, Jun 17, 2016 at 06:23:24AM +0000, Seitz, Hans-Juergen wrote:
> Dear all, does anybody know the ECCN number for libexif? I suppose it is ECCN EAR99 (NLR, No license required), but I could not find anything which approves this.
> Thanks in Advance! Hans-Juergen

> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports. http://sdm.link/zohomanageengine

> _______________________________________________
> libexif-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libexif-devel

Re: [Libexif-devel] ECCN number for libexif

[Mario B. <mar...@gm...>]

Regarding the need of an ECCN number for GPL software, have a look at the
Cygwin licensing site (last paragraph refers to ECCN):
https://cygwin.com/licensing.html

Best regards,
Mario
Am 17.06.2016 8:58 vorm. schrieb "Seitz, Hans-Juergen" <
han...@ze...>:

> Dear all, does anybody know the ECCN number for libexif? I suppose it is ECCN
> EAR99 (NLR, No license required), but I could not find anything which
> approves this.
>
> Thanks in Advance! Hans-Juergen
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports. http://sdm.link/zohomanageengine
> _______________________________________________
> libexif-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libexif-devel
>
>

[Libexif-devel] ECCN number for libexif

[Seitz, Hans-J. <han...@ze...>]

Dear all, does anybody know the ECCN number for libexif? I suppose it is ECCN EAR99 (NLR, No license required), but I could not find anything which approves this.
Thanks in Advance! Hans-Juergen

Re: [Libexif-devel] libexif's libjpeg

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

On Fri, May 27, 2016 at 12:14:18AM -0700, Cindy Xiao wrote:
> Hi,
> 
> I recently wanted to start using libexif to read EXIF data from one JPEG
> file and write it onto another, existing JPEG file. I see that there is a
> small library called libjpeg that is packaged with the exif command-line
> tool, and also that some of the example code (such as cam_features.c
> <http://libexif.cvs.sourceforge.net/viewvc/libexif/libexif/contrib/examples/cam_features.c?revision=1.2&view=markup>)
> uses it to write EXIF data to existing JPEG files. I have a few questions
> about libjpeg:
> 
>    - Does this libjpeg library have any relation with the Independent JPEG
>    Group’s libjpeg <http://libjpeg.sourceforge.net/>?

>    - Is there any reason why it is bundled with the exif command-line tool
>    and not advertised or offered as a standalone library?

The builtin libjpeg in exif is a very small subset of the libjpeg functionality,
basically only allowing marker extraction / insertion (what is needed for exif tag
adjustment).

It is not related to the IJPEG Group libjpeg.

If it makes sense to externally have it ... it is very small and I dont know :.

Ciao, Marcus

[Libexif-devel] libexif's libjpeg

[Cindy X. <di...@ua...>]

Hi,

I recently wanted to start using libexif to read EXIF data from one JPEG
file and write it onto another, existing JPEG file. I see that there is a
small library called libjpeg that is packaged with the exif command-line
tool, and also that some of the example code (such as cam_features.c
<http://libexif.cvs.sourceforge.net/viewvc/libexif/libexif/contrib/examples/cam_features.c?revision=1.2&view=markup>)
uses it to write EXIF data to existing JPEG files. I have a few questions
about libjpeg:

   - Does this libjpeg library have any relation with the Independent JPEG
   Group’s libjpeg <http://libjpeg.sourceforge.net/>?
   - Is there any reason why it is bundled with the exif command-line tool
   and not advertised or offered as a standalone library?

Thanks,
Cindy
​

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

[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] New Swedish PO file for 'libexif' (version 0.6.21)

[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] New Korean PO file for 'exif' (version 0.6.21)

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

    http://translationproject.org/latest/exif/ko.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...>