[
https://issues.apache.org/jira/browse/IMAGING-168?focusedWorklogId=286721&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-286721
]
ASF GitHub Bot logged work on IMAGING-168:
------------------------------------------
Author: ASF GitHub Bot
Created on: 01/Aug/19 13:46
Start Date: 01/Aug/19 13:46
Worklog Time Spent: 10m
Work Description: ecki commented on issue #18: IMAGING-168 installing
package with Swedish characters adds junk char…
URL: https://github.com/apache/commons-imaging/pull/18#issuecomment-517295170
BTW I think Latin1 is one of the 8bit transparent encodings, so the old code
would never be unequal. This is one of the reasons why Latin1 is used if a
encoding is not well defined. I do not understand iptc enough here to say if it
is good or bad to use a different encoding, but it might need to be
configurable...
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 286721)
Time Spent: 1h 10m (was: 1h)
> 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
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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.14#76016)
