[ 
https://issues.apache.org/jira/browse/IMAGING-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16252548#comment-16252548
 ] 

Bruno P. Kinoshita commented on IMAGING-205:
--------------------------------------------

No confusion at all. I've started to learn the code base and get myself used to 
the library recently. If I recall correctly, the development on Sanselan 
stopped, and it was since then moved to Apache Commons Imaging.

Not sure what are the requirements for Commons Imaging to be available for 
Android. Perhaps building the current sources into a jar would work?

There are a few blockers for a 1.0 release. But we could still try to release 
alpha/beta versions before that. In case having the JAR in a Maven repository 
is a requirement for you, and an -alpha or -beta works for you too. Even easier 
if you could use a -SNAPSHOT version.

> Imaging (Apache Sanselan) produces "odd offsets" in (EXIF) metadata
> -------------------------------------------------------------------
>
>                 Key: IMAGING-205
>                 URL: https://issues.apache.org/jira/browse/IMAGING-205
>             Project: Commons Imaging
>          Issue Type: Bug
>          Components: imaging.*
>            Reporter: Joakim Knudsen
>            Assignee: Bruno P. Kinoshita
>            Priority: Critical
>         Attachments: 20171030_21481_COPY.jpg, 
> Gaboxjellyfish-changedexifmetadata.jpg, Gaboxjellyfish.jpg, after.html, 
> before.html
>
>
> I'm using the "last stable version" of Apache Sanselan 0.97 in an Android 
> project (app). I have not upgraded to Commons Imaging yet, since the website 
> says there is no stable release yet. Meanwhile, there are bugs in Sanselan. 
> If I run the [sample code method 
> WriteExifMetadataExample.changeExifMetadata|http://svn.apache.org/repos/asf/commons/proper/sanselan/trunk/src/test/java/org/apache/sanselan/sampleUsage/WriteExifMetadataExample.java?p=820841]
>  on an image, which updates the Apterture and GPS tags, the resulting image 
> fails to validate (through Phil Harvey's [ExifTool 
> software|https://sno.phy.queensu.ca/~phil/exiftool/]):
> {noformat}
> > exiftool.exe -validate -error -warning -a "..\20171030_21481_COPY.jpg"
> Validate                        : 19 Warnings (17 minor)
> Warning                         : [minor] Odd offset for IFD0 tag 0x010f
> Warning                         : [minor] Odd offset for IFD0 tag 0x011a
> Warning                         : [minor] Odd offset for IFD0 tag 0x011b
> Warning                         : [minor] Odd offset for IFD0 tag 0x0131
> Warning                         : [minor] Odd offset for IFD0 tag 0x0132
> Warning                         : [minor] Odd offset for ExifIFD tag 0x829a
> Warning                         : [minor] Odd offset for ExifIFD tag 0x829d
> Warning                         : [minor] Odd offset for ExifIFD tag 0x9003
> Warning                         : [minor] Odd offset for ExifIFD tag 0x9004
> Warning                         : [minor] Odd offset for ExifIFD tag 0x9202
> Warning                         : [minor] Odd offset for ExifIFD tag 0x9205
> Warning                         : [minor] Odd offset for ExifIFD tag 0x920a
> Warning                         : [minor] Odd offset for ExifIFD tag 0x9286
> Warning                         : Non-standard count (1) for GPS tag 0x0001 
> GPSLatitudeRef
> Warning                         : [minor] Odd offset for GPS tag 0x0002
> Warning                         : Non-standard count (1) for GPS tag 0x0003 
> GPSLongitudeRef
> Warning                         : [minor] Odd offset for GPS tag 0x0004
> Warning                         : [minor] Odd offset for IFD1 tag 0x011a
> Warning                         : [minor] Odd offset for IFD1 tag 0x011b
> {noformat}
> I need some advice on how to proceed here. Since Sanselan does not appear to 
> do what it should (even on very basic metadata editing), am I correct to 
> assume that the current version of Commons Imaging does a better job? :-)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to