unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 45660@debbugs.gnu.org
Subject: bug#45660: 28.0.50; Changed word/whitespace syntax
Date: Tue, 05 Jan 2021 20:20:44 +0200	[thread overview]
Message-ID: <87zh1nkzyb.fsf@mail.linkov.net> (raw)
In-Reply-To: <838s98bkyy.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 04 Jan 2021 20:44:37 +0200")

> Previously, many characters, including u+202F, had the punctuation
> ('.') syntax.  I modified that to be more close to the Unicode
> Character Database (UCD), and u+202F is not a punctuation character
> according to the UCD.  It has the Zs general category, which means
> "space separator", the same as SPC, NBSP, EN SPACE, and others.

So according to the Unicode standard it should have whitespace syntax?

And indeed, I see no reason for similar characters to have different syntax:

  name: NO-BREAK SPACE
  general-category: Zs (Separator, Space)
  syntax:   	which means: whitespace

  name: NARROW NO-BREAK SPACE
  general-category: Zs (Separator, Space)
  syntax: w 	which means: word

> Removing u+202F and other similar characters from the "punctuation"
> group had the side effect of leaving it at the default 'w' syntax.
>
> Should we make all Zs characters have the ' ' (whitespace) syntax?
> That should be easy, but we should try being consistent in this
> regard.

Should the word characters separated by NO-BREAK SPACE by treated as one word?
If there is no reason to treat space characters as part of words, then all
characters with the Zs general category could have the same whitespace syntax.





  parent reply	other threads:[~2021-01-05 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 17:25 bug#45660: 28.0.50; Changed word/whitespace syntax Juri Linkov
2021-01-04 18:44 ` Eli Zaretskii
2021-01-04 18:54   ` martin rudalics
2021-01-04 19:19     ` Eli Zaretskii
2021-01-05 18:20   ` Juri Linkov [this message]
2021-01-05 18:45     ` Eli Zaretskii
2021-01-05 18:53     ` martin rudalics
2021-01-05 19:26       ` Eli Zaretskii
2021-01-08 12:06     ` 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=87zh1nkzyb.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=45660@debbugs.gnu.org \
    --cc=eliz@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).