diff options
author | Přemysl Janouch <p@janouch.name> | 2018-08-01 09:06:14 +0200 |
---|---|---|
committer | Přemysl Janouch <p@janouch.name> | 2018-08-01 09:16:44 +0200 |
commit | f79dd027e9f0ff05d949570b657e1e26b941d3fd (patch) | |
tree | 4753f4844741e0e0aebd19a4f1151011118d44f1 | |
parent | fa78831cbd8741263d401033b3a7692cdca1eb9e (diff) | |
download | xK-f79dd027e9f0ff05d949570b657e1e26b941d3fd.tar.gz xK-f79dd027e9f0ff05d949570b657e1e26b941d3fd.tar.xz xK-f79dd027e9f0ff05d949570b657e1e26b941d3fd.zip |
kike: add a comment about identifier encoding
-rw-r--r-- | kike.c | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -233,6 +233,13 @@ irc_is_valid_host (const char *host) || irc_is_valid_hostaddr (host); } +// TODO: currently, we are almost encoding-agnostic (strings just need to be +// ASCII-compatible). We should at least have an option to enforce a specific +// encoding, such as UTF-8. Note that with Unicode we should not allow all +// character clasess and exclude the likes of \pM with the goal of enforcing +// NFC-normalized identifiers--utf8proc is a good candidate library to handle +// the categorization and validation. + static bool irc_is_valid_user (const char *user) { |