GNU bug report logs - #51733
27.1; Detect impossible email addresses better

Previous Next

Packages: gnus, emacs;

Reported by: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>

Date: Wed, 10 Nov 2021 00:29:01 UTC

Severity: wishlist

Found in version 27.1

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #119 received at 51733 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 51733 <at> debbugs.gnu.org, jidanni <at> jidanni.org
Subject: Re: bug#51733: 27.1; Detect impossible email addresses better
Date: Mon, 17 Jan 2022 18:38:48 +0100
I'm looking at the Confusable section now. 

https://www.unicode.org/reports/tr39/#Confusable_Detection

Looks easy enough to implement (and the ELPA package already does the
parsing, so I'll be reusing bits from that).

But...  I'm wondering what the higher level interface would be?  I mean,
quite a lot of strings are confusable with something else, but which
ones are interesting?  The only thing that seems immediately interesting
to check for is whether a string is confusable with ASCII?

That is,

(textsec-confusable-with-ascii-p "C𝗂𝗋𝖼𝗅𝖾")
=> t

Because the ASCII characters are the ones that people rely on when doing
... things, like email and browsing the web.

But I mean, "C𝗂𝗋𝖼𝗅𝖾" is confusable with "БігсӀС" (the latter is
Cyrillic), and if you're writing Russian, that might also be
interesting.  So perhaps a 

(textsec-confusable-with-script-p "C𝗂𝗋𝖼𝗅𝖾" 'cyrillic)
=> t

?  But...  I'm not sure in which contexts that would actually be vital
to know.  Hm.

Anybody have any thoughts here?  

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





This bug report was last modified 3 years and 124 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.