From: Eli Zaretskii <eliz@gnu.org>
To: <Paul.Koning@dell.com>
Cc: simark@simark.ca, zjz@zjz.name, gdb-patches@sourceware.org
Subject: Re: support C/C++ identifiers named with non-ASCII characters
Date: Mon, 21 May 2018 16:16:00 -0000 [thread overview]
Message-ID: <834lj1f0ne.fsf@gnu.org> (raw)
In-Reply-To: <CF83AA8F-D3F8-446C-A078-252ADFB6D4C8@dell.com> (Paul.Koning@dell.com)
> From: <Paul.Koning@dell.com>
> CC: <zjz@zjz.name>, <gdb-patches@sourceware.org>
> Date: Mon, 21 May 2018 14:12:12 +0000
>
> > Given unlimited time, would the right solution be to use a lib to parse the
> > string as utf-8, and reject strings that are not valid utf-8?
>
> This sounds like a scenario where "stringprep" is helpful (or necessary). It validates strings to be valid utf-8, can check that they obey certain rules (such as "word elements only" which rejects punctuation and the like), and can convert them to a canonical form so equal strings match whether they are encoded the same or not.
Is it a fact that non-ASCII identifiers must be encoded in UTF-8, and
can not include invalid UTF-8 sequences?
next prev parent reply other threads:[~2018-05-21 16:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 9:54 張俊芝
2018-05-21 14:21 ` Simon Marchi
2018-05-21 15:27 ` Paul.Koning
2018-05-21 16:16 ` Eli Zaretskii [this message]
2018-05-21 18:34 ` Paul.Koning
[not found] ` <83tvr0ev0p.fsf@gnu.org>
2018-05-21 19:25 ` Paul.Koning
2018-05-21 20:43 ` Joseph Myers
2018-05-22 10:31 ` 張俊芝
2018-05-22 8:34 ` 張俊芝
[not found] ` <1b915196-3e97-4892-7426-be4211fe7889@zjz.name>
2018-05-21 18:00 ` 張俊芝
2018-05-21 18:03 ` 張俊芝
2018-05-21 18:14 ` Matt Rice
2018-05-22 7:06 ` 張俊芝
2018-05-22 14:39 ` Pedro Alves
2018-05-22 14:39 ` 張俊芝
2018-05-22 15:17 ` Pedro Alves
2018-05-22 16:42 ` Pedro Alves
2018-05-22 17:31 ` 張俊芝
2018-05-22 17:38 ` Pedro Alves
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=834lj1f0ne.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Paul.Koning@dell.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=zjz@zjz.name \
/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