Re: html / emacs / email / w3 / gnus: 0xa0 and 0x0a both used as newlines

Re: html / emacs / email / w3 / gnus: 0xa0 and 0x0a both used as newlines

[Lars Magne Ingebrigtsen]

Daniel Ortmann <dortmann@lsil.com> writes:

> 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.

That sounds odd.  0xa0 is non-breaking space, which doesn't have
anything to do with newlines.

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. 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: html / emacs / email / w3 / gnus: 0xa0 and 0x0a both used as newlines

[Daniel Ortmann]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Daniel Ortmann <dortmann@lsil.com> writes:
> 
> > 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.
> 
> That sounds odd.  0xa0 is non-breaking space, which doesn't have
> anything to do with newlines.
> 
> 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.

Well, I am not seeing 0xa0's "quoted", but I *am* seeing them treated as
blank lines.

Note that I have "url" and "w3" installed.  Perhaps the problem lies there?

-- 
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 507.288.7732, 2414 30Av NW #D, Rochester MN 55901
gpg/pgp public key: http://wwwkeys.us.pgp.net
jabber: daniel_ortmann@jabber.org / dortmann@jabber.co.lsil.com

Re: html / emacs / email / w3 / gnus: 0xa0 and 0x0a both used as newlines

[Lars Magne Ingebrigtsen]

Daniel Ortmann <dortmann@lsil.com> writes:

> Well, I am not seeing 0xa0's "quoted", but I *am* seeing them
> treated as blank lines.

In Message mode?  Then they're presumably quoted from the message
you're responding to.

> Note that I have "url" and "w3" installed.  Perhaps the problem lies
> there?

Look at the original messages.  Do the characters appear there, too? 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

html / emacs / email / gnus: 0xa0 classified as "whitespace" but not treated as whitespace

[Daniel Ortmann]

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
--------------------------------

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 <dortmann@lsil.com> writes:

> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> 
> > Daniel Ortmann <dortmann@lsil.com> writes:
> > 
> > > 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.
> > 
> > That sounds odd.  0xa0 is non-breaking space, which doesn't have
> > anything to do with newlines.
> > 
> > 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.
> 
> Well, I am not seeing 0xa0's "quoted", but I *am* seeing them treated as
> blank lines.
> 
> Note that I have "url" and "w3" installed.  Perhaps the problem lies there?

-- 
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 55901
gpg/pgp public key: http://wwwkeys.us.pgp.net
jabber: daniel_ortmann@jabber.org / dortmann@jabber.co.lsil.com

Re: html / emacs / email / gnus: 0xa0 classified as "whitespace" but not treated as whitespace

[Kevin Rodgers]

[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