Uploaded image for project: 'Daffodil'
  1. Daffodil
  2. DFDL-1395

PUA hex values always mapped back to illegal XML chars, even if input was PUA value

XMLWordPrintableJSON

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • deferred
    • 2.0.0
    • API, Unparsing
    • None

      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

              Unassigned Unassigned
              jchab Jessie Chab
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: