>>50
I can't test this because I don't use Windows. Why are the runes not showing up in the keyboard editor? Does Windows not know to fall back to other fonts when the one selected lacks a requested character? That's a really embarrassing bug.
Something to keep in mind is that runes are a unicase alphabet (i.e., there is no capital/lowercase distinction), so there is no need to make each key produce the same character with and without shift depressed.
For example, in my layouts, typing "t" produces "ᛏ" but typing "T" produces "ᚦ".
> and I seem to have 1 more letter than keys on the keyboard, I don't know.
There are only 24 Elder Futhark runes, so unless you're adding Anglo-Saxon characters in as well, then you should have two more keys than letters, even if you don't use the same key for more than one rune.
>can someone translate "zxcvbnm" to elder futhatk and print it out here and confirm it?
In my layouts that produces ᛉᛡᚳᚡᛒᚾᛗ, but my layouts can be used to type Elder Futhark and Anglo-Saxon Futhorc as well as a few miscellaneous medieval runes.
If you want to be strictly Elder Futhark and never press "shift", I might go with something like this:
ᚦᚹᛖᚱᛏᛇᚢᛁᛟᛈ
ᚨᛋᛞᚠᚷᚺᛃ_ᛚ
ᛉ_ᚲᛜᛒᚾᛗ
But this is just one possible idea, since there is no possible way to establish an exact one-to-one correspondence of EF runes to English Latin letters, I've just put the ᚦ, ᛜ, and ᛇ in places that looked easy to reach and reasonably easy to remember.