Re: iso-8859-1 and non-latin-1 chars

[Kenichi Handa <handa@m17n.org>]

In article <200211071706.gA7H6hW09141@rum.cs.yale.edu>, "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:

>>  > When encoding text containing non-latin-1 chars with the latin-1
>>  > coding-system, they get output as some kind of escape sequence.
>>  
>>  Yes.  IIRC, this is hard-coded in the encoder's C code: it works as if
>>  latin-1 was actually iso-latin-1-wth-esc.

> How can we change that ?

This change will do.

*** european.el.~1.75.~	Wed Nov  6 09:13:16 2002
--- european.el	Fri Nov  8 08:32:12 2002
***************
*** 36,42 ****
   'iso-latin-1 2 ?1
   "ISO 2022 based 8-bit encoding for Latin-1 (MIME:ISO-8859-1)."
   '(ascii latin-iso8859-1 nil nil
!    nil nil nil nil nil nil nil nil nil nil nil nil t)
   '((safe-charsets ascii latin-iso8859-1)
     (mime-charset . iso-8859-1)))
  
--- 36,42 ----
   'iso-latin-1 2 ?1
   "ISO 2022 based 8-bit encoding for Latin-1 (MIME:ISO-8859-1)."
   '(ascii latin-iso8859-1 nil nil
!    nil nil nil nil nil nil nil nil nil nil nil t t)
   '((safe-charsets ascii latin-iso8859-1)
     (mime-charset . iso-8859-1)))
  
Or, if this is a problem only for ispell, we can make series
of "safe" coding-systems for ispell.

Or, we can add a global flag, say
`inhibit-unsafe-iso-escape, to tell encoding routine not to
produces those escape sequences.  Then, ispell can let-bind
that variable to t on encoding.

I think the last one is the best solution.

What do you think?

---
Ken'ichi HANDA
handa@m17n.org