Re: newbie &nbsp representation question

What is written into the html source is a hex byte "a0".  The "text" &#xa0 
followed by a ; is for the browser to interpret? rather than be dependent 
on the character set used in the source generation or the browser.  The 
standard used:

<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
<html xmlns="" xml:lang="en" lang="en">

should encode/render a "non breaking space" (by the formerly used and now 
disallowed &nbsp) by &#xa0 (followed by a ;) not by a byte.  This seems in 
sync with the difficulty of older text editors to insert a byte that is 
not seen/displayed by the editor.
--just an Amaya newbie who knows only enough to get into trouble

As a side issue and opinion:
The idea of using a "non breaking space" when the option "keep multiple 
spaces" is used and multiple spaces are placed in the Amaya 
"rendered/non-source" text seems somewhat excessive.  I do not know if 
the XML/xhtml standards disallow multiple spaces.  Leaving multiple spaces 
in the "source" code would allow those multiple spaces to be broken over 
lines rendered by the browser(s). The coder/author would/should insert the 
specific "non breaking space" when that is the desired effect.  So far I 
have not seen a method to insert that specific special character in Amaya 
11.2's WYSIWYG editor.  All "real" writers use source html not a 

I really!!!! like Amaya.  My coding directly in (x)html is woefully error 
prone and feature/syntax ignorant.  Amaya gives great WYSIWYG!  I have 
been using html to keep various "logs" since 1999 and got hooked on 
simple, easy to compose, fast to compose, pages that open source WYSIWYG 
HTML editors provide.  There is probably no excuse for being so addicted 
to the easy solutions that Amaya, Mozilla, Seamonkey, Openoffice, etc. 

Thank you,

Jim Waldram                   Atmospheric Science Dept.
Exec. Computer Support Spec.  University of Wyoming             Department 3038
307-766-5351 (Ph)             1000 E. University Ave.
307-766-2635 (Fax)            Laramie, WY 82071

On Sat, 8 Aug 2009, Stanimir Stamenkov wrote:

> Sat, 08 Aug 2009 14:34:43 +0300, /Stanimir Stamenkov/:
>> Mon, 3 Aug 2009 16:36:58 -0600, /J. Waldram/:
>>> Amaya 11.2, with the "Keep multiple Spaces" option, the &nbsp is
>>> represented as a hex byte 0xa0 instead of &#160; or &#xa0;.  Is this a
>>> mis-translation for the &nbsp that is rendered by browsers?  Since XML
>>> does not allow &nbsp and the &#xa0 is allowed could this be recoded as
>>> a text string not a hex byte?
>> It is not a "hex byte" but the NBSP character included literally in the
>> text (if you choose UTF-8 or another UTF variant then the character will
>> be represented by two or more bytes).  I guess it is included like that
>> as it gets just one character in the source vs. 6 (  or &#160; or
>> &#xA0;).  If you set your source encoding to US-ASCII then this
>> character cannot be literally encoded therefore Amaya will write it as  .
> Seems the mailing list software has replaced occurrences of &nbsp
> followed by ; with a space.  The last sentence should end with it.
> -- 
> Stanimir

Received on Monday, 10 August 2009 18:47:52 UTC