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

Debugger data dumps must use the format-specified encoding, not just utf-8

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Reopened
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: deferred
    • Component/s: Back End, CLI, Debugger, Usability
    • Labels:
      None

      Description

      Our debugger trace output currently outputs data in text and hex, but assumes utf-8 for the text.

      This needs to be improved to use the currently-specified encoding, and to handle decode errors.

      E.g., suppose you have !!crud!! where crud is not c.r.u.d, but some bytes that won't properly decode as characters. This wants to present in the debugger as

      !!????!!

      where ? is the unicode replacement character.

      I believe newlines and other "moving whitespace" like tabs should also be replaced by a substitution character that says what they are. (Box character with a codepoint written inside it)

        Gliffy Diagrams

          Attachments

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              mbeckerle.dfdl Mike Beckerle
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:

                  Tasks

                  Progress: 
                   0/0