From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 52263@debbugs.gnu.org
Subject: bug#52263: Stale comment in xsd-regexp.el about Emacs not supporting Unicode
Date: Sat, 04 Dec 2021 18:16:38 +0200 [thread overview]
Message-ID: <83o85w5ord.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=iR4q+XfwhoaNt-_YSfA_xf8+Y1p4DBLtH8qCAiOObHQ@mail.gmail.com> (message from Stefan Kangas on Sat, 4 Dec 2021 14:07:46 +0100)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 4 Dec 2021 14:07:46 +0100
> Cc: 52263@debbugs.gnu.org
>
> >> Is that correct?
> >
> > Probably. The mule-Unicode-* stuff is definitely obsolete. The only
> > thing that bothers me is what happens with eight-bit characters in the
> > XSD regexps -- are they allowed? Emacs in general does allow them.
> > If xsd-regexp.el doesn't, that should be stated there.
>
> Hmm, so probably more work is needed here than just removing the above
> comment. There is a lot of non-trivial mule and conversion stuff going
> on in that library that might need a proper look by someone that knows
> this stuff well.
Mainly that file needs simplification: we in effect have a single
range of characters, with the possible exception of the codepoints
between 128 and 160. Also, decode-char is now a no-op when the 1st
arg is 'ucs'.
I can offer help in those parts where you don't feel you understand
the issue well enough to make the simplifications.
next prev parent reply other threads:[~2021-12-04 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 18:37 bug#52263: Stale comment in xsd-regexp.el about Emacs not supporting Unicode Stefan Kangas
2021-12-03 19:27 ` Eli Zaretskii
2021-12-04 13:07 ` Stefan Kangas
2021-12-04 16:16 ` Eli Zaretskii [this message]
2021-12-05 17:34 ` Stefan Kangas
2021-12-05 17:48 ` Eli Zaretskii
2021-12-05 18:20 ` Stefan Kangas
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=83o85w5ord.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52263@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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).