From: Juri Linkov <juri@jurta.org>
To: Kenichi Handa <handa@m17n.org>
Cc: dak@gnu.org, Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
Subject: Re: new Emacs HELLO file??
Date: Wed, 02 Sep 2009 00:27:57 +0300 [thread overview]
Message-ID: <873a762ylx.fsf@mail.jurta.org> (raw)
In-Reply-To: <tl7hbvmq4dk.fsf@m17n.org> (Kenichi Handa's message of "Tue, 01 Sep 2009 20:41:11 +0900")
>>>>>> BTW, I think we should convert HELLO to UTF-8. Do you see any symbol
>>>>>> in HELLO not supported by UTF-8?
>>>>>
>>>>> Isn't it currently UTF-8?
>>>>
>>>> It's iso-2022-7bit, and converting it to utf-8 would lose the cjk
>>>> variants.
>> >
>> > Since Emacs-23 has utf-8 as its internal encoding, I have my
>> > problems to see how they are not lost anyway.
>
>> See the charset properties.
>
> As iso-2022-7bit has designation sequences for each
> character set, Emacs can use that information to add proper
> `charset' property, and that property infulence the font
> selection.
The purpose of the HELLO file is to demonstrate Emacs multilingual
capabilities. It currently does this using iso-2022-7bit. Does this
mean that UTF-8 is not the best coding system for multilingual texts
in Emacs, because UTF-8 has some limitations (doesn't provide the
proper font selection, loses cjk variants), so iso-2022-7bit is the
preferable coding system for multilingual texts in Emacs? Is it possible
to improve the UTF-8 support in Emacs since most files use it nowadays?
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-09-01 21:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 21:27 new Emacs HELLO file?? kawabata.taichi
2009-08-28 22:19 ` Juri Linkov
2009-08-29 2:16 ` 川幡 太一
2009-08-29 3:31 ` Stefan Monnier
2009-08-29 5:46 ` Daniel Clemente
2009-08-29 22:43 ` Juri Linkov
2009-08-30 1:16 ` kawabata.taichi
2009-08-30 3:12 ` Eli Zaretskii
2009-08-31 3:33 ` Richard Stallman
2009-08-31 16:10 ` kawabata.taichi
2009-08-31 17:07 ` Rupert Swarbrick
2009-08-31 16:16 ` Juri Linkov
2009-08-30 20:48 ` Juri Linkov
2009-08-31 15:12 ` Chong Yidong
2009-08-31 16:14 ` Juri Linkov
2009-08-31 16:15 ` Andreas Schwab
2009-08-31 16:32 ` David Kastrup
2009-08-31 17:02 ` Andreas Schwab
2009-09-01 11:41 ` Kenichi Handa
2009-09-01 21:27 ` Juri Linkov [this message]
2009-09-03 13:07 ` Kenichi Handa
2009-09-06 18:20 ` 牛粥
2009-09-06 20:01 ` Eli Zaretskii
2009-09-06 21:08 ` 牛粥
2009-09-07 1:02 ` Kenichi Handa
2009-09-07 1:01 ` Kenichi Handa
2009-08-31 17:55 ` Eli Zaretskii
2009-08-31 22:03 ` Andreas Schwab
2009-09-08 0:12 ` kawabata.taichi
2009-09-08 2:53 ` Stephen J. Turnbull
2009-09-12 13:52 ` Per Starbäck
2009-09-12 17:51 ` 川幡 太一
2009-09-08 3:11 ` Eli Zaretskii
2009-09-12 17:45 ` Taichi KAWABATA
2009-09-12 19:39 ` Eli Zaretskii
2009-09-15 5:20 ` Kenichi Handa
2009-09-15 8:08 ` David Kastrup
2009-09-15 17:20 ` Eli Zaretskii
2009-09-15 17:12 ` Eli Zaretskii
2009-09-09 0:47 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873a762ylx.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.