unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: dashes and non-breaking spaces
Date: Sat, 15 Jan 2005 18:30:31 +0100	[thread overview]
Message-ID: <m3651yy4zs.fsf@seneca.benny.turtle-trading.net> (raw)
In-Reply-To: <shmzvak8kw.fsf@tux.gnu.franken.de> (Karl Eichwalder's message of "Sat, 15 Jan 2005 16:36:47 +0100")

Hi Karl,


> Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net> writes:
>> Those are not "escapes" strictly speaking.  If you decode UTF-8 as
>> cp1252 or latin-1 you just get sequences of unusual non-ASCII
>> characters.

Karl Eichwalder writes:
> The point is that Emacs treats them as escapes...

What does "escape" mean here?  There are no escapes of any kind in
latin-1 in the non-ASCII region, as I understand it.  If this is just
another term for "control character", the only valid control
character, if you want to call it that, is \u00A0, NBSP (see subject).

In email, if there are characters in a latin-1 text from the reserved
C1 region (\u0080-\u009F), that is just an indication that it's not
actually latin-1, but that windows-1252 (cp1252) is used.  That
confusion is extremely common.

If there are byte sequences in there that are valid in UTF-8, that
means that it *is* UTF-8 (with a very high degree of certainty).

> (And as I said, those messages are broken; only a part (the quoted
> text) is "wrong".)

Well, that could mean that the sender has seen it in this form and
wants you to see it this way.  Or it can mean that the sender was too
lazy to correct it.

If you wanted to fix it in Emacs, you'd have to treat each quoted
block separately.  The algorithm that I gave would still be
reasonable.


benny

  reply	other threads:[~2005-01-15 17:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-28 13:21 dashes and non-breaking spaces Paul Pogonyshev
2004-12-29 21:08 ` Stefan Monnier
2005-01-02 15:24   ` Paul Pogonyshev
2005-01-04 20:53   ` Karl Eichwalder
2005-01-05  5:46     ` Juri Linkov
2005-01-06  4:53       ` Richard Stallman
2005-01-12  2:02         ` Juri Linkov
2005-01-12  4:41           ` Miles Bader
2005-01-12  6:39             ` Karl Eichwalder
2005-01-12 20:58               ` Miles Bader
2005-01-12 21:58                 ` Stefan Monnier
2005-01-12 22:07                   ` Miles Bader
2005-01-12 22:30                     ` Stefan Monnier
2005-01-13  9:29                       ` David Kastrup
2005-01-13 10:37                         ` Miles Bader
2005-01-14 11:33                           ` Richard Stallman
2005-01-13 20:29               ` Richard Stallman
2005-01-13 21:11                 ` Karl Eichwalder
2005-01-13 21:24                   ` Stefan Monnier
2005-01-13 21:59                     ` Karl Eichwalder
2005-01-15  0:12                   ` Richard Stallman
2005-01-15  6:47                     ` Karl Eichwalder
2005-01-15 14:05                       ` Benjamin Riefenstahl
2005-01-15 15:36                         ` Karl Eichwalder
2005-01-15 17:30                           ` Benjamin Riefenstahl [this message]
2005-01-13 21:39                 ` Paul Pogonyshev
2005-01-15  0:12                   ` Richard Stallman
2005-01-07 13:59   ` Kim F. Storm
2005-01-07 23:04     ` Richard Stallman
2005-01-09  2:17       ` Kim F. Storm
2005-01-03  4:31 ` Richard Stallman

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=m3651yy4zs.fsf@seneca.benny.turtle-trading.net \
    --to=b.riefenstahl@turtle-trading.net \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).