Hello Fred & Grace,


--- In norse_course@yahoogroups.com, Fred & Grace Hatton <hatton@...>
wrote:

>
> I can't make sense of the Old Norse words Xigung posts either. All the
> unusual characters have taken on new identities.

I think you are right, it keeps changing.
When I looked now, I saw that my post's header is marked with:

MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

which shows that Yahoo is back to using MIME, as well as iso-8859-1
char codes. And indeed, the sentence I sent looks like this on the
source level at Yahoo:
"Ok er hann kom til hrossanna, =C3=BE=C3=A1 elti hann =C3=BEau, ok
v=C3=A1r=
u =C3=BEau n=C3=BA
skj=C3=B6rr, er aldrei v=C3=A1ru v=C3=B6n at ganga undan manni, nema
Freyfa=
xi einn;
hann var sv=C3=A1 kyrr sem hann v=C3=A6ri grafinn ni=C3=B0r."

in which you will recognize the MIME codes.
B U T :
The change is that formerly MIMEed chars were coded by only
two hex digits, whereas now there are FOUR! (<-- NB!)
Look for example at "v=C3=A6=ri".
Here C3 = 13*16 + 3 = 211
and A6 = 10*16 +6 = 166

The net code would then be 211*16^2 + 166 = 54016 + 166,
which certainly is more complicated than I can recall
from a few years back(?) Or is the C3-prefix just to be
ignored. Char#(166) is however not quite the iso-8859-1
char that I intended. Could it refer to a different code page?
The reception is good, though, and I do see the message that
I wrote with correct ON chars. Strange that my Browser now has
set itself to "Windows 1252". Apparently the browser did that without
being asked. (I use Mozilla Firebird today, maybe I used plain
Mozilla yesterday, and that is why it differs in the settings)


Xigung