https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104030
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Either we drop the UCN support altogether, or make -Wbidi-chars a 2 level warning, -Wbidi-chars mapping to -Wbidi-chars=1 which doesn't warn about UCNs and -Wbidi-chars=2 that does. UCNs indeed don't have the problem that a user in an editor sees something different than what it actually is (unless some editor interprets UCNs and shows them as unicode chars), but one reason to warn about UCNs was to make sure that even what the program prints doesn't suffer from such problems. Of course, if something like libreoffice (I bet) carefully ensures it is paired, but constructs it from smaller separate literals, then it is fine.
