search

google-code-export / thebigpicture

Automatically exported from code.google.com/p/thebigpicture
1 stars 1 forks source link

IPTC data types are a bit vague #17

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Because of a lack of specification, the IPTC data types are not very
precisely defined and numbered. A better definition should be found.

Original issue reported on code.google.com by p.edel...@gmail.com on 18 Mar 2007 at 9:18

GoogleCodeExporter commented 9 years ago 
A possible bug can arise in iptc.py, class IPTCRecord. It checks specifically 
for
number 15 as a data type, while this isn't prescribed anywhere.

Original comment by p.edel...@gmail.com on 19 Mar 2007 at 7:24

GoogleCodeExporter commented 9 years ago 
According to the specification, there is no proper data type, or numbering for 
that
matter. Rather, the spec defines how many octets can or should be used. So 
maybe we
should use a simple enumeration for that.

There are some different types of recurring data though:
- 8, 16 and 32 bit integers.
- Ascii data
- Dates, specified as a string of numbers (CCYYMMDD)
- Times, specified as a string HHMMSS±HHMM

Original comment by p.edel...@gmail.com on 19 Mar 2007 at 11:26

GoogleCodeExporter commented 9 years ago 
This should be fixed in the second alpha version.

Original comment by p.edel...@gmail.com on 1 Apr 2007 at 10:38

GoogleCodeExporter commented 9 years ago 
v1-alpha2 is an intermediate release. This issue is shifted to v1-alpha3.

Original comment by p.edel...@gmail.com on 10 Apr 2007 at 9:12