Template talk:Runes

Unicode

nice job with the table, but the runes are missing the {{unicode}} template, this should be fixed occasionally. dab (ᛏ) 21:13, 2 August 2006 (UTC)

Armanen runes

Can the Armanen runes be added to this template? FK0071a 11:50, 2 December 2006 (UTC)

no. they are not historical. dab (𒁳) 11:23, 5 December 2006 (UTC)

Format change

This template is very useful, but the format could do with an update. If it is possible to fit the information into a {{Navbox}} template, it would have been a lot better. I have tried once, but it is a bit difficult. Any ideas? –Holt T•C 20:05, 3 November 2008 (UTC)

I don't see a problem with the current template -- quite some thought went into its design. You won't be able to imitate the current tabular arrangement by transcluding {{Navbox}}. --dab (𒁳) 15:37, 4 November 2008 (UTC)

The current template is good, the way it is worked out shows that it has not been made in a flash. However, the ideal would be to have that arrangement in a navbox template, because of the upsides with navbox. Collapsing, right placement, greater flexibility in settings, streamlining the templates used in the topics etc. What I am saying is that if arranging the characters as in the current template is possible in a navbox template, we should go for the latter. The format change is just a suggestion. If it is not possible at all - that is fine, but at least we tried. –Holt T•C 15:53, 4 November 2008 (UTC)

I think it would be more important to fix some issues in the old template, such as the algiz rune which appears in two places (in the second place as the Yr-rune). It should be presented in the same way as the Jera rune.--Berig (talk) 18:02, 5 November 2008 (UTC)

I am not sure what you mean. The Yr rune may have developed out of the Algiz rune, but they are not identical. We happen to discuss them together, in a single article, but that's just a matter of organizing content, not of "identity". dab (𒁳) 18:28, 5 November 2008 (UTC)

strike that, we now even have two separate articles, at Algiz and at Yr rune. dab (𒁳) 18:29, 5 November 2008 (UTC)

I don't think anyone doubts that the Yr rune is derived from the Algiz rune. Fact is that it was only turned upside down and continued to denote the same phoneme in Old East Norse (although it evolved from z to an r sound). It is interesting to note that the only sources for the Norse name of the rune (the rune poems) are from Old West Norse where the rune was superfluous (and not used). When it also became superfluous in East Norse it found a new role in the medieval runes to denote the y phoneme.--Berig (talk) 20:22, 5 November 2008 (UTC)

[outdent] That is fine, my suggestion was more of an aesthetic one. In any case, I agree that the current template is not perfect. For example the transliteration which seems to favour the Elder Futhark, while the AS and Younger variations are noted on the side. E.g. as if ᚩ is a, and kind of o. It is vague for those who are not fully familiar with the futharks. –Holt T•C 20:07, 5 November 2008 (UTC)

Development

I think Template:Navbox with columns could be used for this if the limit was more than 20. — CharlotteWebb 18:45, 11 September 2009 (UTC)

Good idea but a lot more than 20 columns are needed. 1.126.110.22 (talk) 12:08, 7 October 2022 (UTC)

Size of characters

Would there be a way to increase the size of the characters in the template? They're really tiny.

I can do it if it's OK, but I'm not sure how to, from a markup (I guess?) perspective. §FreeRangeFrog 08:38, 30 December 2008 (UTC)

Is it better now? 1.126.105.45 (talk) 19:55, 6 September 2024 (UTC)

Medieval runes

These have been lacking for some time. They should be added to the template, even if the article infoboxes don't include them. LokiClock (talk) 15:48, 4 February 2010 (UTC)

They are now included. 1.126.105.45 (talk) 18:58, 6 September 2024 (UTC)

Position of Transliterations - Inline Emphasis

On my screen, some of the Latin letters appear up among the runes, whereas I would expect to see those only in the bottom row, labeled "transliteration". Do they belong up there for some reason?

Jack Waugh (talk) 01:01, 4 September 2011 (UTC)

Latin is used for discrepancies with the Elder Futhark (bottom) transcriptions & system-exclusive runes. ᛭ LokiClock (talk) 09:16, 5 September 2011 (UTC)

Added brackets around them to help distinguish. They mean that those runes are transcribed differently to how those in the same column typically are. 1.126.110.22 (talk) 12:07, 7 October 2022 (UTC)

I think what LokiClock was trying to say, is that in the main 3 rows of glyphs for Elder Furthark, Old English Furthorc, and Younger Furthark, some variations/discrepancies between the 3 periods are marked by including a transliteration to the right of that character (in black). E.g. the sixth character "torch" glyph differs in the 3 alphabets, and is transliterated as 'k' in Elder Furthark, but as 'c' in Old English Forthorc. The inclusion of the 'c' next to Old English glyph highlights this distinction. However for most readers, the intention of the added inline transliteration emphasis will probably be lost and regarded as 'display noise'.

There are always going to be numerous phonetic shifts between periods. Highlighting some of them seems inconsistent. I would simplify the table by having transliterations only on the bottom row and leave further distinctions to the academic endeavors of the reader. LarryLACa (talk) 00:06, 11 January 2015 (UTC)

Meaning of Transliterations

What the transliterations are intended to mean needs to be clarified. Are they academic Latinisations or phonemic transcriptions? Currently, they appear to be a mixture of both, which is confusing and ambiguous. May I suggest clearly labelling what's what. 1.126.105.45 (talk) 19:03, 6 September 2024 (UTC)

Bold are direct latin transliterations. Lower values are transliterated secondary sound values, which have not been standardised. The Younger values are transliterated to their equivelant in modern Nordic languages. Anglo-Saxon is mainly phonetic. Blockhaj (talk) 21:36, 6 September 2024 (UTC)