unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Cc: wl@gnu.org, kazu@iijlab.net, emacs-devel@gnu.org
Subject: Re: severe problems with composite characters
Date: Thu, 18 Sep 2003 10:24:46 +0100	[thread overview]
Message-ID: <rzq4qza5u01.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: 200309170649.PAA10318@etlken.m17n.org

Kenichi Handa <handa@m17n.org> writes:

> In article <20030917.074537.51710930.wl@gnu.org>, Werner LEMBERG <wl@gnu.org> writes:

[...]

>> Suppose that composite characters are stored to a file with a
>> multi-lingual coding-system. An example is TIS-620 characters with
>> UTF-8 (or ctext).
>
>> When Emacs reads the file, the composite characters are not composed
>> since there is no post-conv function associated to the multi-lingual
>> coding-system.

ctext works for me, the same as iso-2022-7bit (which C-h h uses).
Those coding systems store composition information as escape
sequences, so post-conversion isn't relevant for them (unlike utf-8).

Is the width being wrong a severe problem somehow, or is the severity
mentioned in the subject just the lack of composition?  (I ask partly
because character width is currently somewhat ambiguous in Emacs 22,
e.g. for non-CJK characters from CJK coding systems.)

> But, I've just found a bug in this facility, and installed a
> fix.

What bug?  I can't see a log message.

  reply	other threads:[~2003-09-18  9:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-17  5:45 severe problems with composite characters Werner LEMBERG
2003-09-17  6:49 ` Kenichi Handa
2003-09-18  9:24   ` Dave Love [this message]
2003-09-30 11:22     ` Kenichi Handa
2003-09-19  8:37   ` Kazu Yamamoto
2003-09-19 11:06     ` Kenichi Handa

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=rzq4qza5u01.fsf@albion.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    --cc=emacs-devel@gnu.org \
    --cc=kazu@iijlab.net \
    --cc=wl@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).