From: Florian Weimer <fw@deneb.cygnus.argh.org>
Subject: Re: more multibyte bugs
Date: 06 May 2000 09:10:34 +0200 [thread overview]
Message-ID: <874s8cupat.fsf@deneb.cygnus.argh.org> (raw)
In-Reply-To: <m3n1m4g84x.fsf@vvv.vsu.ru>
Vladimir Volovich <vvv@vvv.vsu.ru> writes:
> FW> If this can't be done (because making a buffer unibyte is some
> FW> kind of global thing),
>
> what do you mean by word "global"?
It affects a whole buffer, not just some region in it.
> FW> one could add a special coding system designed for encoding raw
> FW> bytes in the range 16#80# .. 16#FF#.
>
> how this could be done?
First, you create a MULE charset containing 128 characters. Then
you write a CCL program which maps characters in the range 16#80# ..
16#FF# to these characters (and vice versa). The resulting characters
are not special in any way (except that you don't have a font to
display them), and no accidental combining occurs.
next prev parent reply other threads:[~2000-05-06 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-05 8:57 Vladimir Volovich
2000-05-05 12:34 ` Florian Weimer
2000-05-05 18:32 ` Vladimir Volovich
2000-05-06 7:10 ` Florian Weimer [this message]
2000-05-05 15:23 ` Shenghuo ZHU
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=874s8cupat.fsf@deneb.cygnus.argh.org \
--to=fw@deneb.cygnus.argh.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.
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 NNTP newsgroup(s).