public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sbergman at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/104030] [12 Regression] -Wbidi-chars should not warn about UCNs
Date: Fri, 14 Jan 2022 15:41:32 +0000 [thread overview]
Message-ID: <bug-104030-4-jThbO5F0PG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104030-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104030
--- Comment #7 from Stephan Bergmann <sbergman at redhat dot com> ---
(In reply to Jakub Jelinek from comment #2)
> Of course, if something like libreoffice (I bet) carefully ensures it is
> paired, but constructs it from smaller separate literals, then it is fine.
(Or doesn't even need to ensure that e.g. a LRO is paired with a PDF, as my
understanding of <https://www.unicode.org/reports/tr9/tr9-44.html> "Unicode
Bidirectional Algorithm" is that such an LRO doesn't require a matching PDF, in
which case its effect extends to the end of the paragraph, which appears to be
what the example LibreOffice code in comment 0 makes use of.)
next prev parent reply other threads:[~2022-01-14 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 14:51 [Bug preprocessor/104030] New: " sbergman at redhat dot com
2022-01-14 14:55 ` [Bug preprocessor/104030] [12 Regression] " mpolacek at gcc dot gnu.org
2022-01-14 14:59 ` jakub at gcc dot gnu.org
2022-01-14 15:00 ` jakub at gcc dot gnu.org
2022-01-14 15:05 ` mpolacek at gcc dot gnu.org
2022-01-14 15:07 ` mpolacek at gcc dot gnu.org
2022-01-14 15:30 ` jakub at gcc dot gnu.org
2022-01-14 15:41 ` sbergman at redhat dot com [this message]
2022-01-18 13:52 ` rguenth at gcc dot gnu.org
2022-01-24 22:49 ` cvs-commit at gcc dot gnu.org
2022-01-24 22:50 ` mpolacek 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-104030-4-jThbO5F0PG@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: link
Be 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).