Does it make sense to add support for defining these in schema? The charsets I am adding are pretty speicific; and, questions of public disclosure aside, do not really seem to fit in the global codebase. We can get away with doing this since we happen to be Daffodil Devs, so there is a low barrier to entry for us inserting new encodings. However, if I were just a Daffodil user I would be at a loss for dealing with this usecase.
________________________________ From: Beckerle, Mike <[email protected]> Sent: Monday, May 20, 2019 12:57:41 PM To: [email protected] Subject: Re: Adding character encoding? The encodings are in daffodil-io, and for these small charsets it's very very easy to support them. There is already a 6 bit charset for DFI 264 DUI 001, and also some 5-bit encodings. All this was motivated by Link16. Take a look at file X_DFDL_6_BIT_DFI_264_DUI_001.scala ________________________________ From: Sloane, Brandon <[email protected]> Sent: Monday, May 20, 2019 11:43:40 AM To: [email protected] Subject: Adding character encoding? In working on schema for mil-std-6016, I have discovered a 6 bit character encoding that is distinct from the X-DFDL-US-ASCII-6-BIT-PACKED encoding we already support. What would the process for supporting this be? Brandon T. Sloane Associate, Services [email protected] | tresys.com
