Some before pseudo element breaks Amaya handling of UTF-8

Using Amaya 11.3.1 (Dec  9 2009) under Ubuntu 10.10.
Some before pseudo element breaks Amaya handling of UTF-8: multi-byte 
characters are replaced in the code by the succession of the separated 
bytes.

I write a document with a note called by a digit one like this1. The 
document is encoded as UTF-8 and declared as such.
See attached callnote1.html.

I then feel this would look nicer like [1] and I use before and after 
pseudo-elements to achieve this. The space before the opening square 
bracket is part of the content of the before pseudo-element. I do not 
want to take the risk to have this cut from the preceding word, so the 
space is not a plain space but a non break space U+A0. Is this non 
conforming in any way? This was written in a good serious editor 
(actually Bluefish 2.0.1) and looks nice in other editors too. It 
displays all right in Firefox.
See attached callnoteNBSP[1].html.

If I now open, edit and save this in Amaya, the code is 
broken:multi-byte characters are replaced in the code by the succession 
of the separated bytes. This still gives a correct display in Amaya 
(once) and Firefox, except for the non break space provided by the 
pseudo-element. The code can be opened  in another editor but is not 
readable any more. Amaya is even unable to reopen it’s own file.
See attached callnoteNBSP[1]brokenAmaya.html.

So far for the crude description of the bug. Excuse me if I take now the 
liberty to complain a little. I commonly edit lots of html documents 
using Amaya for the ease of WYSIWYG, and Bluefish when I want to handle 
the code. Since this works perfectly, I do not keep every last good 
version each time I edit a document. (Amaya has long been awfully buggy 
and I wouldn’t have taken such a risk in the past. But since a few years 
Amaya behaves quite reliably, with only small non destructive bugs. 
Thanks to the Amaya team.) This pseudo-element affair came to me as a 
surprise in a rather long and important document and I was not 
particularly happy when I found that Amaya had, at first sight, 
completely messed it up. Fortunately I could get my document back by a 
series of search-and-replace in Bluefish on the many different chains of 
queer bytes for multi-byte characters. I wrote the examples above in 
English to test the bug and write to the list, but my big important 
document was in French with many accented characters, real typographical 
apostrophes, real typographical quotation marks, and thus an awful lot 
of destruction by Amaya. As a work around, I take the css away when I 
use Amaya to continue editing this particular document in WYSIWYG, and 
put it back afterwards. But I may once forget and destroy my document again.
-- 
Amicalement, Dominique,
dominique@d-meeus.be, +32 473 61 31 75, http://www.d-meeus.be/
This made me wonder right away — « Is he deep ? » He wore glasses so it 
was possible. (Paul McCartney, « Introduction », parlant de John dans 
John Lennon, /In his own write 
<http://studies.d-meeus.be/wikindx3/index.php?action=resourceView&id=747>/, 
Jonathan Cape, Londres, 1964.)