From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: escape-quoted
Date: 04 Dec 1998 16:45:56 +0100 [thread overview]
Message-ID: <kigu2zbc3m3.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "04 Dec 1998 15:34:48 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Fabrice POPINEAU <popineau@ese-metz.fr> writes:
>
> > This is the file coding system used by default on the latest
> > pgnus-0.6[1-3] versions for XEmacs, but it is not defined unless
> > XEmacs has been compiled with MULE support. Which is not the case
> > under Win32. What's the proper solution ? Use 'no-conversion ?
>
> Are the coding systems used for XEmacsen without MULE support?
Sometimes. Let me try to illustrate the situation.
Traditionally, you would either compile XEmacs with, or without Mule.
Compiled with Mule, you get multibyte chars, coding systems, fonts,
and all that, including but not limited to 3x slowdown[1]. Compiled
without Mule, you get something that looks more or less like XEmacs
19.16, with the addition of a new "character" type.
The nice thing about Mule is its support for file coding systems,
which allows one to cleanly (as far as anything in Mule is "clean")
solve the problem of DOS and UNIX style text files. So, to avoid
reimplementing a kludge, Andy Piper implemented a `--with-file-coding'
configuration option that turns on only the file-coding-related Mule
features. With that, you get the benefits of clean file coding
support, without the slowdown of Muletilation. So currently, you can
compile XEmacs in three ways:
1) Without Mule or file-coding. This is the default, and it makes
most sense for the people using UNIX, and not caring about I18N.
2) With file-coding. This is done on MS Windows because of the
newline stuff.
3) With Mule. This gets you the all-singing, all-dancing multibyte
support, along with file-coding and stuff. This doesn't yet work
under MS Windows.
So that's history.
[1]
Someone said "30%", but he must have been kidding.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
You know it's going to be a bad day when your twin brother forgot
your birthday.
next prev parent reply other threads:[~1998-12-04 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Shenghuo ZHU's message of "04 Dec 1998 11:31:05 -0500">
1998-12-04 8:56 ` escape-quoted Fabrice POPINEAU
1998-12-04 9:37 ` escape-quoted Andy Piper
1998-12-04 20:16 ` escape-quoted Shenghuo ZHU
1998-12-04 14:34 ` escape-quoted Lars Magne Ingebrigtsen
1998-12-04 15:45 ` Hrvoje Niksic [this message]
1998-12-04 16:38 ` escape-quoted Shenghuo ZHU
1998-12-04 18:16 ` escape-quoted Hrvoje Niksic
1998-12-04 16:31 ` escape-quoted Shenghuo ZHU
1998-12-04 16:38 ` escape-quoted Hrvoje Niksic
1998-12-04 16:50 ` escape-quoted Andy Piper
1998-12-04 22:30 ` escape-quoted Martin Buchholz
1998-12-05 22:50 ` escape-quoted 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=kigu2zbc3m3.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/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).