Assuming your lengthKind is delimited and comma is your delimiter, Daffodil sees the first inner quote (i.e. the quote before $b2) as the end of the escape block and will expect a following comma. Since it won't find a comma it will create a parse error.

Ideally your inner quotes would be escaped with a character specified by the escapeEscapeCharacter property. For example:

  <dfdl:escapeScheme
    dfdl:escapeKind="escapeBlock"
    dfdl:escapeBlockStart="&quot;"
    dfdl:escapeBlockEnd="&quot;"
    dfdl:escapeEscapeCharacter="\"
    ...
    />

Then your data would look like this:

  "Warning ...: string \"$b2\" may slow down scanning",

In this case, the infoset will contain the string with the outer quotes and back slashes removed but the inner quotes included. E.g.

  <field>Warning ...: string "$b2" may slow down scanning</field>

- Steve


On 2023-04-05 03:37 PM, Hardesty, Mark C (US) wrote:
Ex.   ,"Warning in rule [xxxxxxx] in xxxx rules file [xxxxx.xxx]: string "$b2" may slow down scanning",


Reply via email to