[
https://issues.apache.org/jira/browse/DAFFODIL-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869517#comment-16869517
]
Michael Beckerle commented on DAFFODIL-1584:
--------------------------------------------
When there is a length expression, it is evaluated and used as the length to
which padding is inserted when unparsing. Erratum 5.18 specifies this.
The minLength facet is not to be used as it is for other length kinds. When
lengthKind is explicit and expression, minLength is used only for validation.
> 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
> Assignee: Michael Beckerle
> Priority: Major
> Fix For: 2.4.0
>
>
> 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)
