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: Dan F. <da...@co...> - 2010-12-16 08:20:59
|
This release adds more flexibility to the existing exif options and fixes a crash when given bad command-line input. A few libexif bugs are squashed and rational values are now shown with appropriate precision. New translations are added for the bs, ro, & tr locales. libexif-0.6.20 (2010-12-15): * New translations: bs, tr * Updated translations: be, cs, da, de, en_GB, en_CA, it, ja, nl, pl, pt_BR, pt, ru, sk, sq, sr, sv, vi, zh_CN * Fixed some problems in the write-exif.c example program * Stop listing -lm as a required library for dynamic linking in libexif.pc * Turned on the --enable-silent-rules configure option * Changed a lot of strings to make the case of the text more consistent * exif_entry_dump() now displays the correct tag name for GPS tags * Fixed some invalid format specifiers that caused problems on some platforms * Display rational numbers with the right number of significant figures exif-0.6.20 (2010-12-15): * New translation: ro * Updated translations: it, lv, sk * --no-fixup now honoured during --create-exif to not create default tags * Fixed crash when not enough components were given to --set-value * Made --set-value more forgiving of whitespace * Allow --set-value on UNDEFINED tags (treating them as byte arrays) * Honour --machine-readable with --show-mnote and --show-description * Turned on the --enable-silent-rules configure option * Adding or removing a thumbnail can be done simultaneously with other options * Allow --create-exif to be used in place of an input file Here are the SHA1 sums of the released files: b12777ad6327389764570e42afdae66384421cd3 exif-0.6.20.tar.bz2 b90e9eaa9db59018fee70c2b021bb5edca1eb64a exif-0.6.20.tar.gz d7cce9098169269695852db20d24350c2d3c10fe libexif-0.6.20.tar.bz2 562d02737872e3c33eefcb75a5a9260a90466731 libexif-0.6.20.tar.gz 87376eb8b69ee5678af72570e02362d021c2488a libexif-0.6.20.zip >>> Dan |
From: Dan F. <da...@co...> - 2010-12-01 22:22:45
|
It's been a year since the last libexif release, so it's a good time to do another. There haven't been a lot of big changes to the library, but the exif front-end has had a number of improvements. I'll plan to make a release on December 15 if no-one has any objections. >>> Dan |
From: Translation P. R. <ro...@tr...> - 2010-10-27 21:32:13
|
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: Translation P. R. <ro...@tr...> - 2010-10-11 10:02:13
|
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 Icelandic team of translators. The file is available at: http://translationproject.org/latest/exif/is.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: Translation P. R. <ro...@tr...> - 2010-10-02 23:47:23
|
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 Galician team of translators. The file is available at: http://translationproject.org/latest/exif/gl.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: Translation P. R. <ro...@tr...> - 2010-06-01 10:47: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 Italian team of translators. The file is available at: http://translationproject.org/latest/libexif/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/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...> - 2010-04-30 21:57:10
|
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: Dan F. <da...@co...> - 2010-04-16 23:37:54
|
On Sat, Apr 17, 2010 at 01:29:46AM +0200, Leonardo Parisi wrote: > thank for the answer.. I try to see write-exif.c and the files of the exif command-line.. but for now they don't help me so much.. > I try explain my project/problem... I have to process a lot of images, and these images have already the exif information... > I use the libjpeg to open and decompress these images and put it in a memory unsigned char* buffer... now after manipulate these images I > need to save the new image in another file whit the exif information of the original file.. for write this new jpeg I use yet the libjpeg. > I not able to merge libexif and libjpeg to work together to save the new file. Look at action_save() in exif/actions.c >>> Dan -- http://www.MoveAnnouncer.com The web change of address service Let webmasters know that your web site has moved |
From: Leonardo P. <leo...@gm...> - 2010-04-16 23:30:05
|
thank for the answer.. I try to see write-exif.c and the files of the exif command-line.. but for now they don't help me so much.. I try explain my project/problem... I have to process a lot of images, and these images have already the exif information... I use the libjpeg to open and decompress these images and put it in a memory unsigned char* buffer... now after manipulate these images I need to save the new image in another file whit the exif information of the original file.. for write this new jpeg I use yet the libjpeg. I not able to merge libexif and libjpeg to work together to save the new file. On Apr 16, 2010, at 10:16 PM, Dan Fandrich wrote: > On Fri, Apr 16, 2010 at 04:05:36PM +0200, Leonardo Parisi wrote: >> I have a exif data, how I can write on a existing jpeg? > > The sample program contrib/examples/write-exif.c shows a simple example of > how to write to an existing JPEG image that doesn't already contain EXIF > tags. But a more general approach would use the libjpeg library that's > included in the exif command-line front-end tar ball. Unfortunately, > that's not well documented, but the exif main.c is pretty simple and > readable and will show all you need to know about how to do it. > >>>> Dan > -- > http://www.MoveAnnouncer.com The web change of address service > Let webmasters know that your web site has moved > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > libexif-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libexif-devel |
From: Dan F. <da...@co...> - 2010-04-16 20:16:57
|
On Fri, Apr 16, 2010 at 04:05:36PM +0200, Leonardo Parisi wrote: > I have a exif data, how I can write on a existing jpeg? The sample program contrib/examples/write-exif.c shows a simple example of how to write to an existing JPEG image that doesn't already contain EXIF tags. But a more general approach would use the libjpeg library that's included in the exif command-line front-end tar ball. Unfortunately, that's not well documented, but the exif main.c is pretty simple and readable and will show all you need to know about how to do it. >>> Dan -- http://www.MoveAnnouncer.com The web change of address service Let webmasters know that your web site has moved |
From: Leonardo P. <leo...@gm...> - 2010-04-16 14:05:45
|
I have a exif data, how I can write on a existing jpeg? tnx a lot |
From: Translation P. R. <ro...@tr...> - 2010-03-25 10:32: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 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...> |
From: Translation P. R. <ro...@tr...> - 2010-03-24 17:52:15
|
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: Translation P. R. <ro...@tr...> - 2010-03-09 22:12:18
|
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: Translation P. R. <ro...@tr...> - 2010-02-17 02:52:14
|
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...> |
From: Translation P. R. <ro...@tr...> - 2010-02-11 13:22:46
|
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 Latvian team of translators. The file is available at: http://translationproject.org/latest/exif/lv.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: Translation P. R. <ro...@tr...> - 2010-02-09 22:27:18
|
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: Translation P. R. <ro...@tr...> - 2010-02-09 09:32:13
|
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...> - 2010-02-08 16:32:18
|
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: Translation P. R. <ro...@tr...> - 2010-02-06 10:32: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 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...> - 2010-02-06 09:50:42
|
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.20-pre1.pot Whenever you have a new distribution with a new version number ready, containing a newer POT file, please send the URL of that distribution tarball to the address below. The tarball may be just a pretest or a snapshot, it does not even have to compile. It is just used by the translators when they need some extra translation context. Below is the URL which has been provided to the translators of your package. Please inform the translation coordinator, at the address at the bottom, if this information is not current: http://downloads.sourceforge.net/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...> |
From: Marcus M. <ma...@je...> - 2010-02-03 07:30:30
|
On Tue, Feb 02, 2010 at 10:01:27PM -0800, Dan Fandrich wrote: > On Sun, Jan 31, 2010 at 04:07:21PM +0100, Marcus Meissner wrote: > > On Thu, Jan 28, 2010 at 09:07:53PM -0800, Dan Fandrich wrote: > > > I'm going to make these more consistent. > > Sounds good to me. > > After looking at the sheer number of strings that would have to change, > I think I'll switch styles to having the "value" strings starting with > an initial capital letter. My main complaint was the lack of consistency > which this will still fix. With libexif now translated into 21 languages, > it will save a lot of work for translators since more value strings already > have this format. My example set would then look like this: > > Resolution Unit |Inch > YCbCr Positioning |Centered > Exposure Program |Normal program > Orientation |Top - left > Metering Mode |Center-weighted average > Quality |Basic > Unknown Tag |0 > FlashPixVersion |Unknown FlashPix version > > which still looks pretty good. As translator I have to agree :) It also looks a bit better in that display ;) Ciao, Marcus |
From: Dan F. <da...@co...> - 2010-02-03 06:01:44
|
On Sun, Jan 31, 2010 at 04:07:21PM +0100, Marcus Meissner wrote: > On Thu, Jan 28, 2010 at 09:07:53PM -0800, Dan Fandrich wrote: > > I'm going to make these more consistent. > Sounds good to me. After looking at the sheer number of strings that would have to change, I think I'll switch styles to having the "value" strings starting with an initial capital letter. My main complaint was the lack of consistency which this will still fix. With libexif now translated into 21 languages, it will save a lot of work for translators since more value strings already have this format. My example set would then look like this: Resolution Unit |Inch YCbCr Positioning |Centered Exposure Program |Normal program Orientation |Top - left Metering Mode |Center-weighted average Quality |Basic Unknown Tag |0 FlashPixVersion |Unknown FlashPix version which still looks pretty good. >>> Dan -- http://www.MoveAnnouncer.com The web change of address service Let webmasters know that your web site has moved |
From: Marcus M. <ma...@je...> - 2010-01-31 15:07:35
|
On Thu, Jan 28, 2010 at 09:07:53PM -0800, Dan Fandrich wrote: > libexif is pretty inconsistent about whether it returns strings in > upper case, lower case or mixed case. For example: > > Resolution Unit |Inch > YCbCr Positioning |centerd centered? > Exposure Program |Normal program > Orientation |top - left > Metering Mode |Center-Weighted Average > Quality |BASIC > Unknown tag |0 > FlashPixVersion |Unknown FlashPix Version > > This not only looks funny, but makes the job of translators more difficult; > forty strings appear up to three times each, differing only in case and > spacing. > > I'm going to make these more consistent. If I don't hear any objections, > I'm going to make the names/titles (the part before the |) mixed upper > and lower case like an actual title (as most of them above are), and > the values (after the |) all lower case, except when certain words or > abbreviations have to be capitalized. The examples above would then > look like this: > > Resolution Unit |inch > YCbCr Positioning |centerd > Exposure Program |normal program > Orientation |top - left > Metering Mode |center-weighted average > Quality |basic > Unknown Tag |0 > FlashPixVersion |unknown FlashPix version > > This is going to mean translators are going to have to fix lots of > translations in the short term, but the output will be nicer in > the long term. I'll send the new .pot file to the translators right away > to give them lots of time to update translations before the next release. Sounds good to me. Ciao, Marcus |
From: Dan F. <da...@co...> - 2010-01-29 05:08:09
|
libexif is pretty inconsistent about whether it returns strings in upper case, lower case or mixed case. For example: Resolution Unit |Inch YCbCr Positioning |centerd Exposure Program |Normal program Orientation |top - left Metering Mode |Center-Weighted Average Quality |BASIC Unknown tag |0 FlashPixVersion |Unknown FlashPix Version This not only looks funny, but makes the job of translators more difficult; forty strings appear up to three times each, differing only in case and spacing. I'm going to make these more consistent. If I don't hear any objections, I'm going to make the names/titles (the part before the |) mixed upper and lower case like an actual title (as most of them above are), and the values (after the |) all lower case, except when certain words or abbreviations have to be capitalized. The examples above would then look like this: Resolution Unit |inch YCbCr Positioning |centerd Exposure Program |normal program Orientation |top - left Metering Mode |center-weighted average Quality |basic Unknown Tag |0 FlashPixVersion |unknown FlashPix version This is going to mean translators are going to have to fix lots of translations in the short term, but the output will be nicer in the long term. I'll send the new .pot file to the translators right away to give them lots of time to update translations before the next release. >>> Dan |