[
https://issues.apache.org/jira/browse/IMAGING-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869328#comment-16869328
]
Bruno P. Kinoshita commented on IMAGING-168:
--------------------------------------------
Hi [~janArbeit]
Just had a look at the pull request, and it was not merged due to pending
issues in the current code. Once addressed, I would be keen to review, merge,
and include in the next release.
The reason for this hiatus, was probably that others got busy with other
projects. I was busy trying my best to get a 1.0 release as soon as possible...
but it took much longer than I expected due to issues in the code, discussion
in the dev-mailing-list about what needed to change, then the need to address
the feedback from the mailing list, and finally we had 2 CVE's that blocked the
1.0 release.
Now that we have 1.0-alpha1, the next release should be much easier to get out.
But sorry for the delay.
Let me know if you would be interested in working on this issue and perhaps
reviewing that PR or submitting a new one. I am currently overseas in the
antipodes, with not much time to work on OSS and a bit of jet-lag. So I
probably won't be active writing code for the project until mid-July, but happy
to review PR's and reply e-mail/Jira.
Bruno
> IPTC parser should use CodedCharacterSet tag to determine encoding of the
> IPTC tag values
> -----------------------------------------------------------------------------------------
>
> Key: IMAGING-168
> URL: https://issues.apache.org/jira/browse/IMAGING-168
> Project: Commons Imaging
> Issue Type: Bug
> Components: Format: JPEG
> Reporter: sudeep khemka
> Priority: Major
> Fix For: Review Patch
>
> Attachments: codedCharacterSet.patch
>
>
> The IPTC CodedCharacterSet tag can be used to specify the encoding of the
> IPTC tag values. But the setting is currently ignored.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
