public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "leo at sai dot msu.ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/99210] New: X editing for reading file with encoding='utf-8' Date: Mon, 22 Feb 2021 22:40:24 +0000 [thread overview] Message-ID: <bug-99210-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99210 Bug ID: 99210 Summary: X editing for reading file with encoding='utf-8' Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libfortran Assignee: unassigned at gcc dot gnu.org Reporter: leo at sai dot msu.ru Target Milestone: --- Created attachment 50237 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50237&action=edit Example bug 1x editing for utf-8 encoding file nX edit must skip n characters. For files encoding='utf-8', skip n ISO/IEC 10646 characters. But now, nX edit is skipping n bytes. And may cause "Fortran runtime error: Invalid UTF-8 encoding" for valid UTF-8 files.
next reply other threads:[~2021-02-22 22:40 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-22 22:40 leo at sai dot msu.ru [this message] 2021-02-22 22:44 ` [Bug libfortran/99210] " leo at sai dot msu.ru 2021-02-23 1:34 ` jvdelisle at gcc dot gnu.org 2021-02-28 3:25 ` jvdelisle at gcc dot gnu.org 2021-04-17 3:26 ` jvdelisle at gcc dot gnu.org 2021-05-04 2:29 ` jvdelisle at gcc dot gnu.org 2024-02-13 5:00 ` jvdelisle at gcc dot gnu.org 2024-02-13 20:07 ` jvdelisle at gcc dot gnu.org 2024-02-13 22:56 ` jvdelisle at gcc dot gnu.org 2024-02-14 15:58 ` cvs-commit at gcc dot gnu.org 2024-02-14 20:00 ` jvdelisle at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-99210-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).