[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: coding problem char \217 etc
From: |
Uwe Brauer |
Subject: |
Re: coding problem char \217 etc |
Date: |
Fri, 16 Nov 2018 16:58:00 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
>>> "Stefan" == Stefan Monnier <address@hidden> writes:
>> 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).
Yes I know, I tried to delete this line and reopen the file but it did
not help. That is why I asked for the coding. Eli guessed it correctly
and I still don't know how he did it....
Uwe
smime.p7s
Description: S/MIME cryptographic signature
- 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, 2018/11/16
- Re: coding problem char \217 etc,
Uwe Brauer <=
- 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