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

Re: [Libexif-devel] Polish translations and some NLS fixes for libexif and co.

[Lutz <lu...@us...>]

On Mon, 2005-08-15 at 21:48 +0200, Jakub Bogusz wrote:
> http://qboosh.cs.net.pl/pl.po/libexif-0.6.12.pl.po
> http://qboosh.cs.net.pl/pl.po/libexif-gtk-0.3.5.pl.po
> http://qboosh.cs.net.pl/pl.po/exif-0.6.9.pl.po
> http://qboosh.cs.net.pl/pl.po/gexif-0.5.pl.po

Committed to CVS.

> http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/exif-nls.patch?rev=3D1.=
1

Committed to CVS.

> - gexif uses wrong domain name when setting its codeset.
>   Patch available at:
> http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/gexif-codeset.patch?rev=
=3D1.1

Already in CVS.

> http://qboosh.cs.net.pl/pl.po/libexif-nls.patch

Committed to CVS.

Thanks for your work!
--=20
Lutz M=FCller <lu...@us...>

[Libexif-devel] Polish translations and some NLS fixes for libexif and co.

[Jakub B. <qb...@pl...>]

Hello,

First, I made Polish translations for libexif and related packages -
they can be downloaded from:

http://qboosh.cs.net.pl/pl.po/libexif-0.6.12.pl.po
http://qboosh.cs.net.pl/pl.po/libexif-gtk-0.3.5.pl.po
http://qboosh.cs.net.pl/pl.po/exif-0.6.9.pl.po
http://qboosh.cs.net.pl/pl.po/gexif-0.5.pl.po

(to be placed as po/pl.po in individual packages)

When testing them, I found some NLS-related problems in exif and gexif:

- exif tries to convert messages to UTF-8 using hardcoded ISO-8859-1
  instead of real encoding used for given locale.
  Also gettext domain is not set correctly in configure.
  Patch available at:
http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/exif-nls.patch?rev=1.1

- gexif uses wrong domain name when setting its codeset.
  Patch available at:
http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES/gexif-codeset.patch?rev=1.1


And finally, should libexif debug messages be translated or not?
Now some of them are translated, some not.
I've prepared a patch which adds gettext() calls to the remaining ones.
It also fixes some typos etc. in strings used as msgids.
It's available at:
http://qboosh.cs.net.pl/pl.po/libexif-nls.patch


-- 
Jakub Bogusz    http://qboosh.cs.net.pl/

[Libexif-devel] how to get the thumbnail resolution?

[Sergey 'J. B. <ji...@de...>]

Hi,

is there any way to get the exif thumbnail resolution in pixels?

I could probably use some other library to analyze the thumbnail data,
but that would be an overkill. Also, I could not find a function
in libjpeg that would read data from a buffer instead of a file; and saving
the thumbnail in order to get the resolution is also quite inefficient...
so having this functionality in libexif would be really very nice :>

so is there anything in libexif that I could use, and if not - any chance to
get this functionality in the future? :)

Kind regards,
Jin

Re: [Libexif-devel] Parsing TIFF

[Hubert F. <hfi...@te...>]

Lutz M=FCller wrote:
> On Mon, 2005-07-25 at 11:04 -0400, Hubert Figuiere wrote:
>=20
>>>exif_data_save_data should return just the TIFF structure then?
>>
>>Yep. That's what it does now.
>=20
>=20
> Then please increment CURRENT. And we need documentation on that.

Sure.
But does that break the APIs ? I prefer to not break them and rather=20
extend them.

> It was
> pretty easy to just save the EXIF data and pass it on to jpeglib. Pleas=
e
> describe somewhere what to prepend to the EXIF data. There is some
> documentation in exif-data.h, perhaps you can just add a couple of note=
s
> there. And update libexif/NEWS, too. I guess exif needs an update, too.

One just need to add the Exif ID defined as:
ExifHeader[] =3D {0x45, 0x78, 0x69, 0x66, 0x00, 0x00};
I don't know why 6 and not 5 chars, but that is the way it is.

> I have been asked by a company to release a new version. Can you alread=
y
> tell me when CVS will be ready for packaging?


I haven't committed anything yet. So CVS is in workable state.

Hub

Re: [Libexif-devel] Parsing TIFF

[Lutz <lu...@us...>]

On Mon, 2005-07-25 at 11:04 -0400, Hubert Figuiere wrote:
> > exif_data_save_data should return just the TIFF structure then?
> Yep. That's what it does now.

Then please increment CURRENT. And we need documentation on that. It was
pretty easy to just save the EXIF data and pass it on to jpeglib. Please
describe somewhere what to prepend to the EXIF data. There is some
documentation in exif-data.h, perhaps you can just add a couple of notes
there. And update libexif/NEWS, too. I guess exif needs an update, too.

I have been asked by a company to release a new version. Can you already
tell me when CVS will be ready for packaging?

Regards
--=20
Lutz M=FCller <lu...@us...>

Re: [Libexif-devel] Parsing TIFF

[Hubert F. <hfi...@te...>]

Jan Patera wrote:
> Hi,
> 
> I've also started investigating the possibility of parsing TIFFs.
> I've come up with more or less 3 solutions, one of them is yours.
> None of them is really perfect.
> However, I see one big possible drawback.
> With this approach, entire TIFF file is treated as EXIF. This means that
> entire (possibly multipage) TIFF file is read into memory by
> exif_loader_copy(). This can easily be dozens of megabytes.


Yep. But it is quite easy to work around given the EXIF spec. We know 
where to get the data.

That is what I have to fix before having things working....

Hub

Re: [Libexif-devel] Parsing TIFF

[Hubert F. <hfi...@te...>]

Lutz Müller wrote:
> On Sun, 2005-07-24 at 22:42 -0400, Hubert Figuiere wrote:
> 
>>Basically the change is to not copy over the 'Exif\0' marker (6 bytes), 
>>because it is part of JFIF, not part of the Exif data. Exif data is just 
>>TIFF structure, so everything else comes along...
> 
> 
> exif_data_save_data should return just the TIFF structure then?
> 

Yep. That's what it does now.


Hub

Re: [Libexif-devel] Parsing TIFF

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

Hi,

I've also started investigating the possibility of parsing TIFFs.
I've come up with more or less 3 solutions, one of them is yours.
None of them is really perfect.
However, I see one big possible drawback.
With this approach, entire TIFF file is treated as EXIF. This means that
entire (possibly multipage) TIFF file is read into memory by
exif_loader_copy(). This can easily be dozens of megabytes.

 -- Jan

> I'm have almost EXIF parsing from TIFF files working from current
> libexif CVS.
> Basically the change is to not copy over the 'Exif\0' marker (6 bytes),
> because it is part of JFIF, not part of the Exif data. Exif data is just
>  TIFF structure, so everything else comes along....
>
> Currently it sort of crashes with TIFF and CR2, but otherwise it works
> with JPEG, at least with the current test suite.
>
> Any comments ?
>
> Hub

Re: [Libexif-devel] Parsing TIFF

[Lutz <lu...@us...>]

On Sun, 2005-07-24 at 22:42 -0400, Hubert Figuiere wrote:
> Basically the change is to not copy over the 'Exif\0' marker (6 bytes),=
=20
> because it is part of JFIF, not part of the Exif data. Exif data is jus=
t=20
> TIFF structure, so everything else comes along...

exif_data_save_data should return just the TIFF structure then?

Regards
--=20
Lutz M=FCller <lu...@us...>

[Libexif-devel] Parsing TIFF

[Hubert F. <hfi...@te...>]

Hi,


I'm have almost EXIF parsing from TIFF files working from current 
libexif CVS.
Basically the change is to not copy over the 'Exif\0' marker (6 bytes), 
because it is part of JFIF, not part of the Exif data. Exif data is just 
TIFF structure, so everything else comes along....

Currently it sort of crashes with TIFF and CR2, but otherwise it works 
with JPEG, at least with the current test suite.

Any comments ?

Hub

Re: [Libexif-devel] [newbie] Write Exif Data to a jpg file

[Lutz <lu...@us...>]

On Wed, 2005-07-13 at 15:06 +0200, Fabien Poupineau wrote:
> I read this file, but I still don't understand how do you assign the
> values to the tags: if I want to set the GPSLongitudeRef to east, what
> do I have to do ?=20

There is no interface for that. You need to access the ExifEntry->data
directly, i.e.

e =3D exif_entry_new ();
exif_content_add_entry (c, e);
e->tag =3D EXIF_TAG_GPS_...;
e->format =3D EXIF_FORMAT_SHORT;
e->components =3D 1;
e->size =3D ...;
e->data =3D malloc (...):
exif_set_short (e->data, byte_order, ...);

Or similar (I don't know what format the individual tags have -> EXIF
specification).

Regards
--=20
Lutz M=FCller <lu...@us...>

Re: [Libexif-devel] [newbie] Write Exif Data to a jpg file

[Fabien P. <fp...@ma...>]

Lutz M=FCller a =E9crit :

>On Tue, 2005-07-12 at 12:27 +0200, Fabien Poupineau wrote:
> =20
>
>>I'm currently working on an application that needs to write Exif data=20
>>(GPS) into a jpeg file.
>>Actually, I have a tiffRepresentation (the image data) and I want to ad=
d=20
>>GPS info into this data, in order to save the whole in a jpg file.
>>I want to use libexif, but I can't understand the API, and the=20
>>documentation is a bit poor... :)
>>   =20
>>
>
>Agreed. Perhaps the code in libexif/test/test-mem.c can help you to
>understand the syntax.
> =20
>
I read this file, but I still don't understand how do you assign the=20
values to the tags: if I want to set the GPSLongitudeRef to east, what=20
do I have to do ?
I think I get how you save the exif data with the jpg data, but it lacks=20
me the setting of the tags...

Hoping for your answer,
Thanks.

Re: [Libexif-devel] [newbie] Write Exif Data to a jpg file

[Fabien P. <fp...@ma...>]

Lutz M=FCller a =E9crit :

>On Tue, 2005-07-12 at 12:27 +0200, Fabien Poupineau wrote:
> =20
>
>>I'm currently working on an application that needs to write Exif data=20
>>(GPS) into a jpeg file.
>>Actually, I have a tiffRepresentation (the image data) and I want to ad=
d=20
>>GPS info into this data, in order to save the whole in a jpg file.
>>I want to use libexif, but I can't understand the API, and the=20
>>documentation is a bit poor... :)
>>   =20
>>
>
>Agreed. Perhaps the code in libexif/test/test-mem.c can help you to
>understand the syntax.
>
> =20
>
I take a look now...

>Does the image already have EXIF data?
> =20
>
Actually no, I get the GPS info from another source and I have to put=20
then into an image without any EXIF info.

Regards.

Re: [Libexif-devel] [newbie] Write Exif Data to a jpg file

[Lutz <lu...@us...>]

On Tue, 2005-07-12 at 12:27 +0200, Fabien Poupineau wrote:
> I'm currently working on an application that needs to write Exif data=20
> (GPS) into a jpeg file.
> Actually, I have a tiffRepresentation (the image data) and I want to ad=
d=20
> GPS info into this data, in order to save the whole in a jpg file.
> I want to use libexif, but I can't understand the API, and the=20
> documentation is a bit poor... :)

Agreed. Perhaps the code in libexif/test/test-mem.c can help you to
understand the syntax.

Does the image already have EXIF data?

Regards
--=20
Lutz M=FCller <lu...@us...>

[Libexif-devel] [newbie] Write Exif Data to a jpg file

[Fabien P. <fp...@wa...>]

Hello,
I'm currently working on an application that needs to write Exif data 
(GPS) into a jpeg file.
Actually, I have a tiffRepresentation (the image data) and I want to add 
GPS info into this data, in order to save the whole in a jpg file.
I want to use libexif, but I can't understand the API, and the 
documentation is a bit poor... :)
I'm using libexif on Mac OS X, with a Cocoa (Objective-C) application, 
and libexif was compiled successfully yet.
Many thanks for any link or pointer you might give me ;)

fp12

Re: [Libexif-devel] libexif for raw images

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

Hi guys,

TIFF structure is simple. In fact, libEXIF already contains TIFF
parsers. EXIF is built on top of TIFF.
The TIFF consists of an 8-byte TIFF header (already parsed in
exif_data_load_data and Cannon mnote), several IFDs, and image data.
I am volunteering to extend libEXIF to parse EXIF embedded in TIFF.
However, because leaving for holiday, I can do it after July the 10th.

 == Jan

>  Udi Fuchs twisted the bytes to say:
>
>  Udi> I'm also no expert in the TIFF structure, but looking at dcraw.c
> and Udi> specifically at the function parse_tiff() it looks pretty
> simple. I Udi> think that it is the sample as JPEG after you remove the
> first 12 Udi> bytes from the JPEG header.
>
> As trivial/difficult as JPEG. At least the canon version. It embeds a
> EXIF record inside the tiff, two several jpegs and the raw data. You can
> check the code I wrote to scan this files in gqview
> (src/format_canon.c). It is fairly simple and straightforward (100-200
> lines of code). gqview is in C, though. It is nicely documented by Adobe
> (TIFF V 6.0).
>
>
>
>  Udi> Udi
>
>  Udi> On 6/30/05, Lutz M=FCller <lu...@us...> wrote:
>  >> On Wed, 2005-06-29 at 22:46 -0400, Hubert Figuiere wrote:
>  >> > Like reinventing the wheel ?
>  >> =20
>  >> Again, I don't know how complex the TIFF structure is. JPEG is
> trivial. =20
>  >> Regards
>  >> --

Re: [Libexif-devel] libexif for raw images

[Daniel M. G. <dmg...@uv...>]

 Udi Fuchs twisted the bytes to say:

 Udi> I'm also no expert in the TIFF structure, but looking at dcraw.c and
 Udi> specifically at the function parse_tiff() it looks pretty simple. I
 Udi> think that it is the sample as JPEG after you remove the first 12
 Udi> bytes from the JPEG header.

As trivial/difficult as JPEG. At least the canon version. It embeds a
EXIF record inside the tiff, two several jpegs and the raw data. You
can check the code I wrote to scan this files in gqview
(src/format_canon.c). It is fairly simple and straightforward (100-200
lines of code). gqview is in C, though. It is nicely documented by
Adobe (TIFF V 6.0).



 Udi> Udi

 Udi> On 6/30/05, Lutz M=FCller <lu...@us...> wrote:
 >> On Wed, 2005-06-29 at 22:46 -0400, Hubert Figuiere wrote:
 >> > Like reinventing the wheel ?
 >> =20
 >> Again, I don't know how complex the TIFF structure is. JPEG is trivial.
 >> =20
 >> Regards
 >> --
 >> Lutz M=FCller <lu...@us...>
 >> =20
 >> =20
 >> =20
 >> -------------------------------------------------------
 >> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
 >> from IBM. Find simple to follow Roadmaps, straightforward articles,
 >> informative Webcasts and more! Get everything you need to get up to
 >> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
 >> _______________________________________________
 >> Libexif-devel mailing list
 >> Lib...@li...
 >> https://lists.sourceforge.net/lists/listinfo/libexif-devel
 >> 


 Udi> -------------------------------------------------------
 Udi> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
 Udi> from IBM. Find simple to follow Roadmaps, straightforward articles,
 Udi> informative Webcasts and more! Get everything you need to get up to
 Udi> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
 Udi> _______________________________________________
 Udi> Libexif-devel mailing list
 Udi> Lib...@li...
 Udi> https://lists.sourceforge.net/lists/listinfo/libexif-devel

--
Daniel M. German                  "Do not confuse luck with skill.
                                   "
                                   The Replacement Killers"
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

 

Re: [Libexif-devel] libexif for raw images

[Udi F. <udi...@gm...>]

I'm also no expert in the TIFF structure, but looking at dcraw.c and
specifically at the function parse_tiff() it looks pretty simple. I
think that it is the sample as JPEG after you remove the first 12
bytes from the JPEG header.

Udi

On 6/30/05, Lutz M=FCller <lu...@us...> wrote:
> On Wed, 2005-06-29 at 22:46 -0400, Hubert Figuiere wrote:
> > Like reinventing the wheel ?
>=20
> Again, I don't know how complex the TIFF structure is. JPEG is trivial.
>=20
> Regards
> --
> Lutz M=FCller <lu...@us...>
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> _______________________________________________
> Libexif-devel mailing list
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libexif-devel
>

Re: [Libexif-devel] libexif for raw images

[Lutz <lu...@us...>]

On Wed, 2005-06-29 at 22:46 -0400, Hubert Figuiere wrote:
> Like reinventing the wheel ?

Again, I don't know how complex the TIFF structure is. JPEG is trivial.

Regards
--=20
Lutz M=FCller <lu...@us...>

Re: [Libexif-devel] Code cleanup

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

Hi Joerg,

I've found two possible problems:

1)  Could you please beautify it a little bit? I mean all colons
immediately after the text or separated with one space
> +  {1,N_("Macro mode")},
> +  {4,N_(" / Flash mode : ")},
> +  {5,N_(" / Continuous drive mode : ")},
> +  {7,N_(" / Focus mode : ")},
> +  {10,N_(" / Image size : ")},
> +  {11,N_(" / Easy shooting mode : ")},
> +  {13,N_(" / Contrast : ")},
> +  {14,N_(" / Saturation : ")},
> +  {15,N_(" / Sharpness : ")},
> +  {16,N_(" / ISO : ")},
> +  {17,N_(" / Metering mode : ")},
> +  {19,N_(" / AF point selected: ")},
> +  {20,N_(" / Exposure mode: ")},
> +  {32,N_(" / Focus mode2: ")},

2) Looks like the middle line shouldn't be there?
> +  {16,18,N_("200")},
> +  {16,19,N_("300")},
> +  {16,19,N_("400")},

Beside these I see no problems.

 --- Jan

>
> I've done a little code cleanup in libexif/canon/mnote-canon-entry.c,
> which saves us another 180 lines. I don't want to check it in without a
> short review; so can you please do a short look-through and point me to
> problematic places?
>
> Joerg

[Libexif-devel] Code cleanup

[Joerg H. <jo...@de...>]

Hi

I've done a little code cleanup in libexif/canon/mnote-canon-entry.c, which
saves us another 180 lines. I don't want to check it in without a short
review; so can you please do a short look-through and point me to
problematic places?

Joerg

-- 
Was denen einen ihr Watergate, ist den anderen ihr Firstgate.
- Thomas Bliessner, <slr...@me...>

Re: [Libexif-devel] libexif for raw images

[Hubert F. <hfi...@te...>]

Lutz M=FCller wrote:
> On Tue, 2005-06-28 at 02:23 -0400, Hubert Figuiere wrote:
>=20
>>What is the issue about depending on LibTIFF ?
>=20
>=20
> It could be that we just don't need it. We don't need jpeglib in order
> to parse JPEGs. Navigation to the start of the EXIF data is trivial.
> This could be the same for TIFF files. I don't know, though.

All you need is to fetch the tag from the TIFF. You can still do the=20
minimum... All you need is to walk thru the TIFF structures.

Like reinventing the wheel ?

Hub

Re: [Libexif-devel] libexif for raw images

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

> What is the issue about depending on LibTIFF ? Since you want to parse
> TIFF, it is probably you best solution, as the other program is likely
> to depend on it too.
>
> I think that LibTIFF is a decent dependency.

No, no. Please don't introduce hard-coded dependency on libTIFF.
There are tools using libEXIF and not libTIFF which is quite huge.

 -- Jan

Re: [Libexif-devel] libexif for raw images

[Lutz <lu...@us...>]

On Tue, 2005-06-28 at 02:23 -0400, Hubert Figuiere wrote:
> What is the issue about depending on LibTIFF ?

It could be that we just don't need it. We don't need jpeglib in order
to parse JPEGs. Navigation to the start of the EXIF data is trivial.
This could be the same for TIFF files. I don't know, though.
--=20
Lutz M=FCller <lu...@us...>

Re: [Libexif-devel] libexif for raw images

[Hubert F. <hfi...@te...>]

Lutz M=FCller wrote:
> On Fri, 2005-06-17 at 12:02 +0200, Udi Fuchs wrote:
>=20
>>The patch is already Incorporated in UFRaw's CVS. I'm attaching
>>ufraw_exif.c, so you won't need to check out ufraw from the cvs.
>=20
>=20
> I'd like to move that code into libexif. However, I'd like to avoid a
> dependency on libtiff. Do you know the TIFF file format? How do I
> navigate through the start of the file
>=20
> 4D 4D 00 2A 00 00 00 08 00 18 00 FE 00 04 00 00 00 01 00 00 00 01 00 ..=
.
>=20

What is the issue about depending on LibTIFF ? Since you want to parse=20
TIFF, it is probably you best solution, as the other program is likely=20
to depend on it too.

I think that LibTIFF is a decent dependency.

Hub