unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: coding problem char \217 etc
Date: Fri, 16 Nov 2018 17:05:22 +0200	[thread overview]
Message-ID: <8336s1ukp9.fsf@gnu.org> (raw)
In-Reply-To: <87ftw1t99r.fsf@mat.ucm.es> (message from Uwe Brauer on Fri, 16 Nov 2018 14:57:36 +0100)

> From: Uwe Brauer <oub@mat.ucm.es>
> Date: Fri, 16 Nov 2018 14:57:36 +0100
> 
> >From time to time I obtain documents which look like
> 
> \usepackage[latin1]{inputenc} 
>  \usepackage[T1]{fontenc}      % Police contenant les caractres franais
> \usepackage{geometry}         % DŽfinir les marges
> %  \usepackage[francais]{babel}  % Placez ici une liste de langues, la
>                               % dernire Žtant la langue principale
> 
> % \pagestyle{headings}        % Pour mettre des enttes avec les titres
>                               % des subsections en haut de page
> 
> 
> Since I am not sure that the coding survives I write that as
> 
> \usepackage[latin1]{inputenc} 
>  \usepackage[T1]{fontenc}      % Police contenant les caract\217res fran\215ais
> \usepackage{geometry}         % D\216finir les marges
> %  \usepackage[francais]{babel}  % Placez ici une liste de langues, la
>                               % derni\217re \216tant la langue principale
> 
> % \pagestyle{headings}        % Pour mettre des ent\220tes avec les titres
>                               % des subsections en haut de page
> 
> 
> And I simple don't know who to deal with it

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

> Any possibility how emacs could deal with this automatically?

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.



  parent reply	other threads:[~2018-11-16 15:05 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8336s1ukp9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=oub@mat.ucm.es \
    /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 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).