From: Ivan Shmakov <ivan@siamics.net>
To: 18610@debbugs.gnu.org
Subject: bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening
Date: Tue, 07 Oct 2014 13:20:03 +0000 [thread overview]
Message-ID: <874mvg5858.fsf@violet.siamics.net> (raw)
In-Reply-To: <877g0ct5xb.fsf@gnu.org> (K. Handa's message of "Tue, 07 Oct 2014 21:34:08 +0900")
>>>>> 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
next prev parent reply other threads:[~2014-10-07 13:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 14:50 bug#18610: 24.4.50; Specific file causing emacs to segfault upon opening maden.ldm
2014-10-02 15:40 ` Nicolas Richard
2014-10-03 8:14 ` Eli Zaretskii
2014-10-03 11:22 ` Dmitry Antipov
2014-10-03 12:20 ` Eli Zaretskii
2014-10-03 12:39 ` Eli Zaretskii
2014-10-03 15:16 ` Andreas Schwab
2014-10-03 15:32 ` Eli Zaretskii
2014-10-03 16:02 ` Andreas Schwab
2014-10-03 16:35 ` Eli Zaretskii
2014-10-03 16:40 ` Andreas Schwab
2014-10-03 16:57 ` Eli Zaretskii
2014-10-05 8:59 ` K. Handa
2014-10-05 16:09 ` Eli Zaretskii
2014-10-06 14:00 ` K. Handa
2014-10-06 15:20 ` Eli Zaretskii
2014-10-07 12:34 ` K. Handa
2014-10-07 13:20 ` Ivan Shmakov [this message]
2014-10-07 14:33 ` Eli Zaretskii
2014-10-07 15:10 ` Ivan Shmakov
2014-10-07 15:19 ` Eli Zaretskii
2014-10-08 7:33 ` Eli Zaretskii
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=874mvg5858.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=18610@debbugs.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.