Re: master a1ffee1e82: Add textsec-restriction-level function

[Robert Pluim <rpluim@gmail.com>]

>>>>> On Mon, 17 Jan 2022 10:24:30 -0500 (EST), Lars Ingebrigtsen <larsi@gnus.org> said:

    Lars> branch: master
    Lars> commit a1ffee1e82b7152772da86a3adc7513128ffefdf
    Lars> Author: Lars Ingebrigtsen <larsi@gnus.org>
    Lars> Commit: Lars Ingebrigtsen <larsi@gnus.org>

    Lars>     Add textsec-restriction-level function
    
    Lars>     * lisp/international/textsec.el (textsec-restriction-level): New
    Lars>     function.
    Lars> ---
    Lars>  lisp/international/textsec.el            | 52 ++++++++++++++++++++++++++++++++
    Lars>  test/lisp/international/textsec-tests.el | 12 ++++++++
    Lars>  2 files changed, 64 insertions(+)

    Lars> diff --git a/lisp/international/textsec.el b/lisp/international/textsec.el
    Lars> index 884425d492..fc809d52c1 100644
    Lars> --- a/lisp/international/textsec.el
    Lars> +++ b/lisp/international/textsec.el
    Lars> @@ -97,6 +97,58 @@ Not that a string may have several different minimal cover sets."
    Lars>        (setq set (seq-union set (seq-difference s set))))
    Lars>      (sort (delq 'common (delq 'inherited set)) #'string<)))
 
    Lars> +(defun textsec-restriction-level (string)
    Lars> +  "Say what restriction level STRING qualifies for.
    Lars> +Levels are (in order of restrictiveness) `ascii-only',
    Lars> +`single-script', `highly-restrictive', `moderately-restrictive',
    Lars> +`minimally-restrictive' and `unrestricted'."

I assume this is 'decreasing order of restrictiveness'? If so we
should perhaps say so.

Robert
--