You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
|
Jun
(5) |
Jul
(17) |
Aug
(4) |
Sep
(5) |
Oct
(5) |
Nov
(26) |
Dec
(6) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(8) |
Feb
|
Mar
(3) |
Apr
(3) |
May
|
Jun
|
Jul
(4) |
Aug
(18) |
Sep
(9) |
Oct
(8) |
Nov
(5) |
Dec
(4) |
2004 |
Jan
(10) |
Feb
(1) |
Mar
(7) |
Apr
(11) |
May
(13) |
Jun
(5) |
Jul
(3) |
Aug
|
Sep
|
Oct
(15) |
Nov
(6) |
Dec
(10) |
2005 |
Jan
(1) |
Feb
(1) |
Mar
(25) |
Apr
(24) |
May
(9) |
Jun
(20) |
Jul
(13) |
Aug
(4) |
Sep
(17) |
Oct
(7) |
Nov
(2) |
Dec
(11) |
2006 |
Jan
(30) |
Feb
(12) |
Mar
(12) |
Apr
(12) |
May
(7) |
Jun
(12) |
Jul
(14) |
Aug
(16) |
Sep
(20) |
Oct
(16) |
Nov
(35) |
Dec
(42) |
2007 |
Jan
(34) |
Feb
(34) |
Mar
(29) |
Apr
(116) |
May
(42) |
Jun
(25) |
Jul
(4) |
Aug
(9) |
Sep
|
Oct
(2) |
Nov
(4) |
Dec
(10) |
2008 |
Jan
(9) |
Feb
(7) |
Mar
(2) |
Apr
(5) |
May
(2) |
Jun
(3) |
Jul
(3) |
Aug
|
Sep
(7) |
Oct
(4) |
Nov
(42) |
Dec
(20) |
2009 |
Jan
(12) |
Feb
(12) |
Mar
(1) |
Apr
(4) |
May
(2) |
Jun
(4) |
Jul
|
Aug
(3) |
Sep
(23) |
Oct
(34) |
Nov
(16) |
Dec
(8) |
2010 |
Jan
(5) |
Feb
(9) |
Mar
(3) |
Apr
(5) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
(14) |
2011 |
Jan
(4) |
Feb
|
Mar
(3) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
(1) |
Oct
(1) |
Nov
(6) |
Dec
(4) |
2012 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
(10) |
May
(11) |
Jun
|
Jul
(21) |
Aug
(7) |
Sep
|
Oct
(1) |
Nov
(4) |
Dec
|
2013 |
Jan
(1) |
Feb
(6) |
Mar
(11) |
Apr
(2) |
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
(4) |
Oct
|
Nov
(3) |
Dec
(7) |
2014 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(8) |
May
(1) |
Jun
(6) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
(2) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
(2) |
Jun
(3) |
Jul
|
Aug
|
Sep
(8) |
Oct
|
Nov
|
Dec
(1) |
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2020 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
(14) |
Jun
(8) |
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
(1) |
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(1) |
Nov
(5) |
Dec
(5) |
2022 |
Jan
(3) |
Feb
(2) |
Mar
|
Apr
(2) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2023 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
From: Valere M. <val...@ym...> - 2013-03-08 19:46:28
|
> At long last, here this decade's release of libexif-gtk! > Yeaaaah!! > Thanks to everyone who contributed to this release > Thanks a lot to you, Dan! I know it was not at all your priority and really appreciate the time you've passed on it. Remark: if you are interested, I also migrated gexif the same way (completely forgotten that I dit it). |
From: Translation P. R. <ro...@tr...> - 2013-03-08 01:37:16
|
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...> |
From: Dan F. <da...@co...> - 2013-03-07 22:12:44
|
At long last, here this decade's release of libexif-gtk! The biggest change in this version is support for modern versions of GTK+. The major differences from 0.3.5 include: * New translations: de, pl * Updated translations: es, fr, ru * Bug fixes: #1643242: added libexif-gtk-uninstalled.pc file * Proper setting of gettext parameters * libexif-gtk made compatible for both gtk2 (min version: 2.4) and gtk3 * added --with-gtk3 option in configure.ac (default is gtk2) * encoding of source files set to utf-8 * encoding of ru translation file set to utf-8 * fixed internationalisation bugs in gtk-options.c & configure.ac * fixed bugs linked to gtk_notebook_remove_page action * Bug fixes: #2014281: fix display of GPSLatitude and GPSLatitudeRef names * fixed crash when viewing an enumerated tag with an unsupported value * fixed problem with handling the Flash tag in big-endian images * fixed thumbnail save function to actually save Thanks to everyone who contributed to this release, and especially to Valere Monseur who contributed the major GTK+ fixes. Here are the SHA1 sums of the released files: d73facc8beeae9e365b09a3fbc4f6e404a474e12 libexif-gtk-0.4.0.tar.bz2 08aa3f136c507d81f642683125fd7b408d43c830 libexif-gtk-0.4.0.tar.gz They are available for download at https://sourceforge.net/projects/libexif/files/libexif-gtk/0.4.0/ >>> Dan |
From: Valere M. <val...@ym...> - 2013-02-24 15:53:42
|
>At long last, I've uploaded a release candidate for libexif-gtk up at >http://sourceforge.net/projects/libexif/files/libexif-gtk/0.4.0-beta1/libexif-gtk-0.4.0-beta1.tar.bz2/download >Please try it out if you can and report any problems you have here. Barring >any major issues, I'll make an official public release next week. Hi, Thanks for the release, it works ok on my side. I've published the beta1 in the AUR (Archlinux User Repository) so any problem will be reported to me (as package maintainer). Regards, Valère |
From: Dan F. <da...@co...> - 2013-02-23 23:26:33
|
At long last, I've uploaded a release candidate for libexif-gtk up at http://sourceforge.net/projects/libexif/files/libexif-gtk/0.4.0-beta1/libexif-gtk-0.4.0-beta1.tar.bz2/download Please try it out if you can and report any problems you have here. Barring any major issues, I'll make an official public release next week. >>> Dan |
From: Dan F. <da...@co...> - 2013-02-10 19:21:01
|
On Sun, Feb 10, 2013 at 11:35:15AM +0100, Casper wrote: > > Thanks a lot for the idea, it works perfectly with the latest version of > > CVS. > So this is the review request: > https://bugzilla.redhat.com/show_bug.cgi?id=909671 Thanks for confirming that. I checked back through the relevant thread, and it turns out that the only thing this release is left waiting on is me! I'll try to get off my butt this week and get it out. >>> Dan |
From: Casper <fa...@fe...> - 2013-02-10 10:35:27
|
Le dimanche 10 février 2013 à 02:17 +0100, Casper a écrit : > Le samedi 09 février 2013 à 12:26 +0100, Dan Fandrich a écrit : > > There have been some major changes in the CVS version since the last release, > > awaiting a new release. Would you mind trying that version and see if > > that solves these problems? > Thanks a lot for the idea, it works perfectly with the latest version of > CVS. So this is the review request: https://bugzilla.redhat.com/show_bug.cgi?id=909671 -- Pour encrypter vos emails Clef GPG ID : 83288189 @ hkp://pgp.mit.edu:11371 Empreinte : CC26 692F 5205 AC8F 7912 7783 D7A7 F4C5 8328 8189 |
From: Dan F. <da...@co...> - 2013-02-09 11:45:51
|
On Sat, Feb 09, 2013 at 03:56:08AM +0100, Casper wrote: > Dear devs, > I'm trying to package libexif-gtk for Fedora distribution, but I > encountered a problem during the 'make'... > Complete output is in attachment of this email. > I used the standard procedure of build (./configure, make) > > For information, the build is done in a chroot of Fedora 18 x86_64 > (chroot initialized by mock software) with libexif-devel and gtk2-devel > packages installed. > > Could you fix the problem please ?... There have been some major changes in the CVS version since the last release, awaiting a new release. Would you mind trying that version and see if that solves these problems? >>> Dan |
From: Casper <fa...@fe...> - 2013-02-09 02:56:21
|
Dear devs, I'm trying to package libexif-gtk for Fedora distribution, but I encountered a problem during the 'make'... Complete output is in attachment of this email. I used the standard procedure of build (./configure, make) For information, the build is done in a chroot of Fedora 18 x86_64 (chroot initialized by mock software) with libexif-devel and gtk2-devel packages installed. Could you fix the problem please ?... Best regards, Matthieu Saulnier -- Pour encrypter vos emails Clef GPG ID : 83288189 @ hkp://pgp.mit.edu:11371 Empreinte : CC26 692F 5205 AC8F 7912 7783 D7A7 F4C5 8328 8189 |
From: Andre T. <an...@lc...> - 2013-01-15 16:50:03
|
Hello, Let's say I have an image file "img01.jpg", which was taken using "Super Awesome Phone". This code, http://pastebin.com/ETYrHU3Z, displays the camera model correctly. What I'd like to ask is how the replace "Super Awesome Phone" (which is identified by EXIF_TAG_MODEL) with another value, e.g "Nokia 2112" I added these lines in main(): // init_tag is taken from http://libexif.cvs.sourceforge.net/viewvc/libexif/libexif/contrib/examples/write-exif.c?view=markup entry = init_tag(ed, EXIF_IFD_EXIF, EXIF_TAG_MODEL); exif_set_long(entry->data, FILE_BYTE_ORDER, atol("Nokia 3330")); But it didn't work. Nothing was changed. How could I fix this? -- *Andre Tampubolon* GPG public key:pgp.mit.edu:11371/pks/lookup?op=get&search=0xC6492E7D01AA96CF |
From: Translation P. R. <ro...@tr...> - 2012-11-29 20:32:17
|
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...> |
From: Dan F. <da...@co...> - 2012-11-12 21:55:48
|
On Tue, Nov 06, 2012 at 09:58:58PM +0000, Valere Monseur wrote: > I've (finally) looked at the bug. There are 3 different parts: Thanks for looking at this! Unfortunately, my development PC has died, so I won't get a chance to look at this right away. But, I think it's about time for a libexif-gtk release. >>> Dan |
From: Valere M. <val...@ym...> - 2012-11-06 21:59:08
|
Hi, >I also noticed a bug in the tracker that's been waiting 4 >years for someone who knows libexif-gtk to take a look. Would you mind >taking a peek? >http://sourceforge.net/tracker/?func=detail&aid=2014281&group_id=12272&atid=112272 I've (finally) looked at the bug. There are 3 different parts: 1) Port to the new libexif API is already implemented. No action required. 2) Fixes done: Deprecated exif_tag_get_title changed into exif_tag_get_name_in_ifd. Deprecated exif_tag_get_description changed into exif_tag_get_description_in_ifd. Deprecated exif_tag_get_name changed into exif_tag_get_name_in_ifd. 3) Some changes are not completely possible: There is no way in libexif to get all known tags per ifd. So changes in gtk-exif-content-list.c are only partially done. Patch can be found here: http://sourceforge.net/projects/vmonseur.u/files/libexif-gtk/bug-2014281.patch/download Regards Valère. |
From: Translation P. R. <ro...@tr...> - 2012-11-02 00:17:47
|
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...> |
From: Translation P. R. <ro...@tr...> - 2012-10-06 15:12:12
|
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...> |
From: Pavan K. <pav...@gm...> - 2012-08-20 04:59:39
|
Hi, Looks like we might need some fixes in the utility functions. http://stackoverflow.com/questions/12032122/integer-overflow-not-consistent Let me know if you disagree. Regards, Pavan On Mon, Aug 6, 2012 at 4:11 PM, Pavan Kulkarni <pav...@gm...> wrote: > Hi Jan, All > Pardon me for the naive question. > I see that most functions in exif-utils.c (such as exif_get_short() ) are > of type uintxx_t but they actually return value of type intxx_t (the > mentioned function internally calls exif_get_sshort) > Will this not cause undefined behavior? > For the problem I described, I suspect this to be an issue. > Any inputs will be much appreciated. > > Regards > Pavan > > On Fri, Aug 3, 2012 at 12:28 PM, Jan Patera <pa...@pi...> wrote: > >> Pavan, >> >> looks like you have a 64bit build? If so, could you please provide me your >> JPG file? >> libexif has not been tested well on 64 bit platforms yet. >> >> --- Jan >> >> > On further debugging, found that I'm getting an invalid tag from the raw >> > IFD data. >> > I think it is expected to get this tag EXIF_TAG_EXIF_IFD_POINTER >> (0x8769) >> > .. But I'm actually getting (0xFFFFFFFFFFFF8769) which messes up the >> whole >> > tag extraction and gives an unknown tag which is negative -30871 >> > Does anyone have any clue about this problem... >> > Strangely, it works fine on my linux machine. >> > >> > Regards, >> > Pavan >> > >> ------------------------------------------------------------------------------ >> > Live Security Virtual Conference >> > Exclusive live event will cover all the ways today's security and >> > threat landscape has changed and how IT managers can respond. >> Discussions >> > will include endpoint security, mobile security and the latest in >> malware >> > threats. >> > >> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ >> > libexif-devel mailing list >> > lib...@li... >> > https://lists.sourceforge.net/lists/listinfo/libexif-devel >> > >> >> >> > |
From: Pavan K. <pav...@gm...> - 2012-08-06 10:41:29
|
Hi Jan, All Pardon me for the naive question. I see that most functions in exif-utils.c (such as exif_get_short() ) are of type uintxx_t but they actually return value of type intxx_t (the mentioned function internally calls exif_get_sshort) Will this not cause undefined behavior? For the problem I described, I suspect this to be an issue. Any inputs will be much appreciated. Regards Pavan On Fri, Aug 3, 2012 at 12:28 PM, Jan Patera <pa...@pi...> wrote: > Pavan, > > looks like you have a 64bit build? If so, could you please provide me your > JPG file? > libexif has not been tested well on 64 bit platforms yet. > > --- Jan > > > On further debugging, found that I'm getting an invalid tag from the raw > > IFD data. > > I think it is expected to get this tag EXIF_TAG_EXIF_IFD_POINTER (0x8769) > > .. But I'm actually getting (0xFFFFFFFFFFFF8769) which messes up the > whole > > tag extraction and gives an unknown tag which is negative -30871 > > Does anyone have any clue about this problem... > > Strangely, it works fine on my linux machine. > > > > Regards, > > Pavan > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. > > > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ > > libexif-devel mailing list > > lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libexif-devel > > > > > |
From: Translation P. R. <ro...@tr...> - 2012-08-03 07:37:19
|
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...> |
From: Translation P. R. <ro...@tr...> - 2012-08-03 07:37:18
|
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'exif' has been submitted by the Vietnamese team of translators. The file is available at: http://translationproject.org/latest/exif/vi.po (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) All other PO files for your package are available in: http://translationproject.org/latest/exif/ Please consider including all of these in your next release, whether official or a pretest. Whenever you have a new distribution with a new version number ready, containing a newer POT file, please send the URL of that distribution tarball to the address below. The tarball may be just a pretest or a snapshot, it does not even have to compile. It is just used by the translators when they need some extra translation context. The following HTML page has been updated: http://translationproject.org/domain/exif.html If any question arises, please contact the translation coordinator. Thank you for all your work, The Translation Project robot, in the name of your translation coordinator. <coo...@tr...> |
From: Jan P. <pa...@pi...> - 2012-08-03 06:58:44
|
Pavan, looks like you have a 64bit build? If so, could you please provide me your JPG file? libexif has not been tested well on 64 bit platforms yet. --- Jan > On further debugging, found that I'm getting an invalid tag from the raw > IFD data. > I think it is expected to get this tag EXIF_TAG_EXIF_IFD_POINTER (0x8769) > .. But I'm actually getting (0xFFFFFFFFFFFF8769) which messes up the whole > tag extraction and gives an unknown tag which is negative -30871 > Does anyone have any clue about this problem... > Strangely, it works fine on my linux machine. > > Regards, > Pavan > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ > libexif-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libexif-devel > |
From: Pavan K. <pav...@gm...> - 2012-08-03 06:43:50
|
On further debugging, found that I'm getting an invalid tag from the raw IFD data. I think it is expected to get this tag EXIF_TAG_EXIF_IFD_POINTER (0x8769) .. But I'm actually getting (0xFFFFFFFFFFFF8769) which messes up the whole tag extraction and gives an unknown tag which is negative -30871 Does anyone have any clue about this problem... Strangely, it works fine on my linux machine. Regards, Pavan |
From: Pavan K. <pav...@gm...> - 2012-08-02 12:21:54
|
Hi, I have a problem with the metadata of a certain jpeg file. The taken date (original date) is not being obtained from libexif even though I can see it when I view the properties of the file. Moreover when I try to get the exif data of this file on my linux machine (Fedora) it provides the tag EXIF_TAG_DATE_TIME_ORIGINAL and EXIF_TAG_DATE_TIME as expected. And I can extract the date taken correctly. The problem only occurs when I try to get the date taken of this file while running on my MIPS board. Here it does not list any of the below tags in its ExifData. EXIF_TAG_DATE_TIME, EXIF_TAG_DATE_TIME_ORIGINAL, EXIF_TAG_DATE_TIME_DIGITIZED I'm using libexif 0.6.20 Has anyone else faced a similar problem? Can you provide me some hints to debug this problem.. Thanks Pavan |
From: Translation P. R. <ro...@tr...> - 2012-07-29 13:52:11
|
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...> |
From: Translation P. R. <ro...@tr...> - 2012-07-28 16:00:48
|
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.21.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://sourceforge.net/projects/libexif/files/exif/0.6.21/exif-0.6.21.tar.gz 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...> |
From: Translation P. R. <ro...@tr...> - 2012-07-28 15:59:33
|
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.21.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://sourceforge.net/projects/libexif/files/libexif/0.6.21/libexif-0.6.21.tar.gz 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...> |