[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: coding problem char \217 etc
From: |
Stefan Monnier |
Subject: |
Re: coding problem char \217 etc |
Date: |
Fri, 16 Nov 2018 10:33:17 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
> 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.
Note that in his examples he has:
\usepackage[latin1]{inputenc}
which Emacs normally recognizes the indicate that the file uses latin-1
(which is actually a lie in this case, tho that lie might only affect
comments, so it's not a complete lie).
Nowadays, the better bet is to use utf-8 (which is is much easier to
auto-detect and doesn't have umpteen extensions like latin-1 has).
Stefan
- coding problem char \217 etc, Uwe Brauer, 2018/11/16
- Re: coding problem char \217 etc, Andreas Schwab, 2018/11/16
- Re: coding problem char \217 etc, Eli Zaretskii, 2018/11/16
- Re: coding problem char \217 etc, Eli Zaretskii, 2018/11/16
- Re: coding problem char \217 etc,
Stefan Monnier <=
- Re: coding problem char \217 etc, Uwe Brauer, 2018/11/16
- Re: coding problem char \217 etc, Eli Zaretskii, 2018/11/16
- Re: coding problem char \217 etc, Uwe Brauer, 2018/11/16
- Re: coding problem char \217 etc, Eli Zaretskii, 2018/11/16
- Re: coding problem char \217 etc, Uwe Brauer, 2018/11/16
- Re: coding problem char \217 etc, Uwe Brauer, 2018/11/16
- Re: coding problem char \217 etc, Eli Zaretskii, 2018/11/16
- Re: coding problem char \217 etc, Charles A. Roelli, 2018/11/20