> On 24 Mar 2018, at 22:10, Paul Eggert wrote:
>
> Hans Åberg wrote:
>> Might it possible to get an option
>
> Sounds like a reasonable option to me, if someone wants to write and document
> it.
I wrote some C++ code translating it back to UTF-8 for error messages, but it
is sort of roundabo
Hans Åberg wrote:
Might it possible to get an option
Sounds like a reasonable option to me, if someone wants to write and document
it.
Might it possible to get an option, for use with UTF-8, where the yytname table
entries are not translated into C escape strings? - Currently, if one writes say
%token mapsto_key "↦"
it is written as "\"\\342\\206\\246\"" rather than "↦".