Menu
▾
▴
libexif-devel — This is the place where your questions about libexif will be answered.
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
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
|
Dec
|
|
From: n179911 <n1...@gm...> - 2014-04-22 05:21:49
|
Hi, Is 160x120 the standard dimension for thumbnail in jpeg? regardless of the actual dimension of the image? Does the thumbnail has a parameter to tell if the thumbnail is in landscape or portrait? Thank you. Sam |
|
From: Dan F. <da...@co...> - 2014-04-20 11:46:16
|
On Sun, Apr 20, 2014 at 12:20:29PM +0200, Mario Blättermann wrote: > Any news about that? Do you need some more info? Unfortunately, I cannot help > out with implementing this, besides to use my scripts. Even if it doesn't work > yet in the build chain, the module on TP could be created to get man pages in > more native languages. This gives translators some extra time to work on this. I've just been too busy to get to the long list of libexif tasks I have on my plate. If someone were to submit patches, it would definitely short-cut the process :^) >>> Dan |
|
From: Mario B. <mar...@gm...> - 2014-04-20 10:20:40
|
Hi all, Am 03.04.2014 10:52, schrieb Mario Blättermann: > Hi Dan, > > Am 03.04.2014 09:02, schrieb Dan Fandrich: >> On Tue, Mar 18, 2014 at 01:36:57PM +0100, Mario Blättermann wrote: >>> both the libexif library and the exif command line tool are translatable >>> at translationproject.org. But we should also internationalize the exif man >>> page and publish the translation template there. >>> >>> Using po4a this is quite easy. Have a look at the attachment. There you'll >>> find two scripts which generate the pot file and translate the po files >>> back to the actual man page, respectively. For testing purposes, I've also >>> added a German translation file. >> >> I've never seen manual pages translated using the .po mechanism like this. > > Most of the (active) external translation projects like man-pages-de or > man-pages-fr already use po4a. Moreover, the Debian folks uses it for almost all > the dpkg and apt man pages. > >> It makes good sense as the translation workflow is unaltered. >> > > The translation workflow...? I assume you mean the workflow on translators side. > That's unaltered. Translators get a pot template from the TP robot, translate > the messages and send it back. That's the greatest advantage of po4a: Nobody has > to bother with plain text, which would include to figure out a way to track > upstream changes accordingly. In other words, I wouldn't start on a translation > without po files. > >>> We need some glue code to install the files accordingly, but I don't know >>> anything about how the Autotools work, sorry. The translated files itself >>> are already in the correct paths when using the scripts ($PREFIX/man still >>> has to be preceded). >>> >>> In general, the generation of the translated man pages should happen before >>> the release tarball will be created. That way packagers don't have to >>> bother with po4a, especially if a po4a package is missing from certain >>> distributions. Shouldn't be a problem, the man pages are arch-independent >>> anyway. >>> >>> Besides that, the localized versions could be presented at the website, >>> too. The English one is already present. >> >> I'll take a look at what it would take to integrate this. Thanks for >> bringing it to our attention. >> > Thanks for your interest. > Any news about that? Do you need some more info? Unfortunately, I cannot help out with implementing this, besides to use my scripts. Even if it doesn't work yet in the build chain, the module on TP could be created to get man pages in more native languages. This gives translators some extra time to work on this. Best Regards, Mario |
|
From: n179911 <n1...@gm...> - 2014-04-17 22:44:31
|
How does libexif works with libjpeg to insert exif data in jpeg file? I think libjpeg creates JPEG header and JPEG image data. I think EXIF data is after JPEG header and before JPEG image data. To create a jpeg image with EXIF header, do I need to 0. allocate a new buffer big enough for JPEG header + EXIF header + JPEG image data 1. memcpy the JPEG header created by libjpeg 2. memcpy the EXIF header created by libexif 3. memcpy the JPEG image date created by libjpeg Thank you. |
|
From: Mario B. <mar...@gm...> - 2014-04-03 08:52:35
|
Hi Dan, Am 03.04.2014 09:02, schrieb Dan Fandrich: > On Tue, Mar 18, 2014 at 01:36:57PM +0100, Mario Blättermann wrote: >> both the libexif library and the exif command line tool are translatable >> at translationproject.org. But we should also internationalize the exif man >> page and publish the translation template there. >> >> Using po4a this is quite easy. Have a look at the attachment. There you'll >> find two scripts which generate the pot file and translate the po files >> back to the actual man page, respectively. For testing purposes, I've also >> added a German translation file. > > I've never seen manual pages translated using the .po mechanism like this. Most of the (active) external translation projects like man-pages-de or man-pages-fr already use po4a. Moreover, the Debian folks uses it for almost all the dpkg and apt man pages. > It makes good sense as the translation workflow is unaltered. > The translation workflow...? I assume you mean the workflow on translators side. That's unaltered. Translators get a pot template from the TP robot, translate the messages and send it back. That's the greatest advantage of po4a: Nobody has to bother with plain text, which would include to figure out a way to track upstream changes accordingly. In other words, I wouldn't start on a translation without po files. >> We need some glue code to install the files accordingly, but I don't know >> anything about how the Autotools work, sorry. The translated files itself >> are already in the correct paths when using the scripts ($PREFIX/man still >> has to be preceded). >> >> In general, the generation of the translated man pages should happen before >> the release tarball will be created. That way packagers don't have to >> bother with po4a, especially if a po4a package is missing from certain >> distributions. Shouldn't be a problem, the man pages are arch-independent >> anyway. >> >> Besides that, the localized versions could be presented at the website, >> too. The English one is already present. > > I'll take a look at what it would take to integrate this. Thanks for > bringing it to our attention. > Thanks for your interest. Best Regards, Mario |
|
From: Mario B. <mar...@gm...> - 2014-03-18 12:37:12
|
Hi, both the libexif library and the exif command line tool are translatable at translationproject.org. But we should also internationalize the exif man page and publish the translation template there. Using po4a this is quite easy. Have a look at the attachment. There you'll find two scripts which generate the pot file and translate the po files back to the actual man page, respectively. For testing purposes, I've also added a German translation file. We need some glue code to install the files accordingly, but I don't know anything about how the Autotools work, sorry. The translated files itself are already in the correct paths when using the scripts ($PREFIX/man still has to be preceded). In general, the generation of the translated man pages should happen before the release tarball will be created. That way packagers don't have to bother with po4a, especially if a po4a package is missing from certain distributions. Shouldn't be a problem, the man pages are arch-independent anyway. Besides that, the localized versions could be presented at the website, too. The English one is already present. Best Regards, Mario |
|
From: Translation P. R. <ro...@tr...> - 2014-01-18 10:18:01
|
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 Japanese team of translators. The file is available at:
http://translationproject.org/latest/exif/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/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...> - 2013-12-25 16:32: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 Spanish team of translators. The file is available at:
http://translationproject.org/latest/libexif/es.po
(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive. Ask at the address below if you want this.)
All other PO files for your package are available in:
http://translationproject.org/latest/libexif/
Please consider including all of these in your next release, whether
official or a pretest.
Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below. The tarball may be just a pretest or a
snapshot, it does not even have to compile. It is just used by the
translators when they need some extra translation context.
The following HTML page has been updated:
http://translationproject.org/domain/libexif.html
If any question arises, please contact the translation coordinator.
Thank you for all your work,
The Translation Project robot, in the
name of your translation coordinator.
<coo...@tr...>
|
|
From: Translation P. R. <ro...@tr...> - 2013-12-22 07:42: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 Spanish team of translators. The file is available at:
http://translationproject.org/latest/libexif/es.po
(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive. Ask at the address below if you want this.)
All other PO files for your package are available in:
http://translationproject.org/latest/libexif/
Please consider including all of these in your next release, whether
official or a pretest.
Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below. The tarball may be just a pretest or a
snapshot, it does not even have to compile. It is just used by the
translators when they need some extra translation context.
The following HTML page has been updated:
http://translationproject.org/domain/libexif.html
If any question arises, please contact the translation coordinator.
Thank you for all your work,
The Translation Project robot, in the
name of your translation coordinator.
<coo...@tr...>
|
|
From: Translation P. R. <ro...@tr...> - 2013-12-21 23:42: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 Spanish team of translators. The file is available at:
http://translationproject.org/latest/libexif/es.po
(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive. Ask at the address below if you want this.)
All other PO files for your package are available in:
http://translationproject.org/latest/libexif/
Please consider including all of these in your next release, whether
official or a pretest.
Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below. The tarball may be just a pretest or a
snapshot, it does not even have to compile. It is just used by the
translators when they need some extra translation context.
The following HTML page has been updated:
http://translationproject.org/domain/libexif.html
If any question arises, please contact the translation coordinator.
Thank you for all your work,
The Translation Project robot, in the
name of your translation coordinator.
<coo...@tr...>
|
|
From: Translation P. R. <ro...@tr...> - 2013-12-21 09:42: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 Spanish team of translators. The file is available at:
http://translationproject.org/latest/libexif/es.po
(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive. Ask at the address below if you want this.)
All other PO files for your package are available in:
http://translationproject.org/latest/libexif/
Please consider including all of these in your next release, whether
official or a pretest.
Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below. The tarball may be just a pretest or a
snapshot, it does not even have to compile. It is just used by the
translators when they need some extra translation context.
The following HTML page has been updated:
http://translationproject.org/domain/libexif.html
If any question arises, please contact the translation coordinator.
Thank you for all your work,
The Translation Project robot, in the
name of your translation coordinator.
<coo...@tr...>
|
|
From: Translation P. R. <ro...@tr...> - 2013-12-15 17:07: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 Spanish team of translators. The file is available at:
http://translationproject.org/latest/libexif/es.po
(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive. Ask at the address below if you want this.)
All other PO files for your package are available in:
http://translationproject.org/latest/libexif/
Please consider including all of these in your next release, whether
official or a pretest.
Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below. The tarball may be just a pretest or a
snapshot, it does not even have to compile. It is just used by the
translators when they need some extra translation context.
The following HTML page has been updated:
http://translationproject.org/domain/libexif.html
If any question arises, please contact the translation coordinator.
Thank you for all your work,
The Translation Project robot, in the
name of your translation coordinator.
<coo...@tr...>
|
|
From: Translation P. R. <ro...@tr...> - 2013-12-15 11:17: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 Spanish team of translators. The file is available at:
http://translationproject.org/latest/libexif/es.po
(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive. Ask at the address below if you want this.)
All other PO files for your package are available in:
http://translationproject.org/latest/libexif/
Please consider including all of these in your next release, whether
official or a pretest.
Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below. The tarball may be just a pretest or a
snapshot, it does not even have to compile. It is just used by the
translators when they need some extra translation context.
The following HTML page has been updated:
http://translationproject.org/domain/libexif.html
If any question arises, please contact the translation coordinator.
Thank you for all your work,
The Translation Project robot, in the
name of your translation coordinator.
<coo...@tr...>
|
|
From: Translation P. R. <ro...@tr...> - 2013-12-15 07:52: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 Spanish team of translators. The file is available at:
http://translationproject.org/latest/libexif/es.po
(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive. Ask at the address below if you want this.)
All other PO files for your package are available in:
http://translationproject.org/latest/libexif/
Please consider including all of these in your next release, whether
official or a pretest.
Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below. The tarball may be just a pretest or a
snapshot, it does not even have to compile. It is just used by the
translators when they need some extra translation context.
The following HTML page has been updated:
http://translationproject.org/domain/libexif.html
If any question arises, please contact the translation coordinator.
Thank you for all your work,
The Translation Project robot, in the
name of your translation coordinator.
<coo...@tr...>
|
|
From: Translation P. R. <ro...@tr...> - 2013-11-24 17:57: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 Spanish team of translators. The file is available at:
http://translationproject.org/latest/exif/es.po
(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive. Ask at the address below if you want this.)
All other PO files for your package are available in:
http://translationproject.org/latest/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...> - 2013-11-23 17:12:10
|
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 Spanish team of translators. The file is available at:
http://translationproject.org/latest/exif/es.po
(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive. Ask at the address below if you want this.)
All other PO files for your package are available in:
http://translationproject.org/latest/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...> - 2013-11-23 17:02:12
|
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 Spanish team of translators. The file is available at:
http://translationproject.org/latest/exif/es.po
(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive. Ask at the address below if you want this.)
All other PO files for your package are available in:
http://translationproject.org/latest/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-09-09 12:18:57
|
On Mon, Sep 09, 2013 at 10:59:13AM +0200, Mathieu Malaterre wrote: > Just FYI, MakerNote for Milestone Medical is pretty easy: > > $ wget http://gipedia.org/gupedia/images/f/f7/Paprccnew.jpg > $ exif -d Paprccnew.jpg > [...] > ExifData: Loading entry 0x927c ('MakerNote')... > ExifData: MakerNote found (4d 61 63 72 6f 50 41...). > > This is simply an ASCII string with content "MacroPATH 4.0.10" But, does this MakerNote format support other content? It could be that this particular file contains no ancillary data, but others could. I'd rather put in special code to handle such MakerNotes specially without some assurance that there aren't now, or could be in the future, some files with more data in such tags. >>> Dan |
|
From: Dan F. <da...@co...> - 2013-09-09 12:13:56
|
On Mon, Sep 09, 2013 at 10:38:30AM +0200, Mathieu Malaterre wrote: > I am getting the following report: > > ExifData: Unknown tag 0xa401 (entry 14 in '0'). Please report this tag > to <lib...@li...>. > ExifData: Unknown tag 0xa402 (entry 15 in '0'). Please report this tag > to <lib...@li...>. > ExifData: Unknown tag 0xa403 (entry 16 in '0'). Please report this tag > to <lib...@li...>. > ExifData: Unknown tag 0xa404 (entry 17 in '0'). Please report this tag > to <lib...@li...>. > ExifData: Unknown tag 0xa406 (entry 18 in '0'). Please report this tag > to <lib...@li...>. > ExifData: Unknown tag 0xa40c (entry 19 in '0'). Please report this tag > to <lib...@li...>. These tags are not allowed to exist in IFD 0, only the EXIF IFD. That means that technically, the file is corrupt. > However this particular JPG contains private data. How can I remove > the jpg file, and only share the exif data ? You can do that easily enough using libexif, but the exif command-line tool doesn't expose that functionality. You can of course just run "exif file.jpg" and "exif --show-mnote file.jpg" to display the EXIF tags in text format, but if you want the raw EXIF data without writing any code to get it, you'll have to use another program. >>> Dan |
|
From: Mathieu M. <ma...@de...> - 2013-09-09 08:59:40
|
Just FYI, MakerNote for Milestone Medical is pretty easy: $ wget http://gipedia.org/gupedia/images/f/f7/Paprccnew.jpg $ exif -d Paprccnew.jpg [...] ExifData: Loading entry 0x927c ('MakerNote')... ExifData: MakerNote found (4d 61 63 72 6f 50 41...). This is simply an ASCII string with content "MacroPATH 4.0.10" 2cts -M |
|
From: Mathieu M. <ma...@de...> - 2013-09-09 08:38:58
|
Dear all, I am getting the following report: ExifData: Unknown tag 0xa401 (entry 14 in '0'). Please report this tag to <lib...@li...>. ExifData: Unknown tag 0xa402 (entry 15 in '0'). Please report this tag to <lib...@li...>. ExifData: Unknown tag 0xa403 (entry 16 in '0'). Please report this tag to <lib...@li...>. ExifData: Unknown tag 0xa404 (entry 17 in '0'). Please report this tag to <lib...@li...>. ExifData: Unknown tag 0xa406 (entry 18 in '0'). Please report this tag to <lib...@li...>. ExifData: Unknown tag 0xa40c (entry 19 in '0'). Please report this tag to <lib...@li...>. However this particular JPG contains private data. How can I remove the jpg file, and only share the exif data ? Using (debian/sid): $ exif -v 0.6.21 Thanks, |
|
From: Translation P. R. <ro...@tr...> - 2013-07-09 19:32: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 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...> - 2013-07-09 11:47: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 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: Dan F. <da...@co...> - 2013-04-16 21:58:35
|
On Tue, Apr 16, 2013 at 11:27:38PM +0200, Casper wrote: > I'm happy to inform you that libexif-gtk has been pushed in > Rawhide (devel branch of Fedora) and F19 repositories. As for > exif, I'll forward to this ML bugzilla tickets reported by fedora > users. That's good to hear! We'd be happy to hear of any reported problems. >>> Dan |
|
From: Casper <fa...@fe...> - 2013-04-16 21:27:49
|
Dear Devs, I'm happy to inform you that libexif-gtk has been pushed in Rawhide (devel branch of Fedora) and F19 repositories. As for exif, I'll forward to this ML bugzilla tickets reported by fedora users. Regards, Matthieu -- Pour encrypter vos emails Clef GPG ID : 83288189 @ hkp://pgp.mit.edu:11371 Empreinte : CC26 692F 5205 AC8F 7912 7783 D7A7 F4C5 8328 8189 |
258 messages has been excluded from this view by a project administrator.
