still codings problem (saving) with babel.

[Uwe Brauer]

>> On Mon, 12 Dec 2011 17:53:21 +0000, Aidan Kehoe <kehoea at parhasard.net> wrote:

   >  Ar an triú lá déag de mí na Nollaig, scríobh Stephen J. Turnbull: 

   >> Uwe Brauer writes:
   >> 
   >> > Char: é (U+2000E9 jit-ucs-charset-0 35 56) point=467 of 473(99%) column 2 
   >> 
   >> Maybe Aidan can explain what looks like a Latin-1 character is being
   >> stuffed into a jit-ucs charset. 

   > This is what happens when Latin-1 is decoded as UTF-8, since I changed the
   > UTF-8 coding systems to avoid transforming every octet that is not valid
   > UTF-8 to tilde. Basically, babel (or more probably, the URL-retrieval code)
   > isn’t looking at the MIME information about what coding system the data is
   > in at all.

What I found strange is: when this char  is in the buffer
and the other chars are ascii, then saving to UTF-8 works
correctly.

However if the other chars are latin-1  the trouble starts. 

There are two solutions

    -  Use the function steve sent me.

    -  Change babel.el:

Change 
	    (decode-coding-region (point-min) (point-max) 'utf-8)
to
	    (decode-coding-region (point-min) (point-max) 'latin-1)

I am not sure what is better.


BTW, what is the difference between decode-coding-region and
mm-decode-coding-region?


Uwe 

PS this was the first email of yours whose chars were
displayed correctly in Xemacs and seamonkey but not in my
Ipod touch..... :-(