From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: Stefan Monnier <monnier+gnu/emacs@rum.cs.yale.edu>, emacs-devel@gnu.org
Subject: Re: Editing the 0x80..0x90 characters
Date: Thu, 09 May 2002 14:29:09 -0400 [thread overview]
Message-ID: <200205091829.g49IT9s17167@rum.cs.yale.edu> (raw)
In-Reply-To: Pine.SUN.3.91.1020509075629.2376F-100000@is
> > Currently those coding systems
> > decode into (or encode from) ascii + latin-iso8859-5 + eight-bit-control
> > + eight-bit-graphic. The idea is to change it to decode into
> > ascii + latin-iso8859-5 + mule-unicode. So I don't see how the problem
> > is mixed character sets is changed.
>
> I thought that the purpose of that part of the change was to make the
> situation better, not just modify the charsets into which the text is
> decoded. Sorry if I misunderstood.
;-)
I think the idea was that using mule-unicode is better than using
eight-bit-graphic. For instance saving in utf-8 should then work.
Also it would solve the problem of dislaying those chars since you then just
need a unicode font (wasn't that the origin of this thread?).
> > What do you think of the patch below ?
> Can you say a few words about its purpose? I could figure that out from
> the code, but having some description as guidelines would help. TIA.
I hope the paragraph above makes it more clear.
> > I'm not sure what the koi8-u stuff is about. I suspect it's also
> > meant for ukrainian so the new language environment should maybe
> > be "Ukrainian" rather than "Cyrillic-KOI8-U" since that's what
> > mule-cmds.el seems to expect for the "uk" locale.
>
> KOI8-U is indeed for the Ukrainian language. But I don't understand the
> last part: what is the importance of calling the language environment
> "Ukrainian" rather than "Cyrillic-KOI8-U"? Is that just to make it
> easier for Ukrainian users to understand it's for them, or is there
> something else involved?
Check out mule-cmds.el and you'll see that there is already a mapping
from the "uk" locale to the "Ukrainian" language environment (although
this environment doesn't seem to exist yet). I don't think the actual name
has any importance otherwise.
Stefan
next prev parent reply other threads:[~2002-05-09 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <uuoffynbfb.fsf@nbsp.nsk.su>
[not found] ` <3CD177AB.75299AE0@is.elta.co.il>
[not found] ` <uubsbxn65h.fsf@nbsp.nsk.su>
[not found] ` <3CD2581B.42469AF1@is.elta.co.il>
[not found] ` <5l6625dsfu.fsf@rum.cs.yale.edu>
[not found] ` <3CD2E2E5.4EF10708@is.elta.co.il>
[not found] ` <5lsn56cf58.fsf@rum.cs.yale.edu>
[not found] ` <3CD5F7CB.F2FFD9B4@is.elta.co.il>
2002-05-09 0:15 ` Editing the 0x80..0x90 characters Stefan Monnier
2002-05-09 5:05 ` Eli Zaretskii
2002-05-09 18:29 ` Stefan Monnier [this message]
2002-05-09 18:57 ` Eli Zaretskii
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=200205091829.g49IT9s17167@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@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 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.