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

Literal (non-entity) whitespace should not be acceptable within certain properties

XMLWordPrintableJSON

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • s12
    • None
    • Front End
    • None

      According to Mike:

      There are other properties though, where they are not lists of whitespace
      separated values, it's just one value. Example: escapeBlockStart. This
      could be something like '[BEGIN]', or XML's famous '<![CDATA[' . If it
      wanted to have whitespace between the brackets and the word you can't do
      '[ BEGIN ]' according to the rules. You have to do '[%SP;BEGIN%SP;]'. I
      believe if you write '[ BEGIN ]' it should SDE because an individual
      string literal has non-entity whitespaces.

      I created a test that represents this and it parses with no error.

      See test whitespace_01 in the following files:

      daffodil-test/src/test/resources/daffodil/section06/entities/Entities.tdml
      daffodil-test/src/test/scala-debug/daffodil/section06/entities/TestEntities_01.scala
      daffodil-test/src/test/scala/daffodil/section06/entities/TestEntities.scala

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

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - Not Specified
                  Not Specified
                  Logged:
                  Time Spent - 3 minutes
                  3m