[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-task-tracker] [task #12153] Incorporate Octave-Forge core functi
|
From: |
Carnë Draug |
|
Subject: |
[Octave-task-tracker] [task #12153] Incorporate Octave-Forge core functions into Octave |
|
Date: |
Sat, 04 May 2013 18:20:07 +0000 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20100101 Firefox/10.0.12 Iceweasel/10.0.12 |
Follow-up Comment #8, task #12153 (project octave):
Should we bother wth exifread? Matlab has deprecated it. They suggest to use
imfinfo and I looked into it, but matlab's imfinfo only reads a very small
part of the EXIF data, in no way comparable to what exifread/readexif does.
I have 3 suggestions for this:
1 - make imfinfo read only the same EXIF fields has matlab;
2 - make imfinfo return all the EXIF fields that exifread/readexif at the root
of the structure returned;
3 - make iminfo return the same as matlab with only one extra field, named
EXIF which itself is another structure with all the other EXIF fields.
What do you guys think is best?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/task/?12153>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/