From: Lars Ingebrigtsen <larsi@gnus.org>
To: Howard Melman <hmelman@gmail.com>
Cc: 51292@debbugs.gnu.org
Subject: bug#51292: 27.2; Reversing strings with unicode combining characters
Date: Wed, 20 Oct 2021 10:58:50 +0200 [thread overview]
Message-ID: <875ytsnkc5.fsf@gnus.org> (raw)
In-Reply-To: <lyilxshfrz.fsf@new-host-3.home> (Howard Melman's message of "Tue, 19 Oct 2021 17:21:36 -0400")
Howard Melman <hmelman@gmail.com> writes:
>> But it might make sense to add function to tokenize a string into
>> grapheme clusters -- I can see that being useful. Then the caller can
>> chop and reverse the list of clusters as they wish.
>>
>> `string-tokenize-graphemes'?
>
> I agree that seems potentially useful.
It's not that common to have un-normalised strings, though, and if you
normalise the string first you get
(reverse (ucs-normalize-NFC-string "nai\u0308ve"))
=> "evïan"
as expected. So I think adding more utility functions here wouldn't be
productive (i.e., I don't think they would actually be useful for
people -- they'd just complicate things for users further).
So I think everything here is basically working as designed in Emacs,
and that the design is fine. (And that the s-reverse isn't good.) So
I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-20 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 19:16 bug#51292: 27.2; Reversing strings with unicode combining characters Howard Melman
2021-10-19 19:26 ` Lars Ingebrigtsen
2021-10-19 20:50 ` Lars Ingebrigtsen
2021-10-19 21:21 ` Howard Melman
2021-10-20 8:58 ` Lars Ingebrigtsen [this message]
2021-10-19 23:13 ` Stefan Kangas
2021-10-20 8:11 ` Lars Ingebrigtsen
2021-10-20 13:02 ` Stefan Kangas
2021-10-21 2:50 ` Lars Ingebrigtsen
2021-10-21 3:51 ` Stefan Kangas
2021-10-20 11:50 ` Eli Zaretskii
2021-10-20 11:45 ` Eli Zaretskii
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=875ytsnkc5.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=51292@debbugs.gnu.org \
--cc=hmelman@gmail.com \
/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).