[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening
From: |
Ivan Shmakov |
Subject: |
bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening |
Date: |
Tue, 07 Oct 2014 13:20:03 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
>>>>> K Handa <handa@gnu.org> writes:
>>>>> In article <83egulmdhz.fsf@gnu.org>, Eli Zaretskii writes:
[…]
>> Yes, but what's the reason for having latin-extra-code-table in the
>> first place?
> I vaguely remember that it was a request from latin-1 users who
> occasionally have to edit files created by Windows users, and those
> files tend to contain those non-Latin-1 characters.
Specifically, latin-extra-code-table has non-nil elements at
indices #x91 through #x96, which are, as it seems, windows-1252
code points for the characters common to English typography [1]
(specifically: ‘, ’, “, ”, •, and –; or U+2018, U+2019, U+201C,
U+201D, U+2022, U+2013.)
ISO-8859-1 /proper/ uses these code points for C1 controls;
specifically [2]: Private Use 1 (PU1), Private Use 2 (PU2), Set
Transmit State (STS), Cancel character (CCH), Message Waiting
(MW), and Start of Protected Area (SPA). Which (I believe) are
unlikely to be produced by the “common” Windows software.
Thus, just using the windows-1252 encoding (perhaps also as a
default fallback in Latin-1 environments) looks like a cleaner
solution to me.
[1] https://en.wikipedia.org/wiki/Windows-1252
[2] https://en.wikipedia.org/wiki/C0_and_C1_control_codes
[…]
>>> Sorry for the poor comments in my code. I'll work on it soon.
>> TIA.
> http://en.wikipedia.org/wiki/TiA ? :-p
https://en.wiktionary.org/wiki/TIA
(Sorry, just couldn’t resist.)
[…]
--
FSF associate member #7257 np. Symphonic Dances Op. 64 — Edvard Grieg
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, (continued)
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, Eli Zaretskii, 2014/10/03
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, Andreas Schwab, 2014/10/03
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, Eli Zaretskii, 2014/10/03
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, Andreas Schwab, 2014/10/03
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, Eli Zaretskii, 2014/10/03
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, K. Handa, 2014/10/05
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, Eli Zaretskii, 2014/10/05
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, K. Handa, 2014/10/06
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, Eli Zaretskii, 2014/10/06
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, K. Handa, 2014/10/07
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening,
Ivan Shmakov <=
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, Eli Zaretskii, 2014/10/07
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, Ivan Shmakov, 2014/10/07
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, Eli Zaretskii, 2014/10/07
- bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening, Eli Zaretskii, 2014/10/08