From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Daniel Ortmann Newsgroups: gmane.emacs.bugs Subject: html / emacs / email / gnus: 0xa0 classified as "whitespace" but not treated as whitespace Date: 19 Oct 2004 16:37:25 -0500 Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1098221886 2250 80.91.229.6 (19 Oct 2004 21:38:06 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 19 Oct 2004 21:38:06 +0000 (UTC) Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Oct 19 23:37:44 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CK1fr-0008Mg-00 for ; Tue, 19 Oct 2004 23:37:44 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CK1nC-00077G-9I for geb-bug-gnu-emacs@m.gmane.org; Tue, 19 Oct 2004 17:45:18 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CK1n9-00076b-8u for bug-gnu-emacs@gnu.org; Tue, 19 Oct 2004 17:45:15 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CK1n8-00075L-Al for bug-gnu-emacs@gnu.org; Tue, 19 Oct 2004 17:45:14 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CK1n7-00075C-U9 for bug-gnu-emacs@gnu.org; Tue, 19 Oct 2004 17:45:14 -0400 Original-Received: from [147.145.40.20] (helo=mail0.lsil.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CK1fi-0000YB-EG for bug-gnu-emacs@gnu.org; Tue, 19 Oct 2004 17:37:34 -0400 Original-Received: from milmhbs0.lsil.com (mhbs.lsil.com [147.145.1.30]) by mail0.lsil.com (8.12.8/8.12.8) with ESMTP id i9JLa6cq022067 for ; Tue, 19 Oct 2004 14:36:06 -0700 (PDT) Original-Received: from rm10.lsil.com (rm10.lsil.com [147.145.140.210]) by milmhbs0.lsil.com (8.12.11/8.12.11) with ESMTP id i9JLbS1m021799 for ; Tue, 19 Oct 2004 14:37:29 -0700 Original-Received: from localhost (rm140pc119 [147.145.140.119]) by rm10.lsil.com (8.11.6+Sun/8.10.2) with ESMTP id i9JLbPK15081 for ; Tue, 19 Oct 2004 16:37:28 -0500 (CDT) Original-Received: from dortmann by localhost with local (Exim 4.34) id 1CK1fZ-0008RA-7e for bug-gnu-emacs@gnu.org; Tue, 19 Oct 2004 16:37:25 -0500 Original-To: bug-gnu-emacs@gnu.org In-Reply-To: Original-Lines: 53 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 X-Scanned-By: MIMEDefang 2.39 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.bugs:9373 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:9373 Correction, 0xa0 should actually be treated as whitespace but is not. I.e. fill-paragraph and friends don't treat it as whitespace: Here is what describe-char-after says: -------------------------------- character: =A0 (04240, 2208, 0x8a0) charset: latin-iso8859-1 (Right-Hand Part of Latin Alphabet 1 (ISO/IEC = 8859-1): ISO-IR-100) code point: 32 syntax: whitespace category: :This character counts as a space for indentation purposes. = l:Latin=20=20 buffer code: 0x81 0xA0 file code: not encodable by coding system nil font: -Misc-Fixed-Medium-R-SemiCondensed--13-120-75-75-C-60-ISO8859-1 -------------------------------- I use the following routine to fix them up: (defun 0xa0-clean () (interactive) (query-replace-regexp "\240" " ")) Any hint as to where the problem might be? I suspect it's a simple fix. Daniel Ortmann writes: > Lars Magne Ingebrigtsen writes: >=20 > > Daniel Ortmann writes: > >=20 > > > Many emails are now using 0xa0 as a newline character (at least as > > > rendered by w3 under gnus and as sent by messages using "R" for > > > Reply). Often the normal newline 0x0a occurs above and below the > > > 0xa0 line. > >=20 > > That sounds odd. 0xa0 is non-breaking space, which doesn't have > > anything to do with newlines. > >=20 > > However, it's not uncommon for message (especially HTML, for some > > reason) to have non-breaking space in them. So of you respond to such > > an article, they'll be quoted just like any other character. >=20 > Well, I am not seeing 0xa0's "quoted", but I *am* seeing them treated as > blank lines. >=20 > Note that I have "url" and "w3" installed. Perhaps the problem lies ther= e? --=20 Daniel Ortmann, LSI Logic, 3425 40th Av NW, Suite 200, Rochester MN 55901 work: Daniel.Ortmann@lsil.com / 507.535.3861 / 63861 int / 8012.3861 gdds home: dortmann@charter.net 612.518.3147, 2414 30 Av NW #D, Rochester MN 559= 01 gpg/pgp public key: http://wwwkeys.us.pgp.net jabber: daniel_ortmann@jabber.org / dortmann@jabber.co.lsil.com