/futh/ - Futhark

>>12

Damn I fucked up the fat text. What I mean was

Fat text = (Prefix)FAT(Sufix)

Rune text = (Prefix)᛬ᚱᛃᚢᚾ᛬(Sufix)

you know what I mean?

>>12

>>13

Interesting thought. I'll look into it.

If you'd prefer to just type them directly, I have some keyboard layouts I've developed. Here is one for OS X:

https://github.com/raidh0/runic-text-resources/blob/master/OS%20X/futhorc.keylayout

I'll get my Linux xkb layout up in a moment. It's hard to install, but I can assist.

If you're on Windows I can't really help you. But these might be of some use:

http://www.babelstone.co.uk/Keyboards/Runic.html

Linux xkb map and installation doc:

https://github.com/raidh0/runic-text-resources/tree/master/Linux

An alternative, brute force method would be to write a simple console program that would convert ASCII text into the correct unicode characters, and then one could just copy/paste the results.

If anyone's interested, I'll post the code.

>>28

I'll be honest, I'm not to sure how to add a text format. If I had some instruction I could.

>>28

The correspondence is not letter-to-letter, though, but sound-to-letter. There is a relatively good phonetic library in the NLTK and I've been pondering how to make a useful tool for runic transcription with it, but I've not written even a line of code.

>>34

>>32

Give me a little while, and I'll write a really simple C++ code that converts specific keys into runes. It's not very elegant, but it just werks.

The correspondence has a phonetic component, but most of the time it's just verbatim transcription, because a complete phonetic transcription can be confusing. No one wants to see "p-i-p-e-l" in rune form, they want to see "people," even though the eo dipthong is taken care of by Isa, and the e on the end is silent.

>>39

The code will work like a keyboard, so it won't actually take care of any "th," or "ei" clusters; you'll have to enter that in manually.

>>39

>Give me a little while, and I'll write a really simple C++ code that converts specific keys into runes. It's not very elegant, but it just werks.

That's just a keyboard map. There's no reason to write a program that traps keystrokes and outputs characters when your OS already has one. Just use one of the existing keyboard maps or help to create new keyboard mappings. This software literally already exists in your kernel or windowing system; it wants you to give it keymaps.

>The correspondence has a phonetic component, but most of the time it's just verbatim transcription, because a complete phonetic transcription can be confusing. No one wants to see "p-i-p-e-l" in rune form, they want to see "people," even though the eo dipthong is taken care of by Isa, and the e on the end is silent.

English writing is like five or six rounds of phonetic cruft piled on over the original Proto-Germanic phonetic system, and a letter-to-letter approach would never use important runes like ᚦ or ᛜ. If we are going to promote a new writing system, it would be fucking moronic not to at least start with a direct phonetic representation.

>>43

The point is that it's a letter-to-letter transcription until Iwar, Thurs, or Ing can be used.

>>46

We have at most one opportunity to switch people over from the Latin alphabet to runes. How many spelling reforms have succeeded in Modern English? People laugh them off every time they are proposed. If we try to adopt a "transitional" writing system that uses a letter-to-letter mapping, with the plan of eventually switching to a phonetic mapping at some later date, we will be stuck with the original letter-to-letter mapping indefinitely.

If we are going to propose a runic writing system for Modern English, then the only thing that is sensible, with any chance whatsoever of sticking, is to develop a phonetic transcription: one phoneme, one rune; one rune, one phoneme.

>>17

>>21

Due to signals of hostility from Github in their (now withdrawn) "Code of Conduct", these layouts are now hosted at Gitgud:

https://gitgud.io/raidh0/runic-text-resources