foreign characters

foreign characters

[prad]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1270 bytes --]

sometimes people send me stuff with characters in different languages
which show up like \351 (acute e), from evil windoze systems.

when i save the file, emacs says that these items are not encodable
with message like this:

====
These default coding systems were tried to encode text
in the buffer `tmp.html':
  (utf-8-unix (3464 . 4194181) (6020 . 4194281) (14957 . 4194181)
  (15010 . 4194181) (16070 . 4194181) (16310 . 4194181) (16363
  . 4194181) (16659 . 4194181) (18246 . 4194181) (18988 . 4194181)
  (19990 . 4194193))
However, each of them encountered characters it couldn't encode:
  utf-8-unix cannot encode these: … é … … … … … … … … ...

Click on a character (or switch to this window by `M-x other-window'
and select the characters by RET) to jump to the place it appears,
where `C-u C-x =' will give information about it.

Select one of the safe coding systems listed below,
or cancel the writing with C-g and edit the buffer
====

so if i push tab a whole list of different languages coding systems come
up. i tried picking mule-unix one, but the character still stays as \351
or \205 or whatever (though the file saves).

what can i do to have emacs substitute the correct letter representation
instead of looking at \351?

-- 
in friendship,
prad

Re: foreign characters

[Pascal J. Bourguignon]

prad <prad@towardsfreedom.com> writes:

> what can i do to have emacs substitute the correct letter representation
> instead of looking at \351?

1- ask the remote to send you UTF-8.  It's the de-facto norm.

2.1- save the file as raw-text: C-x RET c raw-text reT C-x C-w file.txt RET
2.2- kill the buffer. C-x k
2.3- open the file in the right encoding: C-x RET c RIGHT-ENCODING C-x C-f file.txt RET

Now the problem of course is to know what's the right encoding! :-)
There are a lot of encodings where \351 <-> é.  But you may try
iso-8859-1 to start with.  (That said they don't use iso-8859-1 on
MS-Windows).


-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

Re: foreign characters

[Peter Dyballa]

Am 07.05.2012 um 23:08 schrieb prad:

> what can i do to have emacs substitute the correct letter representation
> instead of looking at \351?

Save in ISO Latin-1 (-2, -3, -4, -10, -13, 14, -15, -16) or in MS Losedos Code Pages 1250 or 1252. 

--
Greetings

  Pete       (:
        _    / __    -    -
      _/ \__/_/        -     -
     (´`)      (´`)   -    -
      `´        `´

Re: foreign characters

[prad]

"Pascal J. Bourguignon" <pjb@informatimago.com> writes:

> prad <prad@towardsfreedom.com> writes:
>
>> what can i do to have emacs substitute the correct letter representation
>> instead of looking at \351?
>
> 1- ask the remote to send you UTF-8.  It's the de-facto norm.
>
> 2.1- save the file as raw-text: C-x RET c raw-text reT C-x C-w file.txt RET
> 2.2- kill the buffer. C-x k
> 2.3- open the file in the right encoding: C-x RET c RIGHT-ENCODING C-x C-f file.txt RET
>
> Now the problem of course is to know what's the right encoding! :-)
> There are a lot of encodings where \351 <-> é.  But you may try
> iso-8859-1 to start with.  (That said they don't use iso-8859-1 on
> MS-Windows).
>
thx for all this pascal! i didn't know about any of this stuff.
thx to you too peter because i tried some of the encoding you'd sent as
well as what's above.

so i'm in much better shape now and am understanding this area more than
i did before.

-- 
in friendship,
prad

Re: foreign characters

[Oleksandr Gavenko]

On 2012-05-08, prad wrote:

> "Pascal J. Bourguignon" <pjb@informatimago.com> writes:
>
>> prad <prad@towardsfreedom.com> writes:
>>
>>> what can i do to have emacs substitute the correct letter representation
>>> instead of looking at \351?
>>
>> 1- ask the remote to send you UTF-8.  It's the de-facto norm.
>>
>> 2.1- save the file as raw-text: C-x RET c raw-text reT C-x C-w file.txt RET
>> 2.2- kill the buffer. C-x k
>> 2.3- open the file in the right encoding: C-x RET c RIGHT-ENCODING C-x C-f file.txt RET
>>
>> Now the problem of course is to know what's the right encoding! :-)
>> There are a lot of encodings where \351 <-> é.  But you may try
>> iso-8859-1 to start with.  (That said they don't use iso-8859-1 on
>> MS-Windows).
>>
> thx for all this pascal! i didn't know about any of this stuff.
> thx to you too peter because i tried some of the encoding you'd sent as
> well as what's above.
>
> so i'm in much better shape now and am understanding this area more than
> i did before.

Don't forget C-x RET C-r (for reread file with different coding system) and
M-x recode-region.

-- 
Best regards!