From: Pascal Bourguignon <spam@thalassa.informatimago.com>
Subject: problem with mule-utf-8 ?
Date: 06 Sep 2003 16:59:24 +0200 [thread overview]
Message-ID: <87n0dirmib.fsf@thalassa.informatimago.com> (raw)
Hello,
I'm trying to make an UTF-8 file containing some katakana characters.
So, I take a new buffer, type M-x set-input-method RET japanese-katakana RET
a SPACE e SPACE i SPACE o SPACE C-x C-s, and then it says:
------------------------------------------------------------------------
These default coding systems were tried to encode text
in the buffer `test':
utf-8 iso-latin-1
However, each of them encountered these problematic characters:
iso-latin-1: ア エ イ オ ウ ヤ
utf-8: ア エ イ オ ウ ヤ
The first problematic character is at point in the displayed buffer,
and C-u C-x = will give information about it.
Select one of the following safe coding systems, or edit the buffer:
euc-jp shift_jis iso-2022-jp japanese-iso-7bit-1978-irv
iso-2022-7bit
Or specify any other coding system
on your risk of losing the problematic characters.
------------------------------------------------------------------------
So, what's the matter? I thought that unicode inclued all the
characters, and that utf-8 was able to transcribe all unicode
character, or not?
Of course, I insist and save it with utf-8 encoding, then when I load
this utf-8 file later, I get rectangle frames instead of katakana...
Is this a problem with mule, or is it with unicode?
--
__Pascal_Bourguignon__ http://www.informatimago.com/
----------------------------------------------------------------------
Do not adjust your mind, there is a fault in reality.
next reply other threads:[~2003-09-06 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 14:59 Pascal Bourguignon [this message]
2003-09-06 20:17 ` problem with mule-utf-8 ? 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
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=87n0dirmib.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).