document #230
Block escape scheme issue
| Status: | closed | Start date: | 09/16/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | Steve Hanson | % Done: | 100% |
|
| Category: | - | |||
| Target version: | - | |||
| Document Type: | Proposed Recommendation |
Description
Andy has spotted a scenario where what is written does not get parsed in the same way and a character is lost. Only occurs when there is an escape escape character as the last character and it is different from the first character of the escape block end.
History
Updated by Steve Hanson about 8 years ago
- Status changed from submitted to accepted
- % Done changed from 0 to 50
WG agreed that what is happening is that the data being presented to the unparser is not compliant with the escape scheme, and the unparser should issue a processing error. Erratum to be raised.
Updated by Steve Hanson almost 8 years ago
Erratum 5.1 in DFDL Experience Document 4.
Updated by Michael Beckerle over 5 years ago
- Status changed from accepted to closed
- % Done changed from 50 to 100
(Other formats not available in this archive.