unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Karl Eichwalder <ke@gnu.franken.de>
Cc: juri@jurta.org, snogglethorpe@gmail.com, emacs-devel@gnu.org,
	monnier@iro.umontreal.ca, miles@gnu.org
Subject: Re: dashes and non-breaking spaces
Date: Thu, 13 Jan 2005 22:11:17 +0100	[thread overview]
Message-ID: <shwtuhkpai.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <E1CpBbQ-0007Yz-V0@fencepost.gnu.org> (Richard Stallman's message of "Thu, 13 Jan 2005 15:29:56 -0500")

Richard Stallman <rms@gnu.org> writes:

> The word "must" makes this statement so strong that it surprises me.
> Why do you think this is such a great problem?

I often receive broken UTF-8 messages.  People quote UTF-8 texts with
German "umlauts" and treat these texts as iso-8859-1 encoded resulting
in escapes instead of 'ß', for example:

    > 'Die Stadt heiÃ\237t "Lutherstadt Wittenberg".'
                 heißt (corrected)

"\237" and some other escapes can often occur and then the text is
disturbed with many blue fragments.

Messages written in French often contain non-breaking spaces
intentionally and legitimately; adding a special marker to them destroys
the text (Stefan Monnier explained it in a previous message).

-- 
http://www.gnu.franken.de/ke/                           |      ,__o
                                                        |    _-\_<,
                                                        |   (*)/'(*)
Key fingerprint = F138 B28F B7ED E0AC 1AB4  AA7F C90A 35C3 E9D0 5D1C

  reply	other threads:[~2005-01-13 21:11 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 [this message]
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
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=shwtuhkpai.fsf@tux.gnu.franken.de \
    --to=ke@gnu.franken.de \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=miles@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=snogglethorpe@gmail.com \
    /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).