unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Cc: mariano@gnome.org, alexander.winston@comcast.net,
	emacs-devel@gnu.org, danilo@gnome.org, monnier@iro.umontreal.ca,
	miles@gnu.org
Subject: Re: Possible UTF-8 CJK Regressions in Terminal Emulators
Date: Thu, 18 Mar 2004 15:34:07 +0000	[thread overview]
Message-ID: <rzqvfl2yxsg.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: 200403010815.RAA14365@etlken.m17n.org

[I don't know what this has to do with the subject.]

Kenichi Handa <handa@m17n.org> writes:

> In article <buoeksjyee3.fsf@mcspd15.ucom.lsi.nec.co.jp>, Miles Bader <miles@lsi.nec.co.jp> writes:
>
>> Alexander Winston <alexander.winston@comcast.net> writes:
>>>  Okay, back to UTF-8. With regard to CJK being disabled to default, I
>>>  believe that this decision is rather prejudicial to many Asian users.

I don't think so.  There's no reason why you shouldn't define a
language environment corresponding to ja_JP.UTF-8 which turned it on
(not that language environments is the right approach to locale
handling).

Anyway, there seems to be very little interest from users; I don't
recall any of the contributions I expected.  Mostly I've just had
unhelpful remarks from non-CJK users.

>> I've been told that the reason `utf-translate-cjk-mode' is disabled by
>> default is that it consumes some non-trivial amount of memory (and
>> loading time,

Yes.  If I remember correctly, I posted measurements.

>> unless it's dumped I guess).

It doesn't make sense to dump it, the way it works.

> As we have post-read-conversion function for utf-8, it is
> possible to detect untranslated CJK characters and translate
> them.
>
> How abut this?
>
> Change utf-translate-cjk-mode to a customizable variable
> utf-translate-cjk which is nil, t, or auto (default).  The
> values nil and t mean the same thing as the current value of
> utf-translate-cjk-mode.  The value `auto' means setting up
> tables for translating CJK characters automatically if
> necessary.
>
> By adding pre-write-conversion function, we can make the
> above work also on writing.  But, in that case, it seems
> difficult to make find-coding-systems-region/string work
> consistently.  To check if a text is encodable by utf-8, we
> must load translation tables.

As far as I remember, that's why I didn't implement that sort of
thing.  post-read-conversion machinery is already there, I think.

[Is this code base ever going to be released so that most users
actually can use it?]

       reply	other threads:[~2004-03-18 15:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1077557604.1632.26.camel@duende>
     [not found] ` <jwv3c90bgi7.fsf-monnier+emacs/pretest@asado.iro.umontreal.ca>
     [not found]   ` <1077643915.12919.2.camel@duende>
     [not found]     ` <jwvwu6c6yca.fsf-monnier+emacs/pretest@asado.iro.umontreal.ca>
     [not found]       ` <1077682436.28482.9.camel@duende>
     [not found]         ` <buoeksjyee3.fsf@mcspd15.ucom.lsi.nec.co.jp>
     [not found]           ` <200403010815.RAA14365@etlken.m17n.org>
2004-03-18 15:34             ` Dave Love [this message]
2004-04-07 12:30               ` Possible UTF-8 CJK Regressions in Terminal Emulators Kenichi Handa
2004-04-08 11:27                 ` Dave Love
2004-04-09 11:28                   ` Kenichi Handa
2004-06-07 12:27                     ` Kenichi Handa
2004-06-07 12:36                       ` Miles Bader
2004-06-07 13:00                         ` Kenichi Handa
2004-06-08 18:02                           ` Dave Love
2004-06-09  7:37                             ` Kenichi Handa
2004-06-09  9:38                               ` Stefan Monnier
2004-06-10  0:20                                 ` Kenichi Handa
2004-06-08 17:56                       ` Dave Love
2004-06-09  7:24                         ` Kenichi Handa
2004-06-12  2:41                       ` Kenichi Handa
2004-06-12 13:46                         ` Juanma Barranquero
2004-06-13  8:42                           ` Kenichi Handa
2004-06-13 11:36                             ` Juanma Barranquero
2004-06-13 13:18                             ` Andreas Schwab
2004-06-14  1:05                               ` Kenichi Handa
2004-06-13 20:39                             ` Luc Teirlinck

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=rzqvfl2yxsg.fsf@albion.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    --cc=alexander.winston@comcast.net \
    --cc=danilo@gnome.org \
    --cc=emacs-devel@gnu.org \
    --cc=mariano@gnome.org \
    --cc=miles@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).