escape-quoted

escape-quoted

[Fabrice POPINEAU]

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 ?

Thanks,

Fabrice Popineau

Re: escape-quoted

[Andy Piper]

At 09:56 04/12/98 +0100, Fabrice POPINEAU wrote:
>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 ?

The proper solution is probably to enable escape quoted behaviour under
file-coding but that entails enabling multibyte support which I don't want
to do. In the past we have just created dummy coding systems copied from
no-conversion. see coding.el.

andy
---------------------------------------------------------------------------
" .sigs are like your face - rarely seen by you and uglier than you think"
Dr Andy Piper, Technical Architect, Parallax Solutions Ltd
mail: andyp@parallax.co.uk web: www.parallax.co.uk/~andyp

Re: escape-quoted

[Lars Magne Ingebrigtsen]

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?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: escape-quoted

[Hrvoje Niksic]

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.

Re: escape-quoted

[Shenghuo ZHU]

>>>>> "FP" == Fabrice POPINEAU <popineau@ese-metz.fr> writes:

FP> This is the file coding system used by default on the latest
FP> pgnus-0.6[1-3] versions for XEmacs, but it is not defined unless
FP> XEmacs has been compiled with MULE support. Which is not the case
FP> under Win32. What's the proper solution ? Use 'no-conversion ?

The problem is that XEmacs w/o mule checks coding system but does not
define escape-quoted. Is this a bug of XEmacs w/o mule?

If not, what variable indicates whether XEmacs has been compiled with
MULE support?

I guess enable-multibyte-characters is true, since gnus call
find-charset-region as you said in your message "find-charset-region".

-- 
Shenghuo

Re: escape-quoted

[Hrvoje Niksic]

Shenghuo ZHU <zsh@cs.rochester.edu> writes:

> >>>>> "FP" == Fabrice POPINEAU <popineau@ese-metz.fr> writes:
> 
> FP> This is the file coding system used by default on the latest
> FP> pgnus-0.6[1-3] versions for XEmacs, but it is not defined unless
> FP> XEmacs has been compiled with MULE support. Which is not the case
> FP> under Win32. What's the proper solution ? Use 'no-conversion ?
> 
> The problem is that XEmacs w/o mule checks coding system but does not
> define escape-quoted. Is this a bug of XEmacs w/o mule?

See my explanation on levels of file coding support.  I think that
it's not a bug for XEmacs with file coding (but not Mule) support to
not defined `escape-quoted'.

> If not, what variable indicates whether XEmacs has been compiled
> with MULE support?

(featurep 'mule)        ; non-nil if Mule is present

(featurep 'file-coding) ; non-nil if file coding is present

> I guess enable-multibyte-characters

That variable has no effect whatsoever in XEmacs.  It shouldn't even
be bound.  It should be exorcized, then burned, and then *really*
hurt.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
What is mind?  No matter.
What is matter?  Never mind.

Re: escape-quoted

[Shenghuo ZHU]

>>>>> "HN" == Hrvoje Niksic <hniksic@srce.hr> writes:
HN> 2) With file-coding.  This is done on MS Windows because of the
HN>    newline stuff.

With this configure, is enable-multibyte-characters set to true?

-- 
Shenghuo

Re: escape-quoted

[Andy Piper]

At 17:38 04/12/98 +0100, Hrvoje Niksic wrote:
>(featurep 'file-coding) ; non-nil if file coding is present

Which is also true for mule (i.e. mule and file-coding are not mutually
exclusive - mule is file-coding with multibyte and multilingual support).

andy
---------------------------------------------------------------------------
" .sigs are like your face - rarely seen by you and uglier than you think"
Dr Andy Piper, Technical Architect, Parallax Solutions Ltd
mail: andyp@parallax.co.uk web: www.parallax.co.uk/~andyp

Re: escape-quoted

[Hrvoje Niksic]

Shenghuo ZHU <zsh@cs.rochester.edu> writes:

> >>>>> "HN" == Hrvoje Niksic <hniksic@srce.hr> writes:
> HN> 2) With file-coding.  This is done on MS Windows because of the
> HN>    newline stuff.
> 
> With this configure, is enable-multibyte-characters set to true?

enable-multibyte-characters means NOTHING in XEmacs.  No such thing.
No such variable.

If you meant to ask: "with this configure, are characters allowed to
consist of more than one byte?", then the answer is no.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
I'm a Lisp variable -- bind me!

Re: escape-quoted

[Shenghuo ZHU]

Fri Dec  4 12:13:12 1998  Shenghuo ZHU  <zsh@cs.rochester.edu>

	* message.el (message-draft-coding-system): Fix for XEmacs-NT.
	* mm-util.el (mm-find-charset-region): Ditto.

-- 
Shenghuo

:- patch ------------------------------
--- message.el	1998/12/04 17:06:13	1.1
+++ message.el	1998/12/04 19:28:32
@@ -879,8 +879,12 @@
   "Coding system to encode outgoing mail.")
 
 (defvar message-draft-coding-system 
-  (if (string-match "XEmacs\\|Lucid" emacs-version)
-      'escape-quoted 'emacs-mule)
+  (cond 
+   ((not (fboundp 'coding-system-p)) nil)
+   ((coding-system-p 'emacs-mule) 'emacs-mule)
+   ((coding-system-p 'escape-quoted) 'escape-quoted)
+   ((coding-system-p 'no-conversion) 'no-conversion)
+   (t nil))
   "Coding system to compose mail.")
 
 (defvar message-default-charset 'iso-8859-1

--- mm-util.el	1998/12/04 17:12:48	1.1
+++ mm-util.el	1998/12/04 17:13:36
@@ -249,7 +249,8 @@
   "Return a list of charsets in the region."
   (cond
    ((and (boundp 'enable-multibyte-characters)
-	 enable-multibyte-characters)
+	 enable-multibyte-characters
+	 (fboundp 'find-charset-region))
     (find-charset-region b e))
    ((not (boundp 'current-language-environment))
     (save-excursion

Re: escape-quoted

[Martin Buchholz]

>>>>> "Fabrice" == Fabrice POPINEAU <popineau@ese-metz.fr> writes:

Fabrice> This is the file coding system used by default on the latest
Fabrice> pgnus-0.6[1-3] versions for XEmacs, but it is not defined unless
Fabrice> XEmacs has been compiled with MULE support. Which is not the case
Fabrice> under Win32. What's the proper solution ? Use 'no-conversion ?

Normally the only reason to use escape-quoted is because the source
file contains non-Latin-1 charactrers.  Even just a Japanese comment
or a bogus ESCAPE character will cause trouble.  There is no reason
why the gnus sources need to do that.

Martin

Re: escape-quoted

[Shenghuo ZHU]

>>>>> "Martin" == Martin Buchholz <martin@xemacs.org> writes:
>>>>> "Fabrice" == Fabrice POPINEAU <popineau@ese-metz.fr> writes:

Fabrice> This is the file coding system used by default on the latest
Fabrice> pgnus-0.6[1-3] versions for XEmacs, but it is not defined
Fabrice> unless XEmacs has been compiled with MULE support. Which is
Fabrice> not the case under Win32. What's the proper solution ? Use
Fabrice> 'no-conversion ?

Martin> Normally the only reason to use escape-quoted is because the
Martin> source file contains non-Latin-1 charactrers.  Even just a
Martin> Japanese comment or a bogus ESCAPE character will cause
Martin> trouble.  There is no reason why the gnus sources need to do
Martin> that.

The reason is to save an unsent (not encoded) message, which may
contain any kind of characters.

-- 
Shenghuo