J. P. Gilliver (John) wrote:
In message , "J. P. Gilliver
(John)" writes:
In message , Andy Burns
writes:
T wrote:

I was going to write you back using the thorn symbol, but
I would have to switch to HTML to do so.

What's so hard about 0

What's so hard is that you might be seeing the character you expect
before the question mark, but not everyone else will; I see a square.
HTML might get over such limitations, if the person reading has a
recent enough HTML parser that it knows the code for the character
that you've used.

And judging by the fact that it's come back as " ", I'm guessing you
were using a non-standard question mark too! (And the mystery character
has come out as 0 this time!)

AHA! So there was something I missed there. The char-set is UTF-8.

http://al.howardknight.net/msgid.cgi...ividual.net%3E

https://groups.google.com/forum/#!or...A/vSR8gShFBwAJ

EA 9D A4 ?

http://unicode-search.net/unicode-na....pl?term=THORN

UTF-8 encoding LATIN CA*PI*TAL LET*TER THORN WITH STROKE

What's interesting, is none of my three browsers can reproduce the
graphic symbols in that table. I guess "THORN with stroke"
causes them to "have a stroke". The best of the lot of browsers,
all it got was a square.

I loaded the unicode-search page into MSEDGE and it managed
to render the information OK. Page looks like this. The one
in question, is the one in the middle of the seven entries.

https://s23.postimg.org/k5dv5m3bf/thorn.gif

*******

So are those hieroglyphics or Sumerian cuneiform ? :-)

Apparently cuneiform has its own Unicode table. So the
next time your browser cannot render something, blame it
on this.

https://en.wikipedia.org/wiki/Cuneiform_script

"In exchange for three sheep today, I will pay you a hamburger on Tuesday"
http://www.unicode.org/charts/PDF/U12000.pdf

Paul