all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Random832 <random832@fastmail.com>
To: emacs-devel@gnu.org
Subject: Re: Casting as wide a net as possible
Date: Tue, 15 Dec 2015 13:54:20 -0500	[thread overview]
Message-ID: <87poy7k0f7.fsf@fastmail.com> (raw)
In-Reply-To: m2oadr37jr.fsf@fastmail.fm

Filipp Gunbin <fgunbin@fastmail.fm> writes:
> I see.  However, this doesn't seem to affect English and American
> English languages, but rather European ones.

There are occasional accented words e.g. naïve, borrowed from
other languages. And also punctuation marks (more common with
people who use certain word processing software packages that
automatically replace typewriter quotes with them).

> Honestly, I always though that those languages do not have many
> encodings in use, probably I'm wrong.

Well, obviously there’s Latin-1 and UTF-8. There’s also
Windows-1252, which is semi-compatible with Latin-1. You can
sometimes end up with the Windows-1252 bytes treated as if they
were Latin-1 C1 controls (and perhaps encoded further into
UTF-8). There are also older encodings that aren’t used much
anymore e.g. DOS 437/850, MacRoman, etc.

I¹ve also seen content that was mechanically translated from one
to another using an 8-bit mapping table, with incompatible
characters mapped arbitrarily. For example, if you ever see
something with quotes/apostrophes replaced with superscripts,
like in this paragraph, this probably means the text originated
in MacRoman and was translated to Latin-1 with the ³André
Pirard² mapping.

Anyway, the point is, since non-ASCII characters aren’t
pervasive, it’s easy to miss noticing that something’s wrong
with them. For one last demo, this paragraph features UTF-8,
treated as Windows-1252, and then re-encoded as UTF-8 again.




  reply	other threads:[~2015-12-15 18:54 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
2015-12-14 18:19         ` Yuri Khan
2015-12-15 18:12           ` Filipp Gunbin
2015-12-15 18:54             ` Random832 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87poy7k0f7.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 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.