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: Fri, 03 Dec 2021 21:27:11 +0200 [thread overview]
Message-ID: <83r1at7als.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkw-JudWWEdqdTeZ+BqsJ-7GWK-kMeb2MpM+5eSY4kjNQ@mail.gmail.com> (message from Stefan Kangas on Fri, 3 Dec 2021 10:37:10 -0800)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 3 Dec 2021 10:37:10 -0800
>
> I believe this comment in lisp/nxml/xsd-regexp.el can be removed as
> Emacs supports Unicode now:
>
> ;; The semantics of XSD regexps are defined in terms of Unicode.
> ;; Non-Unicode characters are not allowed in regular expressions and
> ;; will not match against the generated regular expressions. A
> ;; Unicode character means a character in one of the Mule charsets
> ;; ascii, latin-iso8859-1, mule-unicode-0100-24ff,
> ;; mule-unicode-2500-33ff, mule-unicode-e000-ffff, eight-bit-control
> ;; or a character translatable to such a character (i.e a character
> ;; for which `encode-char' will return non-nil).
> ;;
> ;; Unfortunately, this means that this package is currently useless
> ;; for CJK characters, since there's no mule-unicode charset for the
> ;; CJK ranges of Unicode. We should devise a workaround for this
> ;; until the fabled Unicode version of Emacs makes an appearance.
>
> 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.
next prev parent reply other threads:[~2021-12-03 19:27 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 [this message]
2021-12-04 13:07 ` Stefan Kangas
2021-12-04 16:16 ` Eli Zaretskii
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=83r1at7als.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).