You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Michael Beckerle (JIRA)" <ji...@apache.org> on 2018/10/23 13:14:00 UTC

[jira] [Commented] (DAFFODIL-894) utf16Width property - unpaired surrogate behavior

    [ https://issues.apache.org/jira/browse/DAFFODIL-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660630#comment-16660630 ] 

Michael Beckerle commented on DAFFODIL-894:
-------------------------------------------

Current sentiment in the DFDL Workgroup is to make utf16Width='variable' optional functionality, because it's not really feasible to implement in the JVM/Java world. In that case this would be a feature we would consciously choose not to implement in Daffodil, at least as it is working today (JVM-language, etc.)

> utf16Width property - unpaired surrogate behavior
> -------------------------------------------------
>
>                 Key: DAFFODIL-894
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-894
>             Project: Daffodil
>          Issue Type: Wish
>          Components: Back End
>    Affects Versions: s11
>            Reporter: Michael Beckerle
>            Priority: Major
>
> Part of DFDL-893 but worth carving off as a lower-priority aspect.
> This was a comment on the original January 2011 version 1.0.3 spec of DFDL.
> The Sept 2013 1.0.4 spec says: 
> When utf16Width is 'variable', then on parsing an un-paired surrogate codepoint causes a decode error, which can be controlled via dfdl:encodingErrorPolicy. 
> Is this the actual behavior, i.e., does ICU let us even do this? (If not then this will be an issue with the DFDL spec.)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)