unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
Cc: emacs-devel@gnu.org
Subject: Re: utf-8 cjk translation bug?
Date: 30 Sep 2003 19:05:07 +0900	[thread overview]
Message-ID: <buoisna1tik.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <3F7951CD.5050401@gnu.org>

Jason Rumney <jasonr@gnu.org> writes:
> > `C-u C-x =' shows the boxes as being in charset
> > mule-unicode-e000-ffff; the rest of the characters are still listed
> > as being in japanese-jisx0208.
> 
> I guess you would need a unicode font that includes double-width roman
> characters. Or frob utf-translate-cjk-mode to ignore the fact that those
> characters are within the representable range of unicode characters and
> convert them to jisx0208 anyway.

Why would that be necessary?  The purpose of utf-translate-cjk-mode is
to translate external unicode encodings to/from emacs charsets.  For
instance, after reading the utf-8 file, the katakana characters in the
example I gave are represented in emacs using japanese-jisx0208, and
displayed using a JISX0208.1983 encoded font.  I don't think unicode
fonts come into play at all.

-Miles
-- 
Yo mama's so fat when she gets on an elevator it HAS to go down.

  reply	other threads:[~2003-09-30 10:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30  8:30 utf-8 cjk translation bug? Miles Bader
2003-09-30  9:50 ` Jason Rumney
2003-09-30 10:05   ` Miles Bader [this message]
2003-09-30 12:59 ` Kenichi Handa
2003-10-01 12:44   ` Dave Love
2003-10-02  1:08     ` Kenichi Handa
2003-10-03 16:04       ` Dave Love
2003-10-03 16:34         ` Jason Rumney
2003-10-06  2:29           ` Miles Bader
2003-10-06 20:00             ` Miles Bader
2003-10-06 20:53               ` Jason Rumney
2003-10-06 23:18               ` Kenichi Handa
2003-10-07  9:57               ` Stephen J. Turnbull
2003-10-07 11:41             ` Dave Love
2003-10-07 11:40           ` Dave Love
2003-10-06 23:53         ` Kenichi Handa
2003-10-10 16:56           ` Dave Love
2003-10-13 23:55             ` 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=buoisna1tik.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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).