[
https://issues.apache.org/jira/browse/DAFFODIL-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Beckerle closed DAFFODIL-1395.
-----------------------------------
Resolution: Won't Fix
Working as designed.
A feature to turn off the behavior might be useful, but will wait for a need.
(I.e., is this working per requirements? )
> PUA hex values always mapped back to illegal XML chars, even if input was PUA
> value
> -----------------------------------------------------------------------------------
>
> Key: DAFFODIL-1395
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1395
> Project: Daffodil
> Issue Type: Bug
> Components: API, Unparsing
> Affects Versions: 2.0.0
> Reporter: Jessie Chab
> Priority: Minor
>
> See DFDL-1369 for context. We currently map any illegal XML char to a value
> in the PUA (Private Use Area) on parse, then map it back to the illegal char
> on unparse. However, if you attempt to unparse an actual PUA value, Daffodill
> incorrectly maps it back to an illegal character.
> See tests:
> test_puaInfosetChars_03
> test_puaInfosetChars_04
> in the following files:
> daffodil-test/src/test/resources/edu/illinois/ncsa/daffodil/section00/general/testUnparserGeneral.tdml
> daffodil-test/src/test/scala-debug/edu/illinois/ncsa/daffodil/section00/general/TestUnparserGeneralDebug.scala
> daffodil-test/src/test/scala/edu/illinois/ncsa/daffodil/section00/general/TestUnparserGeneral.scala
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
