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

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

[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 Polish PO file for 'libexif' (version 0.6.17)

[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 Polish PO file for 'exif' (version 0.6.17)

[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 Dutch PO file for 'libexif' (version 0.6.17)

[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 Dutch PO file for 'exif' (version 0.6.17)

[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 Indonesian PO file for 'exif' (version 0.6.17)

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

    http://translationproject.org/latest/exif/id.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 '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.17.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://garr.dl.sourceforge.net/sourceforge/libexif/libexif-0.6.17.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 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.17.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://garr.dl.sourceforge.net/sourceforge/libexif/exif-0.6.17.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] Removing the Patches and Support Requests trackers

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

Right now, the libexif project has four categories of tracker entries enabled
at SourceForge: Bugs, Feature Requests, Patches and Support Requests.  I
propose removing the last two, since for a project like libexif they're
redundant.

People submitting patches will be submitting them to fix bugs or introduce
new features--the two existing categories (the two current outstanding
patches would be perfectly at home in the Bugs category).  Having a
Support Requests category implies that someone will be reading them and
replying to them.  Unfortunately, we don't seem to have the manpower here
to do that. The existing support request entries date back to 2003 and almost
all of them have gone unanswered.  New support requests should be directed
to this mailing list where they'll have a chance of being noticed and
answered, or filed under the Feature Requests category.

If noone disagrees, I'll recategorize the open items and likely bring a few
still-relevant items to this list.

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

[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] libexif and exif 0.6.17 released

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

libexif version 0.6.17 and the exif command-line front-end have been
released.  They are identical to the release candidate I posted a few days
ago.  The major changes since the last release are as follows:

libexif-0.6.17 (2008-11-06):
  * Updated translations: cs, de, pl, sk, vi
  * New translations: nl, se, en_CA
  * Enabled sv translation by default
  * Bug fixes: #1773810, #1774626, #1536244, CVE-2007-6351, CVE-2007-6352,
    #2071600 and others
  * Enhanced support of Canon and Olympus makernotes 
  * Added support for Fuji and Sanyo makernotes
  * Added support for the NO_VERBOSE_TAG_STRINGS and NO_VERBOSE_TAG_DATA
    macros to reduce size for embedded applications
  * Added support for more tags

exif-0.6.17 (2008-11-06):
  * Fixed the output of -s and -t when iconv is configured
  * Updated translations: pl
  * Added translations: id nl sk sv vi zh_CN
  * Fixed a double character encoding conversion problem with recent
    GNU gettext because version >= 0.10.36 does the conversion of message
    texts itself.

Thank-you to everyone who contributed to this release.

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

Re: [Libexif-devel] listing headers

[Torsten C. <tc...@va...>]

>> (I would have expected a simple double printed though)
>
> Well, this is what libexif does: it simply prints 3 doubles because
> there are 3 values.

True ... I meant as a single double.

http://www.flickr.com/geoformats.gne

But anyway

> Hmm, did you read my second mail?

Sorry, thought you meant use - not change or copy.

> Check what exif_entry_initialize does
> for e.g. EXIF_TAG_EXIF_VERSION. You should either
> 1) adapt exif_entry_initialize so that it suports also GPS tags
>  (currently it does not)
> 2) copy-past-adapt the code from exif_entry_initialize to your code:

For now I just want to get the POC working. But I will provide a patch
once it's there.
So for now I went with 2)

    static void set_value(ExifEntry *entry, ExifTag tag, ExifByteOrder
order, double value)
    {
        entry->tag = tag;
        entry->components = 3;
        entry->format = EXIF_FORMAT_RATIONAL;
        entry->size = exif_format_get_size(entry->format) * entry->components;

        entry->data = exif_entry_alloc(entry, entry->size);
        if (!entry->data) return;

        // dd/1,mm/1,ss/1 dd/1,mmmm/100,0/1
        ExifRational value1;
        value1.numerator = 1;
        value1.denominator = 1;
        ExifRational value2;
        value2.numerator = 1;
        value2.denominator = 1;
        ExifRational value3;
        value3.numerator = 1;
        value3.denominator = 1;

        exif_set_rational(entry->data, order, value1);
        exif_set_rational(entry->data+sizeof(ExifRational), order, value2);
        exif_set_rational(entry->data+2*sizeof(ExifRational), order, value3);
    }

Still needs the double -> rationals conversion though. Would be nice
if libexif would support some of that a little better. Especially with
exif_entry_alloc not being available outside.

cheers
--
Torsten

Re: [Libexif-devel] listing headers

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

> On Thu, Nov 6, 2008 at 10:22 PM, Jan Patera <pa...@pi...> wrote:
>>>     Longitude = 89.00, 40.00, 11.16
>>>
> (I would have expected a simple double printed though)

Well, this is what libexif does: it simply prints 3 doubles because
there are 3 values.

> What I haven't worked out yet is how to set 3 rationals.
>
>         entry_lon = exif_entry_new();
>         exif_entry_initialize(entry_lon, EXIF_TAG_GPS_LONGITUDE);
>
>         ExifRational value;
>         value.numerator = 54
>         value.denominator = 1;
>
>         exif_set_rational(entry_lon->data, exif_data_get_byte_order(ed),
> value);
>
>         exif_content_add_entry(ed->ifd[EXIF_IFD_GPS], entry_lon);
>
>         exif_entry_unref(entry_lon);
>
> According to the spec there are 3 rationals. But I have no idea how to
> do that with the API.
>
> May I ask for another pointer? :)

Hmm, did you read my second mail? Check what exif_entry_initialize does
for e.g. EXIF_TAG_EXIF_VERSION. You should either
1) adapt exif_entry_initialize so that it suports also GPS tags
  (currently it does not)
2) copy-past-adapt the code from exif_entry_initialize to your code:

 e->components = 3; // Use the correct number
 e->format = EXIF_FORMAT_xxxx; // Use correct format. RATIONAL?
 e->size = exif_format_get_size (e->format) * e->components;
 e->data = exif_entry_alloc (e, e->size);
 if (!e->data) fail;

 exif_set_rational(e->data, o, value1);
 exif_set_rational(e->data+sizeof(ExifRational), o, value2);
 exif_set_rational(e->data+2*sizeof(ExifRational), o, value3);

 -- Jan

Re: [Libexif-devel] listing headers

[Torsten C. <tc...@va...>]

On Thu, Nov 6, 2008 at 10:22 PM, Jan Patera <pa...@pi...> wrote:
>>     Longitude = 89.00, 40.00, 11.16
>>
>> For one the Longitude format is awkward.
>> Using exiv2 on the file I get
>>  0x0004 GPSInfo      GPSLongitude                Rational    3  89/1
>> 40/1 6978/625
>
> Which format would you like libexif to use? The same format as exiv2 uses,
> i.e. the exact fractions?

Actually - never mind. Just had a look at the spec and found the
exif_set_rational/exif_get_rational ... so that's just the textual
representation. And doesn't really matter that much. (I would have
expected a simple double printed though)

What I haven't worked out yet is how to set 3 rationals.

        entry_lon = exif_entry_new();
        exif_entry_initialize(entry_lon, EXIF_TAG_GPS_LONGITUDE);

        ExifRational value;
        value.numerator = 54
        value.denominator = 1;

        exif_set_rational(entry_lon->data, exif_data_get_byte_order(ed), value);

        exif_content_add_entry(ed->ifd[EXIF_IFD_GPS], entry_lon);

        exif_entry_unref(entry_lon);

According to the spec there are 3 rationals. But I have no idea how to
do that with the API.

May I ask for another pointer? :)

cheers
--
Torsten

Re: [Libexif-devel] listing headers

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

>     Longitude = 89.00, 40.00, 11.16
>
> For one the Longitude format is awkward.
> Using exiv2 on the file I get
>  0x0004 GPSInfo      GPSLongitude                Rational    3  89/1
> 40/1 6978/625

Which format would you like libexif to use? The same format as exiv2 uses,
i.e. the exact fractions?

 -- Jan

Re: [Libexif-devel] listing headers

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

Hi,

> Now how do I update or add exif information if not available?
> I assume I would have to create a new exif entry with exif_entry_new()
> Not sure how to fill it properly though.
> For example there is no exif_entry_set_value(). Will I have to modify
> the struct directly?

When the entry doesn't exist yet, you should do something like this:
1) e = exif_entry_new()
2) do something similar that exif_entry_initialize does for e.g.
EXIF_TAG_EXIF_VERSION. Here you will have to set the correct
value(s) using something like
exif_set_short(e->data, exif_data_get_byte_order(e->parent->parent), val);
3) exif_content_add_entry(ifd, e);
4) exif_entry_unref(e);

Hope this helps.
                    -- Jan

Re: [Libexif-devel] listing headers

[Torsten C. <tc...@va...>]

Hey Stanislav,

Thanks for the quick feedback.

> This is broken and can never work, as tags are unique only per IFD, not
> per EXIF. Use exif_tag_get_title_in_ifd.

I see ... makes sense

Actually I was after the GPS information anyway. So I ended up with

    ExifEntry *entry_lat = exif_data_get_entry(ed, EXIF_TAG_GPS_LATITUDE);
    if (exif_entry_get_value(entry_lat, value, sizeof(value))) {
        NSLog(@"lat = %s", value);
    }

    ExifEntry *entry_latref = exif_data_get_entry(ed,
EXIF_TAG_GPS_LATITUDE_REF);
    if (exif_entry_get_value(entry_latref, value, sizeof(value))) {
        NSLog(@"latref = %s", value);
    }

    ExifEntry *entry_lon = exif_data_get_entry(ed, EXIF_TAG_GPS_LONGITUDE);
    if (exif_entry_get_value(entry_lon, value, sizeof(value))) {
        NSLog(@"lon = %s", value);
    }

    ExifEntry *entry_lonref = exif_data_get_entry(ed,
EXIF_TAG_GPS_LONGITUDE_REF);
    if (exif_entry_get_value(entry_lonref, value, sizeof(value))) {
        NSLog(@"lonref = %s", value);
    }

Which seems to work just fine. Now how do I update or add exif
information if not available?
I assume I would have to create a new exif entry with exif_entry_new()
Not sure how to fill it properly though.
For example there is no exif_entry_set_value(). Will I have to modify
the struct directly?

Any pointers?

cheers
--
Torsten

Re: [Libexif-devel] listing headers

[Stanislav B. <sb...@su...>]

Torsten Curdt wrote:

>         for (t = 0; t < 0xffff; t++) {
>             name = exif_tag_get_title(t);
>             if (!name) {
>                 continue;
>             }

This is broken and can never work, as tags are unique only per IFD, not
per EXIF. Use exif_tag_get_title_in_ifd.

This bad assumption causes failure of GPS Latitude in most applications
based on libexif (eog, libexif-gtk,...)

libexif API is very confusing here. ExifTag is enum, something that is
expected to be unique. But arguments of type ExifTag are not unique!

To be able to implement such an ugly hack without compiler complains,
half of these tags are defined in enum, the other half by #define.

And there is not a better way to "list all tags currently known to
libexif" than querying all 65536x5 possible tag/ifd combinations.

There is another ugly hack to make this query with only 65538 steps:
http://sourceforge.net/tracker/download.php?group_id=12272&atid=312272&file_id=284116&aid=2014281

> But it seems like I am not getting all information
> 
>     idf: GPS
>     GPS tag version = 0x02, 0x02, 0x00, 0x00
>     InteroperabilityIndex = N
>     InteroperabilityVersion = 30.00, 13.00, 53.58
>     East or West Longitude = W
>     Longitude = 89.00, 40.00, 11.16

-- 
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                          e-mail: sb...@su...
Lihovarská 1060/12           tel: +420 284 028 966, +49 911 740538747
190 00 Praha 9                                  fax: +420 284 028 951
Czech Republic                                    http://www.suse.cz/

[Libexif-devel] listing headers

[Torsten C. <tc...@va...>]

Hey folks,

Need some help with the API. Goal is to add/modify the GPS bit in the
exif information. But for now I just wanted to see what exif headers
are set. So I am iterating:

    unsigned int i;
    unsigned int t;
    const char *name;
    char value[128];
    const char *v;

    for (i = 0; i < EXIF_IFD_COUNT; i++) {
        ExifContent *ifd = ed->ifd[i];

        const char *ifd_name = exif_ifd_get_name(i);

        if (!ifd_name) {
            continue;
        }

        NSLog(@"idf: %s", ifd_name);

        for (t = 0; t < 0xffff; t++) {
            name = exif_tag_get_title(t);
            if (!name) {
                continue;
            }

            ExifEntry *entry = exif_content_get_entry(ifd, t);
            if (!entry) {
                continue;
            }

            v = exif_entry_get_value(entry, value, sizeof(value));

            if (!v) {
                continue;
            }

            NSLog(@"%s = %s", name, value);
        }
    }

But it seems like I am not getting all information

    idf: GPS
    GPS tag version = 0x02, 0x02, 0x00, 0x00
    InteroperabilityIndex = N
    InteroperabilityVersion = 30.00, 13.00, 53.58
    East or West Longitude = W
    Longitude = 89.00, 40.00, 11.16

For one the Longitude format is awkward. But more importantly - the
Latitude is missing. Using exiv2 on the file I get

 0x0000 GPSInfo      GPSVersionID                Byte        4  2 2 0 0
 0x0001 GPSInfo      GPSLatitudeRef              Ascii       2  N
 0x0002 GPSInfo      GPSLatitude                 Rational    3  30/1
13/1 133941/2500
 0x0003 GPSInfo      GPSLongitudeRef             Ascii       2  W
 0x0004 GPSInfo      GPSLongitude                Rational    3  89/1
40/1 6978/625

What am I doing wrong?

Oh btw: I came across this as well

  Unknown tag 0x882a (entry 9 in '0'). Please report this tag to
<lib...@li...>.

cheers
--
Torsten

[Libexif-devel] 0.6.17 release candidate

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

I've uploaded RC1 packages of libexif and exif 0.6.17 temporarily to
http://www.npsnet.com/danf/software/exif/  Please try them out and unless
someone reports something wrong by tomorrow, I'll release them officially.

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

[Libexif-devel] New German 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 German team of translators.  The file is available at:

    http://translationproject.org/latest/exif/de.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 German 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 German team of translators.  The file is available at:

    http://translationproject.org/latest/libexif/de.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] Time for a libexif release

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

On Tue, Nov 04, 2008 at 09:51:59PM -0800, Dan Fandrich wrote:
> On Tue, Nov 04, 2008 at 06:01:17PM +0100, Marcus Meissner wrote:
> > I now submitted de.po to translation project. There were around 4 strings or
> > so changed judging from the diff I have.
> 
> The "new" version at translationproject.org actually regressed to older
> .pot file.  The one in libexif's CVS was based on the 2007-12-14 .pot file
> (the latest officially released one), but the version I just rsync'ed from
> tp.org is based on the 2007-06-12 .pot file.  That means it's missing a
> bunch of translations that were previously done (you can see them
> commented out at the end of the file).

Hmm. :/

Ciao, Marcus

Re: [Libexif-devel] Time for a libexif release

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

On Tue, Nov 04, 2008 at 06:01:17PM +0100, Marcus Meissner wrote:
> I now submitted de.po to translation project. There were around 4 strings or
> so changed judging from the diff I have.

The "new" version at translationproject.org actually regressed to older
.pot file.  The one in libexif's CVS was based on the 2007-12-14 .pot file
(the latest officially released one), but the version I just rsync'ed from
tp.org is based on the 2007-06-12 .pot file.  That means it's missing a
bunch of translations that were previously done (you can see them
commented out at the end of 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] Python binding and Watcom contribs

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

On Tue, Nov 04, 2008 at 04:24:59PM -0800, I wrote:
> There are two entries in the libexif/contribs directory: a Python wrapper
> and a Watcom makefile. Both no longer work due to changes to libexif. 
> Neither of them were in the 0.6.16 release, so I guess it's not a big deal
> if they're not in the imminent release, but is someone willing to fix them
> up for next time?

Also included in this is category the module in the aolserver directory. 
That should really be moved under contrib as well.

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