From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: coding problem char \217 etc
Date: Fri, 16 Nov 2018 16:36:01 +0100 [thread overview]
Message-ID: <877ehdt4pq.fsf@mat.ucm.es> (raw)
In-Reply-To: 8336s1ukp9.fsf@gnu.org
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
> You need to tell Emacs to read the file with the correct decoding. In
> this case, I think this will do the trick:
> C-x RET c mac-roman RET C-x C-f FILE-NAME RET
That worked thank you!
1. You did you guess mac-roman? How can I find out myself in the future?
2. Is there any faster possibility? I tried out
(set-buffer-file-coding-system 'mac nil) but this did not work,
also there I did not find mac-roman as a coding system.
> Maybe. It depends on your locale defaults and on whether you
> customized those defaults (with the likes of prefer-coding-system).
> Not every encoding can be reliably decoded, if the defaults defeat
> that.
> One way of avoiding the manual specification of the encoding is to use
> the coding: tag inside the file, either on the first line or in the
> file-local variables.
That is what I usually do, but a tag in the first line but if I receive
a file whose coding I don't know and don't know how to find it out, I am
sort of stuck.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5025 bytes --]
next prev parent reply other threads:[~2018-11-16 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 13:57 coding problem char \217 etc Uwe Brauer
2018-11-16 14:28 ` Andreas Schwab
2018-11-16 15:36 ` Uwe Brauer
2018-11-16 15:46 ` Andreas Schwab
2018-11-16 15:05 ` Eli Zaretskii
2018-11-16 15:22 ` Eli Zaretskii
2018-11-16 15:33 ` Stefan Monnier
2018-11-16 15:58 ` Uwe Brauer
2018-11-16 15:36 ` Uwe Brauer [this message]
2018-11-16 15:53 ` Eli Zaretskii
2018-11-16 16:00 ` Uwe Brauer
2018-11-16 16:08 ` Eli Zaretskii
2018-11-16 16:31 ` Uwe Brauer
2018-11-16 16:35 ` Uwe Brauer
2018-11-16 17:23 ` Eli Zaretskii
2018-11-20 19:30 ` Charles A. Roelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ehdt4pq.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.