* escape-quoted @ 1998-12-04 8:56 ` Fabrice POPINEAU 1998-12-04 9:37 ` escape-quoted Andy Piper ` (3 more replies) 0 siblings, 4 replies; 12+ messages in thread From: Fabrice POPINEAU @ 1998-12-04 8:56 UTC (permalink / raw) 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: escape-quoted 1998-12-04 8:56 ` escape-quoted Fabrice POPINEAU @ 1998-12-04 9:37 ` Andy Piper 1998-12-04 20:16 ` escape-quoted Shenghuo ZHU 1998-12-04 14:34 ` escape-quoted Lars Magne Ingebrigtsen ` (2 subsequent siblings) 3 siblings, 1 reply; 12+ messages in thread From: Andy Piper @ 1998-12-04 9:37 UTC (permalink / raw) 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: escape-quoted 1998-12-04 9:37 ` escape-quoted Andy Piper @ 1998-12-04 20:16 ` Shenghuo ZHU 0 siblings, 0 replies; 12+ messages in thread From: Shenghuo ZHU @ 1998-12-04 20:16 UTC (permalink / raw) 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: escape-quoted 1998-12-04 8:56 ` escape-quoted Fabrice POPINEAU 1998-12-04 9:37 ` escape-quoted Andy Piper @ 1998-12-04 14:34 ` Lars Magne Ingebrigtsen 1998-12-04 15:45 ` escape-quoted Hrvoje Niksic 1998-12-04 16:31 ` escape-quoted Shenghuo ZHU 1998-12-04 22:30 ` escape-quoted Martin Buchholz 3 siblings, 1 reply; 12+ messages in thread From: Lars Magne Ingebrigtsen @ 1998-12-04 14:34 UTC (permalink / raw) 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: escape-quoted 1998-12-04 14:34 ` escape-quoted Lars Magne Ingebrigtsen @ 1998-12-04 15:45 ` Hrvoje Niksic 1998-12-04 16:38 ` escape-quoted Shenghuo ZHU 0 siblings, 1 reply; 12+ messages in thread From: Hrvoje Niksic @ 1998-12-04 15:45 UTC (permalink / raw) 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. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: escape-quoted 1998-12-04 15:45 ` escape-quoted Hrvoje Niksic @ 1998-12-04 16:38 ` Shenghuo ZHU 1998-12-04 18:16 ` escape-quoted Hrvoje Niksic 0 siblings, 1 reply; 12+ messages in thread From: Shenghuo ZHU @ 1998-12-04 16:38 UTC (permalink / raw) >>>>> "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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: escape-quoted 1998-12-04 16:38 ` escape-quoted Shenghuo ZHU @ 1998-12-04 18:16 ` Hrvoje Niksic 0 siblings, 0 replies; 12+ messages in thread From: Hrvoje Niksic @ 1998-12-04 18:16 UTC (permalink / raw) 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! ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: escape-quoted 1998-12-04 8:56 ` escape-quoted Fabrice POPINEAU 1998-12-04 9:37 ` escape-quoted Andy Piper 1998-12-04 14:34 ` escape-quoted Lars Magne Ingebrigtsen @ 1998-12-04 16:31 ` Shenghuo ZHU 1998-12-04 16:38 ` escape-quoted Hrvoje Niksic 1998-12-04 22:30 ` escape-quoted Martin Buchholz 3 siblings, 1 reply; 12+ messages in thread From: Shenghuo ZHU @ 1998-12-04 16:31 UTC (permalink / raw) >>>>> "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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: escape-quoted 1998-12-04 16:31 ` escape-quoted Shenghuo ZHU @ 1998-12-04 16:38 ` Hrvoje Niksic 1998-12-04 16:50 ` escape-quoted Andy Piper 0 siblings, 1 reply; 12+ messages in thread From: Hrvoje Niksic @ 1998-12-04 16:38 UTC (permalink / raw) Cc: ding, xemacs-nt 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. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: escape-quoted 1998-12-04 16:38 ` escape-quoted Hrvoje Niksic @ 1998-12-04 16:50 ` Andy Piper 0 siblings, 0 replies; 12+ messages in thread From: Andy Piper @ 1998-12-04 16:50 UTC (permalink / raw) Cc: ding, xemacs-nt 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: escape-quoted 1998-12-04 8:56 ` escape-quoted Fabrice POPINEAU ` (2 preceding siblings ...) 1998-12-04 16:31 ` escape-quoted Shenghuo ZHU @ 1998-12-04 22:30 ` Martin Buchholz 1998-12-05 22:50 ` escape-quoted Shenghuo ZHU 3 siblings, 1 reply; 12+ messages in thread From: Martin Buchholz @ 1998-12-04 22:30 UTC (permalink / raw) Cc: ding, xemacs-nt >>>>> "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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: escape-quoted 1998-12-04 22:30 ` escape-quoted Martin Buchholz @ 1998-12-05 22:50 ` Shenghuo ZHU 0 siblings, 0 replies; 12+ messages in thread From: Shenghuo ZHU @ 1998-12-05 22:50 UTC (permalink / raw) >>>>> "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 ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~1998-12-05 22:50 UTC | newest] Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [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 ` escape-quoted Hrvoje Niksic 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
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).