zsh-workers
 help / color / mirror / code / Atom feed
From: Daiki Ueno <ueno@unixuser.org>
To: "Bart Schaefer" <schaefer@brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: Problem inputting Japanese using XIM
Date: Tue, 22 Jan 2002 11:35:12 +0900	[thread overview]
Message-ID: <c8899158-bf43-4067-ada4-ace3133ed74d@deisui.bug.org> (raw)
In-Reply-To: <020121152432.ZM27716@candle.brasslantern.com> (Bart Schaefer's message of "Mon, 21 Jan 2002 15:24:32 -0800")

>>>>> In <020121152432.ZM27716@candle.brasslantern.com> 
>>>>>	"Bart Schaefer" <schaefer@brasslantern.com> wrote:

> > I'm wondering why zsh considers characters in the [0x80, 0xa0] range
> > as control characters?

> Zsh does not handle multibyte character sets, in general.  Internally it
> always treats a single byte as a single character.  The characters with
> ASCII values above 128 are meta-characters, and those in the range 128-
> 159 are control-meta-characters (just as 0-31 are control without meta).

Thank you for the response, I understood that.

By the way, the control-character formatting routines can be found here
and there in Src/Zle/*.c.  While they convert 0x0a into the form of "^J"
and so on, it seems that which is only helpful in displaying C0
characters, not C1 characters.  Is this expected?

The actual code is as follows:

(snipped off Src/Zle/zle_refresh.c:1122 ...)
	} else if (line[t0] == 0x7f) {
	    *vp++ = '^';
	    *vp++ = '?';
	} else if (icntrl(line[t0])) {
	    *vp++ = '^';
	    *vp++ = line[t0] | '@';
	} else
	    *vp++ = line[t0];

Regards,
-- 
Daiki Ueno


      reply	other threads:[~2002-01-22  2:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21  7:01 Daiki Ueno
2002-01-21 23:24 ` Bart Schaefer
2002-01-22  2:35   ` Daiki Ueno [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c8899158-bf43-4067-ada4-ace3133ed74d@deisui.bug.org \
    --to=ueno@unixuser.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).