unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@etl.go.jp>
Cc: rms@gnu.org, ulrich@a0.complang.tuwien.ac.at, emacs-devel@gnu.org
Subject: Re: Latin-1 non breaking space not highlighted
Date: Mon, 15 Apr 2002 08:54:04 +0900 (JST)	[thread overview]
Message-ID: <200204142354.IAA01951@etlken.m17n.org> (raw)
In-Reply-To: "eliz@is.elta.co.il"'s message of Sun, 14 Apr 2002 07:10:36 +0300

"Eli Zaretskii" <eliz@is.elta.co.il> writes:
>>  It looks like there is a real problem.  I guess we should not simply
>>  change show-trailing-whitespace to use the whitespace syntax class.

> I see two possible solutions:

>   - hardcode a few more special characters, like ISO8859-x NBSP and a
>     few Unicode characters;
> or
>   - use syntax tables for non-ASCII characters only, assuming that no
>     Lisp package does anything weird with their syntax class.

I think show-trailing-whitespace should not be affected by
syntax of characters because what it should concern is a
glyph.  If a glyph of a character is just space, even if the
syntax is `symbol' or whatever else, it should be
highlighted.

So, what we need is a char-table of such characters that are
displayed by white glyph.  In addition to many NBSPs, that
char-table should also contain the following CJK white-space
characters:
 (make-char 'japanese-jisx0208-1978 33 33)
 (make-char 'chinese-gb2312 33 33)
 (make-char 'japanese-jisx0208 33 33)
 (make-char 'korean-ksc5601 33 33)
 (make-char 'chinese-cns11643-1 33 33)
 (make-char 'japanese-jisx0213-1 33 33)
 (make-char 'chinese-big5-1 33 33)

---
Ken'ichi HANDA
handa@etl.go.jp

             reply	other threads:[~2002-04-14 23:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-14 23:54 Kenichi Handa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-22  1:53 Latin-1 non breaking space not highlighted Kenichi Handa
2002-04-22 22:37 ` Richard Stallman
2002-04-19  1:55 Kenichi Handa
2002-04-19 13:55 ` Stefan Monnier
2002-04-19 14:07   ` Miles Bader
2002-04-14 23:30 Ulrich Neumerkel
2002-04-16 20:16 ` Richard Stallman
     [not found] <Pine.SUN.3.91.1020408100627.28830A-100000@is>
2002-04-09 12:08 ` Richard Stallman
2002-04-09 14:37   ` Eli Zaretskii
2002-04-10 20:16     ` Richard Stallman
2002-04-11 18:54       ` Eli Zaretskii
2002-04-12  8:18         ` Eli Zaretskii
2002-04-13 19:06           ` Richard Stallman
2002-04-14  4:10             ` Eli Zaretskii
2002-04-15 21:59               ` Richard Stallman
2002-04-18  5:38                 ` Eli Zaretskii
2002-04-18 10:18                   ` Stefan Monnier
2002-04-18 11:33                     ` Eli Zaretskii
2002-04-18 10:36                       ` Stefan Monnier
2002-04-19  5:25                     ` Richard Stallman

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=200204142354.IAA01951@etlken.m17n.org \
    --to=handa@etl.go.jp \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=ulrich@a0.complang.tuwien.ac.at \
    /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).