[
https://issues.apache.org/jira/browse/DAFFODIL-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18012360#comment-18012360
]
Mike Beckerle commented on DAFFODIL-2894:
-----------------------------------------
To my knowledge, there are only plugin charsets for 8-bit and less-than-8-bit
charsets.
More elaborate charsets need an API, but more elaborate charsets can be added
to Daffodil by way of a code contribution.
But these small 8 or less than 8 bit charset plugins we see today could be
described with a small XML or JSON file and code could just read them, and the
corresponding internal charset objects created. I.e., there is no object-class
code-type API required for these.
I suggest we deprecate charset extension via "API" (which is really just using
the internal charset classes in Daffodil along with a service loader) and just
provide a way to read a file containing a description of a plug-in charset.
> Stabalize and document pluggable charset API
> --------------------------------------------
>
> Key: DAFFODIL-2894
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2894
> Project: Daffodil
> Issue Type: Bug
> Components: API
> Reporter: Steve Lawrence
> Priority: Major
> Fix For: 4.0.0
>
>
> Daffodil supports the ability to have pluggable character sets. This is
> supported, but the API is not really documented and is not part of the
> "public" api. There aren't many known external charsets, but it's possible
> that might change. Like we did with Layers, we may want to take another look
> at our character set API and see if it is sufficient move it from an
> experimental API to a more public stable API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
