From: Pascal Bourguignon <spam@thalassa.informatimago.com>
Subject: Re: problem with mule-utf-8 ?
Date: 09 Sep 2003 02:08:34 +0200 [thread overview]
Message-ID: <871xuqbz7h.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: 8765k4lsx5.fsf@emacswiki.org
Alex Schroeder <alex@emacswiki.org> writes:
> Pascal Bourguignon <spam@thalassa.informatimago.com> writes:
>
> > Is this a problem with mule, or is it with unicode?
>
> Emacs doesn't do Han-Unification by default. The CVS version has code
> to do that, but until then, if you type Japanese characters using the
> Japanese input methods, they can only be represented in the iso-2022
> encodings, or in specific Japanese encodings such as euc-jp.
I see. Thank you.
--
__Pascal_Bourguignon__
http://www.informatimago.com/
Do not adjust your mind, there is a fault in reality.
prev parent reply other threads:[~2003-09-09 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 14:59 problem with mule-utf-8 ? Pascal Bourguignon
2003-09-06 20:17 ` Eli Zaretskii
2003-09-08 5:47 ` Janusz S. Bień
2003-09-08 14:24 ` Eli Zaretskii
2003-09-07 11:49 ` Alex Schroeder
2003-09-09 0:08 ` Pascal Bourguignon [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
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=871xuqbz7h.fsf@thalassa.informatimago.com \
--to=spam@thalassa.informatimago.com \
/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.
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).