unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Misformatted replies to UTF-8 messages
@ 2002-02-25 13:38 ShengHuo ZHU
  2002-02-25 16:21 ` Eli Zaretskii
  0 siblings, 1 reply; 4+ messages in thread
From: ShengHuo ZHU @ 2002-02-25 13:38 UTC (permalink / raw)



I received a bug report in Emacs 21.1.95 which is because
find-coding-systems-region prefer ctext-no-compositions to mule-utf-8,
e.g.  the following lines return ctext-no-compositions.

  (car (find-coding-systems-string
       (concat (char-to-string 2276) (char-to-string 2367))))

I think it has been fixed in the main branch. Could the fix be ported
to EMACS_21_1_RC?  Also, please send the patch to Arkadiusz Miskiewicz
<misiek@pld.ORG.PL> , who will apply it to PLD package of emacs.

ShengHuo

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Misformatted replies to UTF-8 messages
  2002-02-25 13:38 Misformatted replies to UTF-8 messages ShengHuo ZHU
@ 2002-02-25 16:21 ` Eli Zaretskii
  2002-02-25 18:08   ` ShengHuo ZHU
  0 siblings, 1 reply; 4+ messages in thread
From: Eli Zaretskii @ 2002-02-25 16:21 UTC (permalink / raw)
  Cc: emacs-devel

This is off the top of my head, before I had time to step through the 
code.

On Mon, 25 Feb 2002, ShengHuo ZHU wrote:

> I received a bug report in Emacs 21.1.95 which is because
> find-coding-systems-region prefer ctext-no-compositions to mule-utf-8,
> e.g.  the following lines return ctext-no-compositions.
> 
>   (car (find-coding-systems-string
>        (concat (char-to-string 2276) (char-to-string 2367))))

Why is this regarded as a bug?  UTF-8 is generally very low on the 
priority list of the possible encodings, so IIRC the user needs to invoke 
prefer-coding-system to get UTF.  If she doesn't, almost any other 
encoding will be preferred to UTF-8.

Is this some language environment that is already supposed to prefer 
UTF-8?  If so, could the user who saw the problem please submit a full
bug  report with the necessary info supplied by "M-x report-emacs-bug"?

> I think it has been fixed in the main branch. Could the fix be ported
> to EMACS_21_1_RC?

If the problem doesn't exist in CVS head, it's by sheer luck, because 
IIRC the definition of ctext-no-compositions is identical in both 
branches.

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Misformatted replies to UTF-8 messages
  2002-02-25 16:21 ` Eli Zaretskii
@ 2002-02-25 18:08   ` ShengHuo ZHU
  2002-02-25 19:41     ` Eli Zaretskii
  0 siblings, 1 reply; 4+ messages in thread
From: ShengHuo ZHU @ 2002-02-25 18:08 UTC (permalink / raw)
  Cc: emacs-devel

Eli Zaretskii <eliz@is.elta.co.il> writes:

> This is off the top of my head, before I had time to step through the 
> code.
>
> On Mon, 25 Feb 2002, ShengHuo ZHU wrote:
>
>> I received a bug report in Emacs 21.1.95 which is because
>> find-coding-systems-region prefer ctext-no-compositions to mule-utf-8,
>> e.g.  the following lines return ctext-no-compositions.
>> 
>>   (car (find-coding-systems-string
>>        (concat (char-to-string 2276) (char-to-string 2367))))
>
> Why is this regarded as a bug?  UTF-8 is generally very low on the 
> priority list of the possible encodings, so IIRC the user needs to invoke 
> prefer-coding-system to get UTF.  If she doesn't, almost any other 
> encoding will be preferred to UTF-8.

Because I saw it before in the Emacs main branch and later it returns
mule-utf-8.

> Is this some language environment that is already supposed to prefer 
> UTF-8?  If so, could the user who saw the problem please submit a full
> bug  report with the necessary info supplied by "M-x report-emacs-bug"?

I've asked the user to submit the bug report.

>> I think it has been fixed in the main branch. Could the fix be ported
>> to EMACS_21_1_RC?
>
> If the problem doesn't exist in CVS head, it's by sheer luck, because 
> IIRC the definition of ctext-no-compositions is identical in both 
> branches.

But the definition of utf-8 is changed, probably in Dave Love's
2001-12-18, -15, -07 changes.

ShengHuo

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Misformatted replies to UTF-8 messages
  2002-02-25 18:08   ` ShengHuo ZHU
@ 2002-02-25 19:41     ` Eli Zaretskii
  0 siblings, 0 replies; 4+ messages in thread
From: Eli Zaretskii @ 2002-02-25 19:41 UTC (permalink / raw)
  Cc: emacs-devel

> From: ShengHuo ZHU <zsh@cs.rochester.edu>
> Date: Mon, 25 Feb 2002 13:08:01 -0500
> 
> > Why is this regarded as a bug?  UTF-8 is generally very low on the 
> > priority list of the possible encodings, so IIRC the user needs to
> > invoke 
> > prefer-coding-system to get UTF.  If she doesn't, almost any other 
> > encoding will be preferred to UTF-8.
> 
> Because I saw it before in the Emacs main branch and later it
> returns mule-utf-8.

Ah, I think that's because the CVS head has a different priority list.

> I've asked the user to submit the bug report.

Thank you.

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-02-25 19:41 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-02-25 13:38 Misformatted replies to UTF-8 messages ShengHuo ZHU
2002-02-25 16:21 ` Eli Zaretskii
2002-02-25 18:08   ` ShengHuo ZHU
2002-02-25 19:41     ` Eli Zaretskii

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).