Comment 10 for bug 1783475

@Mark This won't prevent applications from parsing octal numbers in strings, it's just where you're wanting to include a non-ASCII character in a string field, something like this:

  field(FVST, "F\374nf") # "Fünf" using the ISO-8859-1 char-set

which would have to be spelled like this instead:

  field(FVST, "F\xFCnf")

@Dirk The JSON5 spec is a small subset of the ECMAScript 5.1 language spec, so they're just following what that standard said. Actually the epicsStrnRawFromEscaped() routine will still accept a single hex digit, but the dbLoadRecords() lexer will complain if it doesn't see two.