See, e.g.,
http://www.electromontis.net/evoligion/_C/C10.shtml#C10
at the extremities of the text in the green box.

For a year or so I have used left-and right-pointing solid equilateral triangles as navigation pointers to previous and following chapters. These have not been coded, but just visible glyphs. Suddenly the validator gives up, Saying 'Waiter, there's a bad byte in my code! I can't eat that!'. It says something like  '\xD5 on line 20', but it won't show the source code, and the source code doesn't have an \xD5 that I can find, so it leaves me guessing.

I tried &#8882 and &$8883, which get past the validator, but they are puny little things of no merit whatsoever.

(I realize that these really should be at the extremities of the 'Chapter Navigation' line below the box, but this is an  invariant SSI, not what is needed here. I may fiddle with this ...)

Per Jukkela's (sp?) suggestion, I persist in using % on image widths, and 'accessed on xxxx-xx-xx' inside URL anchors, which the validator fusses about and I need, but at least the validator will soldier on after bitching, which it won't do with the triangles.

If you know work-arounds for any of these 3, I'd appreciate hearing about them! The pointers are the most pressing, since they now prevent validation. I don't know why they work, but they do. Can't you persuade the validator to treat them as harmless typos and proceed?

Cheers,

Ferren
===================
(Dr) Ferren MacIntyre
1 ch. des Echarts
Campagne sur Aude
11260 France
+33 (0) 468 748870
===================
MacBook Pro 5,1; 2.4GHz, 4GB
OS X 10.6.8 Snow Leopard
3D Marine Aquarium Screensaver Preview
Free 3D Marine Aquarium Screensaver
Watch dolphins, sharks & orcas on your desktop! Check it out at www.inbox.com/marineaquarium