[Bug 1940283] Re: Misleading Error: Invalid character '"'

[Andrew Johnson via Core-talk <core-talk at aps.anl.gov>]

The dbLex.l parser doesn't try to understand UTF-8 and will accept any
characters from \x80-\xff in the string for the second parameter of a
field() or info() entry. If you want us to keep that behavior you should
generate a PR adding tests for that capability, with comments in the
test giving the reasoning for them.

What happens to a string after it has been saved by dbPutString() or
dbPutInfo() may be more challenging though. If a field is a JSON link
it's parsed during iocInit() by the yajl parser, and that probably does
require the string to be valid UTF-8. Similarly the QSRV code which
parses info tags named "Q:group" uses the yajl parser. I think your
update to the dbpf command calls the yajl parser so value strings there
may have to be UTF-8, etc.

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1940283

Title:
  Misleading Error: Invalid character '"'

Status in EPICS Base:
  New

Bug description:
  When using a tab character in a field, EPICS 7 prints a misleading
  error message, not hinting at the tab but at the closing(?) quote.

  Example 1:  field(DESC,  "a	b")
  Example 2:  info(TAB,  "a	b")

  Error: Invalid character '"'
   at or before """ in path "."  file "..." line ...

  
  BTW: Is there a reason why I cannot use a tab in my (info) fields?

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1940283/+subscriptions