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

Previous Next

Full log

Message #107 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:09:19 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

> I don't think I understand what you mean by "the Asian parts".  Do you
> mean the CJK parts where we lump several scripts together into 'han'
> and 'kana'?

Possibly -- I haven't looked closely.

>> It's impossible to implement the Unicode security recommendations based
>> on the Blocks.txt data -- it's that simple.
>
> Can you tell more about why it is impossible?  If it's a relatively
> simple issue of "translating" the Unicode script names into ours, then
> it should be quite simple.  Since you say it's impossible, I guess
> there's some factor(s) here that I miss?

Perhaps there's something I'm missing, because it seems self-evident to
me that the Blocks data can't be used for this.

For instance,

(textsec-single-script-p "ޱ﷽")
=> t

but

(elt char-script-table ?ޱ)
=> thaana

(elt char-script-table ?﷽)
=> arabic

I think the Unicode people have the authoritative say here, so
implementing the recommendations seems like the way to go.  And it's
less work in the long run, because we can just import the data files and
not try to fix things up manually (like blocks.awk attempts to do).

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

Previous Next

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