unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Yuri Khan <yurivkhan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: [OFFTOPIC] Re: Invoking a function from a list of functions
Date: Thu, 29 Nov 2018 01:15:41 +0700	[thread overview]
Message-ID: <CAP_d_8Ua2TK7DaHUPe0SF8jd_1rKdqQRbEt7OM5HhsfPsjFiLg@mail.gmail.com> (raw)
In-Reply-To: <83wooxduzz.fsf@gnu.org>

On Thu, Nov 29, 2018 at 12:21 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > >>> (á, á)> > (2, 2)
> >
> > In my view python does it right(er) than elisp
>
> That's debatable: the Unicode Standard says to act according to
> canonical equivalence only in text, whereas the above are symbol
> names.  We do display them the same (if the font supports that), but
> we aren't under any obligation to map them to the same symbols, IMO.

Standard Annex 31 deals with identifiers in programming languages, and
recommends considering identifiers equivalent if they are the same
under Normalization Form C for case-sensitive languages (such as
Python and Elisp).

(It suggests using Normalization Form KC for case-insensitive
languages, although I do not see how compatibility decomposition is
similar to case folding.)

> > ELISP>  (list Α A)
> > ("hi" "there")
>
> Why bad?  Those characters are not canonically equivalent.

They are not even compatibility equivalent. Homoglyphic, yes, but not
equivalent in any way.

> If you
> want to go by compatibility equivalence, you will enter a slippery
> slope, where, for example, Ⅰ and 1 will yield the same symbol or even
> the same number.

No they won’t. Compatibility decomposition of U+2160 ROMAN NUMERAL ONE
is U+0073 LATIN CAPITAL LETTER I.



  reply	other threads:[~2018-11-28 18:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3677.1541718983.1284.help-gnu-emacs@gnu.org>
2018-11-12  5:39 ` Invoking a function from a list of functions Rusi
2018-11-12 15:19   ` [OFFTOPIC] " Stefan Monnier
     [not found]   ` <mailman.3921.1542036006.1284.help-gnu-emacs@gnu.org>
2018-11-16  2:48     ` Rusi
2018-11-16 16:40       ` James K. Lowden
2018-11-17 15:59         ` Rusi
2018-11-19 22:23           ` James K. Lowden
2018-11-19 23:11             ` Stefan Monnier
2018-11-20  6:15               ` Amin Bandali
2018-11-21 15:05                 ` Stefan Monnier
2018-11-23  3:41                   ` Amin Bandali
     [not found]               ` <mailman.4291.1542694542.1284.help-gnu-emacs@gnu.org>
2018-11-28 14:14                 ` Rusi
2018-12-11 18:48                   ` Amin Bandali
     [not found]             ` <mailman.4280.1542669123.1284.help-gnu-emacs@gnu.org>
2018-11-28 14:10               ` Rusi
2018-11-28 16:31                 ` Eli Zaretskii
2018-11-28 18:15                   ` Yuri Khan [this message]
2018-11-28 18:57                     ` Eli Zaretskii
2018-11-28 19:08                       ` Yuri Khan
     [not found]                       ` <mailman.4820.1543432126.1284.help-gnu-emacs@gnu.org>
2018-11-29  5:37                         ` Rusi
2018-11-16 16:40       ` James K. Lowden
2018-11-16 17:15         ` Drew Adams

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP_d_8Ua2TK7DaHUPe0SF8jd_1rKdqQRbEt7OM5HhsfPsjFiLg@mail.gmail.com \
    --to=yurivkhan@gmail.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).