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/08/15 19:49:00 UTC

[jira] [Commented] (DAFFODIL-1584) Verify unparser specified length padding behavior - whether minLength is used.

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

Michael Beckerle commented on DAFFODIL-1584:
--------------------------------------------

See dfdl-wg@ogf.org email thread with titles containing "need clarification on unparsing with textPadKind='padChar'"


> Verify unparser specified length padding behavior - whether minLength is used.
> ------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-1584
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1584
>             Project: Daffodil
>          Issue Type: New Feature
>          Components: Back End
>            Reporter: Michael Beckerle
>            Priority: Major
>             Fix For: deferred
>
>
> Tests like unparseDelimitedPaddedString09 and unparseDelimitedPaddedString09
> (note: poorly named because these tests aren't about delimited anything, or the delimters are beside the point)
> These tests have been updated to expect the length to be the maximum of the length property value (literal or evaluated expression), and the minLength facet, for strings, and dfdl:textOutputMinLength for other simple types.
> However, this is under discussion by the DFDL workgroup, so may change.
> Erratum 5.18 is the one that is subject to clarification of this behavior.



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