[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Error UTF-8 strings
From: |
Akim Demaille |
Subject: |
Re: Error UTF-8 strings |
Date: |
Sun, 21 Jun 2020 11:45:47 +0200 |
Hi Hans,
> Le 21 juin 2020 à 10:19, Hans Åberg <haberg-1@telia.com> a écrit :
>
>
>> On 21 Jun 2020, at 07:59, Akim Demaille <akim@lrde.epita.fr> wrote:
>> Could you please give more details? How can I reproduce that?
>
> Use
> %token <name> "<string>"
> where <string> has non-ASCII characters (high bit set), and trigger it in a
> syntax error, as the failing token or one of the expected ones.
That's not a bug report.
I need details. What skeleton? What options for parse.error? What locale are
you using?
If you want some support, give us something we can actually work on.
Give me something reproducible. I'll disregard anything else.
Cheers!
- Error UTF-8 strings, Hans Åberg, 2020/06/20
- Re: Error UTF-8 strings, Akim Demaille, 2020/06/21
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/21
- Re: Error UTF-8 strings,
Akim Demaille <=
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/21
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/21
- Re: Error UTF-8 strings, Akim Demaille, 2020/06/22
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/22
- Re: Error UTF-8 strings, Akim Demaille, 2020/06/23
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/23
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/23
- Re: Error UTF-8 strings, Akim Demaille, 2020/06/24
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/24
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/23