From: Random832 <random832@fastmail.com>
To: emacs-devel@gnu.org
Subject: Re: Casting as wide a net as possible
Date: Mon, 14 Dec 2015 12:59:10 -0500 [thread overview]
Message-ID: <87zixcud1t.fsf@fastmail.com> (raw)
In-Reply-To: m2poy93q28.fsf@fastmail.fm
Filipp Gunbin <fgunbin@fastmail.fm> writes:
> On 14/12/2015 21:01 +0600, Yuri Khan wrote:
>> On Mon, Dec 14, 2015 at 8:41 PM, Filipp Gunbin <fgunbin@fastmail.fm> wrote:
>>> When I started using Emacs, it attracted me with the ease of working
>>> with codings. I've tried some editors at that time, of course
>>> (including well-known IDEs, for years), but never before it was so easy
>>> to just open a file in a given coding, or re-open it in another. We,
>>> non-English-natives, still have problems with different encodings (yes,
>>> KOI8-R, CP-1251 and CP-866 for Russian are still here) and Emacs helped
>>> me to learn more clearly what the encoding is.
>>
>> English natives have worse problems with encodings.
>
> What do you mean? Just interesting.
The definition of "worse" is subjective, but I think what he's
referring to is the fact that someone might open a file in the
wrong encoding, without noticing or caring that some accented
word or punctuation symbol in some paragraph deep within the
file looks wrong, add more content in the new encoding, save
it... then you have a file which has a mixture of bytes in
different encodings, which is very difficult to fix
automatically.
Whereas, if you open a file in Cyrillic (or, say, Japanese), you
know immediately that it's in the wrong encoding and won't do
any editing until the coding situation is fixed.
next prev parent reply other threads:[~2015-12-14 17:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 16:46 Casting as wide a net as possible (was: First draft of the Emacs website) John Yates
2015-12-10 17:31 ` Eli Zaretskii
2015-12-10 18:56 ` Drew Adams
2015-12-10 19:02 ` Casting as wide a net as possible John Wiegley
2015-12-10 19:07 ` Eli Zaretskii
2015-12-10 19:48 ` David Kastrup
2015-12-10 20:01 ` Eli Zaretskii
2015-12-10 20:17 ` David Kastrup
2015-12-10 20:19 ` John Wiegley
2015-12-10 20:50 ` David Kastrup
2015-12-11 7:09 ` Richard Stallman
2015-12-10 19:54 ` covici
2015-12-10 21:21 ` Marcin Borkowski
2015-12-14 13:05 ` Adrian.B.Robert
2015-12-14 16:21 ` raman
2015-12-14 18:21 ` John Wiegley
2015-12-11 7:08 ` Casting as wide a net as possible (was: First draft of the Emacs website) Richard Stallman
2015-12-11 16:14 ` Casting as wide a net as possible raman
2015-12-14 14:41 ` Filipp Gunbin
2015-12-14 15:01 ` Yuri Khan
2015-12-14 17:20 ` Filipp Gunbin
2015-12-14 17:59 ` Random832 [this message]
2015-12-14 18:19 ` Yuri Khan
2015-12-15 18:12 ` Filipp Gunbin
2015-12-15 18:54 ` Random832
2015-12-15 19:03 ` Random832
[not found] <<CAJnXXogJywM4xRM9OEF1RKEwOib_G_JJvj=YThhsUwFn6gHviQ@mail.gmail.com>
[not found] ` <<fa45f69a-b8df-46f8-8fda-4735dc34e4dc@default>
[not found] ` <<m2d1uenn4h.fsf@newartisans.com>
[not found] ` <<83a8pi9l6o.fsf@gnu.org>
2015-12-10 19:15 ` Drew Adams
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=87zixcud1t.fsf@fastmail.com \
--to=random832@fastmail.com \
--cc=emacs-devel@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 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).