unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Karl Eichwalder <keichwa@gmx.net>
Cc: eliz@is.elta.co.il, emacs-devel@gnu.org
Subject: Re: Reporting UTF-8 related problems?
Date: Tue, 30 Jul 2002 08:01:47 +0200	[thread overview]
Message-ID: <shznw9eotw.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <200207300522.OAA05828@etlken.m17n.org> (Kenichi Handa's message of "Tue, 30 Jul 2002 14:22:33 +0900 (JST)")

Kenichi Handa <handa@etl.go.jp> writes:

>> Char: “ (0150310, 53448, 0xd0c8) point=309 of 321 (96%) column 12 
>
> This is because Emacs received this byte sequence:
> 	ESC $ ( B ! H
> "ESC $ ( B" is a designation sequence for jisx0208, 
> and the following two bytes "! H" specifies the above
> Japanese symbol.

Originally, it was the "right double quote raising" and not meant to be
a special Japanese symbol ;)

> This is a problem of lynx and galeon (or some core part of
> gnome, I don't know).

I will have an eye on it.

> I don't understand what do you mean.  "kill and yank" from
> where to where?  What is the meaning of "marking it"?

Sorry.  This time: from Emacs to Emacs.  I assumed, you can C-d the
current letter and yank it back (C-y).  My assumptions is wrong.  C-d
just deletes; thus C-y cannot yank it back.

> No.  I think your Galeon actually sent `?' to Emacs.  My
> Galeon (ver.1.2.5) sends "ESC % G ... ESC % @".

Oops, my Galeon ist outdated.

> What I suspect is that UTF-8 xterm asks Galeon to send
> selection-data by UTF8_STRING (not by TEXT as Emacs does).

Sounds convincingly.  Thanks.

-- 
ke@suse.de (work) / keichwa@gmx.net (home):              |
http://www.suse.de/~ke/                                  |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)

  reply	other threads:[~2002-07-30  6:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-28 16:14 Reporting UTF-8 related problems? Karl Eichwalder
2002-07-28 18:23 ` Eli Zaretskii
2002-07-28 18:26 ` Eli Zaretskii
2002-07-29  5:18   ` Kenichi Handa
2002-07-29  5:37     ` Kenichi Handa
2002-07-29 15:35     ` Karl Eichwalder
2002-07-30  5:22       ` Kenichi Handa
2002-07-30  6:01         ` Karl Eichwalder [this message]
2002-07-30  7:11           ` Kenichi Handa
2002-07-30  7:57             ` Andreas Schwab
2002-07-30  8:30               ` Kenichi Handa
2002-07-30 18:58             ` Karl Eichwalder
2002-07-30 19:51               ` Karl Eichwalder
2002-07-31  2:59               ` Karl Eichwalder
2002-07-31 12:26               ` Kenichi Handa
2002-07-31 16:29                 ` Karl Eichwalder
2002-08-01  5:18                 ` Eli Zaretskii
2002-08-14  1:21                   ` Kenichi Handa
2002-11-03 20:21                     ` Karl Eichwalder
2002-11-04  4:56                       ` Karl Eichwalder
2002-07-29 17:29   ` 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=shznw9eotw.fsf@tux.gnu.franken.de \
    --to=keichwa@gmx.net \
    --cc=eliz@is.elta.co.il \
    --cc=emacs-devel@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).