[
https://issues.apache.org/jira/browse/IMAGING-168?focusedWorklogId=286724&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-286724
]
ASF GitHub Bot logged work on IMAGING-168:
------------------------------------------
Author: ASF GitHub Bot
Created on: 01/Aug/19 13:53
Start Date: 01/Aug/19 13:53
Worklog Time Spent: 10m
Work Description: janArb commented on issue #18: IMAGING-168 installing
package with Swedish characters adds junk char…
URL: https://github.com/apache/commons-imaging/pull/18#issuecomment-517297269
@ecki It was not configurable before and latin is still the fallback if no
encoding is defined. Why should this bugfix here solve more features? I think
an encoding configuration should be treated as feature.
PS: It definitely is good to support UTF8 if that is defined in the official
IPTC encoding tag (https://de.wikipedia.org/wiki/IPTC-IIM-Standard -> Coded
Character Set)
----------------------------------------------------------------
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: 286724)
Time Spent: 1h 40m (was: 1.5h)
> 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 40m
> 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)
