From: Eli Zaretskii <eliz@gnu.org>
To: Chen Bin <chenbin.sh@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] add 'string-distance' to calculate Levenshtein distance
Date: Sat, 14 Apr 2018 20:08:51 +0300 [thread overview]
Message-ID: <83d0z14sws.fsf@gnu.org> (raw)
In-Reply-To: <87o9ilhhcd.fsf@gmail.com> (message from Chen Bin on Sun, 15 Apr 2018 02:40:18 +1000)
> From: Chen Bin <chenbin.sh@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Sun, 15 Apr 2018 02:40:18 +1000
>
> Correct me if I'm wrong.
>
> I read cod eand found definion of Lisp_String:
> struct GCALIGNED Lisp_String
> {
> ptrdiff_t size;
> ptrdiff_t size_byte;
> INTERVAL intervals; /* Text properties in this string. */
> unsigned char *data;
> };
>
> I understand string text is encoded in UTF8 format and is stored in
> 'Lisp_String::data'. There is actually no difference between unibyte
> and multibyte text since UTF8 is compatible with ASCII and we only deal
> with 'data' field.
No, that's incorrect. The difference does exist, it just all but
disappear for unibyte strings encoded in UTF-8. But if you encode a
string in some other encoding, like Latin-1, you will see a very
different stream of bytes.
> I attached the latest patch.
Thanks.
> + ;; string containing unicode character (Hanzi)
> + (should (equal 6 (string-distance "ab" "ab我她")))
> + (should (equal 3 (string-distance "我" "她"))))
Should the distance be measured in bytes or in characters? I think
it's the latter, in which case the implementation should work in
characters, not bytes.
next prev parent reply other threads:[~2018-04-14 17:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 2:35 [PATCH] add 'string-distance' to calculate Levenshtein distance Chen Bin
2018-04-14 7:05 ` Eli Zaretskii
[not found] ` <87lgdq831h.fsf@gmail.com>
2018-04-14 13:24 ` Eli Zaretskii
2018-04-14 16:40 ` Chen Bin
2018-04-14 17:08 ` Eli Zaretskii [this message]
2018-04-15 7:15 ` Chen Bin
2018-04-15 14:47 ` Eli Zaretskii
[not found] ` <CAAE-R+-RDWvyrv+uqHszzh6VMH6An3disOw=PyPWaTnUTHDOCw@mail.gmail.com>
[not found] ` <83k1t72b2o.fsf@gnu.org>
2018-04-17 2:43 ` chen bin
2018-04-17 15:44 ` Eli Zaretskii
2018-04-18 7:11 ` chen bin
[not found] ` <CAAE-R+8s++_LRcQCLX60Z=TQeQHdtbM5X1k525bfNnnPSLDvRw@mail.gmail.com>
[not found] ` <83bmei36dw.fsf@gnu.org>
2018-04-17 12:31 ` chen bin
2018-04-19 8:05 ` Eli Zaretskii
2018-04-19 14:55 ` chen bin
2018-04-20 4:37 ` chen bin
2018-04-20 6:01 ` Thien-Thi Nguyen
2018-04-20 10:47 ` chen bin
2018-04-21 7:22 ` Eli Zaretskii
2018-04-21 20:47 ` Juri Linkov
2018-04-28 7:36 ` Eli Zaretskii
2018-05-06 9:53 ` chen bin
2018-04-15 18:53 ` Paul Eggert
2018-04-14 17:18 ` Nathan Moreau
2018-04-14 17:36 ` Paul Eggert
2018-04-15 18:17 ` Andreas Politz
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=83d0z14sws.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=chenbin.sh@gmail.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).