unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: html / emacs / email / gnus: 0xa0 classified as "whitespace" but not   treated as whitespace
Date: Wed, 20 Oct 2004 09:58:08 -0600	[thread overview]
Message-ID: <2tng8mF221agtU1@uni-berlin.de> (raw)
In-Reply-To: <mailman.4093.1098222316.2017.bug-gnu-emacs@gnu.org>

[Please don't top-post.]

Daniel Ortmann wrote:
 > 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:   (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
 > 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
 > --------------------------------

Latin 1 0xA0 is named NO-BREAK SPACE for a reason.  It should not be
treated the same as ASCII 0x20, which is the SPACE character.

-- 
Kevin

  parent reply	other threads:[~2004-10-20 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 17:09 html / emacs / email / w3 / gnus: 0xa0 and 0x0a both used as newlines Lars Magne Ingebrigtsen
2004-09-30 18:42 ` Daniel Ortmann
2004-10-19 21:37   ` html / emacs / email / gnus: 0xa0 classified as "whitespace" but not treated as whitespace Daniel Ortmann
     [not found]   ` <mailman.4093.1098222316.2017.bug-gnu-emacs@gnu.org>
2004-10-20 15:58     ` Kevin Rodgers [this message]
     [not found] ` <mailman.573.1096570193.2017.bug-gnu-emacs@gnu.org>
2004-09-30 19:52   ` html / emacs / email / w3 / gnus: 0xa0 and 0x0a both used as newlines Lars Magne Ingebrigtsen

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=2tng8mF221agtU1@uni-berlin.de \
    --to=ihs_4664@yahoo.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).