[
https://issues.apache.org/jira/browse/DAFFODIL-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497429#comment-17497429
]
Alexander Revello commented on DAFFODIL-2663:
---------------------------------------------
Before I go too far down the path I wanted to get a little more clarification
on the goal of this. The way I interpreted this is that anyone who wants to
plug in an unofficially supported charset will need to create their own charset
in charsets directory of daffodil-io. This functionality already exists but it
is not particularly straightforward to do so I created a class that can be
extended and requires everything someone would need to plug in a charset
> charset encoders need to be pluggable
> -------------------------------------
>
> Key: DAFFODIL-2663
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2663
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 3.2.1
> Reporter: Mike Beckerle
> Assignee: Alexander Revello
> Priority: Major
> Labels: beginner
>
> We've seen an ongoing need for more and distinct charset encoders/decoders
> for new encodings.
> They need to be pluggable components, not something that requires creating a
> new release of Daffodil for.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
