[Next Project] The Poetic Edda, translated by Henry Adams Bellows

210 views
Skip to first unread message

Galen Hazelwood

unread,
Feb 27, 2025, 1:14:08 PMFeb 27
to standar...@googlegroups.com
I proposed doing this one previously, and was warned off based on the difficulty of formatting it. I think I've proved myself with my work on the Wellman collection, and would like to propose this one again.

As proof of concept, I've formatted the first poem in the book, the Voluspo, into what I think is an acceptable state. I've also patched together a preliminary local.css file based on the SEMoS and the examples of similar epic poems, specifically the Nibelungenlied. It's viewable in this repository:


Thanks,
--Galen

Alex Cabal

unread,
Feb 27, 2025, 4:16:28 PMFeb 27
to standar...@googlegroups.com
OK. This looks like a top tier difficulty book but if you want to give
it a shot then go for it. As you noted Emma worked on similar formatting
in the Nibelungenleid so I will assign her as the manager here.

The pronouncing index would be better formatted as a glossary. You will
have to include a search key map, see the manual. I don't think we need
to include the actual links to references as people can just search for
them if they want.
> <https://github.com/galenhz/anonymous_the-poetic-edda_henry-adams-bellows>
>
> Thanks,
> --Galen
>
> --
> You received this message because you are subscribed to the Google
> Groups "Standard Ebooks" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to standardebook...@googlegroups.com
> <mailto:standardebook...@googlegroups.com>.
> To view this discussion visit
> https://groups.google.com/d/msgid/standardebooks/CANDRfYeNA6Kfc8R4-XpSEqE5R0Ju6m2vh7nMxZ3Vqkzs5J1DHQ%40mail.gmail.com <https://groups.google.com/d/msgid/standardebooks/CANDRfYeNA6Kfc8R4-XpSEqE5R0Ju6m2vh7nMxZ3Vqkzs5J1DHQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.

Emma Sweeney

unread,
Feb 27, 2025, 5:29:01 PMFeb 27
to Standard Ebooks
The file formatting should look something like this:

<body epub:type="bodymatter z3998:fiction">
<section data-parent="volume-1" id="voluspo" epub:type="chapter">
...
<section id="voluspo-introduction" epub:type="introduction">
...
</section>
<section id="voluspo-poem" epub:type="z3998:poem">
...
</section>
</section>
</body>

Some poems have subsections which would also be placed in separate <section> elements.

For this production, I recommend using <div> elements rather than <section> elements for the stanzas; the other poems have prose paragraphs in between stanzas.

You should also convert the stanza numbers to roman numerals.

In the endnotes and introductions, there are some lines of poetry listed on a single line that have caesuras. These need to be placed in <blockquote> elements and restructured like in SEMoS 7.5.

If you encounter anything else that is confusing, the poem how-to guide can help.

Good luck!


Emma

Galen Hazelwood

unread,
Feb 27, 2025, 5:42:34 PMFeb 27
to standar...@googlegroups.com
Emma,

Thanks a lot! I may have to follow up with further questions, but this should be enough to get me going.

--Galen

To unsubscribe from this group and stop receiving emails from it, send an email to standardebook...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/standardebooks/d89531f3-a233-4d93-9b47-d77a7ed2c22an%40googlegroups.com.

Galen Hazelwood

unread,
Feb 27, 2025, 5:50:02 PMFeb 27
to standar...@googlegroups.com
(...are you sure you want the stanza numbers as roman numerals?)

Vince

unread,
Feb 27, 2025, 6:09:22 PMFeb 27
to Standard Ebooks
That is our standard (same as for chapter numbers). I will point out for Emma’s sake that Hovamol has 165 stanzas, and we normally switch to decimal when chapters get much above 100. Hovamol’s the only one over 100, though, so she may still prefer roman.

Emma Sweeney

unread,
Feb 27, 2025, 6:25:45 PMFeb 27
to Standard Ebooks
Yes, they should be roman numerals (SEMoS 8.1.1). The Nibelungenlied uses Arabic numerals because the numberings reach well over 2000. In the Poetic Edda, only one out of thirty-five poems breaks 100. Since a majority of the poems are below 100 stanzas, they should all be converted roman numerals for consistency.

Emma

Galen Hazelwood

unread,
Feb 27, 2025, 6:36:29 PMFeb 27
to standar...@googlegroups.com
All right. I've pushed a commit for the Voluspo which matches your suggestions, and will continue work on the rest.

--Galen

Galen Hazelwood

unread,
Mar 18, 2025, 11:58:37 AMMar 18
to standar...@googlegroups.com
I've completed the machete-tier formatting work on the poems themselves, and am going to start up on the pronunciation index next. It's going to be a slog with only a limited amount of automation possible, since the original spelling of the names aren't in the index at all, just the pronunciations. A few questions before I get going:

1. The SEMoS glossary section allows for multiple terms with a single definition (dd). The index has the opposite situation: a single term with multiple definitions. I think it makes sense to have a single entry for the term with enumerated definitions, like a dictionary word with multiple meanings. Does this make sense, and is there a particular way it should be formatted? Multiple p elements inside the dd, or an HTML ordered list?

2. Given 1, it might be good to keep the links to references, to help differentiate which version applies. No page numbers of course, so I'd need to convert them as links to individual stanzas. If you still think we don't need them, I won't argue; it would save me a lot of work.

3. I'd like to save the phonetic pronunciations as part of the glossary definitions, so I'd like to save the pronunciation guide. Should it be a separate backmatter page, or an introductory section to the glossary itself?

4. (Tangentially related) How should we semanticate the names of the poems, and the names of the work? SEMoS might suggest that "Poetic Edda" would be considered a long poem (se:name.publication.poem) and the individual poems quoted (not italicized) as short works, but that doesn't feel right. The Edda is a collection of poems, not a single unified epic, so I suggest it should get se:name.publication.book, and the poem names italicized with se:name.publication.poem.


To unsubscribe from this group and stop receiving emails from it, send an email to standardebook...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/standardebooks/7c013ac5-907a-4ab6-891a-eec0ac62d36c%40standardebooks.org.

Emma Sweeney

unread,
Mar 18, 2025, 3:24:49 PMMar 18
to Standard Ebooks
1. According to MDN Web Docs, a term with multiple definitions is structured like:

<dl>
<dt id="[TERM]" epub:type="glossterm">
<dfn>[TERM]</dfn>
</dt>
<dd epub:type="glossdef">
<p>[DEFINITION 1].</p>
</dd>
<dd epub:type="glossdef">
<p>[DEFINITION 2].</p>
</dd>
...
</dl>

2. That would be nice, but you would be creating thousands of links. I don't want you to torture yourself. :)

3. I think you should keep the "Pronouncing Index of Proper Names"; these names don't follow typical English phonemes. It's also pretty helpful to know that "Alf" refers to seven different people in the story. This would be in an `appendix.xhtml` with `appendix` semantics. Take a look at other appendices in the corpus for details.

4. The individual stories are short publications so they are quoted. The Poetic Edda would have <i epub:type="se:name.publication.book"> semantics.


Emma

Galen Hazelwood

unread,
Mar 18, 2025, 4:47:24 PMMar 18
to standar...@googlegroups.com
Thanks. Your response to 3 is a little confusing. I'm converting the pronunciation index as a whole into a glossary to preserve it, and my question was specifically about the two-page introduction that precedes it. That section should be made into an appendix? I can see the logic, but wanted to make sure I understood.

Emma Sweeney

unread,
Mar 18, 2025, 7:49:42 PMMar 18
to Standard Ebooks
Sorry, I should've looked at the book rather than rely on memory!

Now that I'm able to look at the book, It looks like the Introductory Note would be in an appendix file. It will be titled:

<hgroup>
<h2 epub:type="title">Pronouncing Index of Proper Names</h2>
<p epub:type="subtitle">Introductory Note</p>
</hgroup>


Emma

Emma Sweeney

unread,
Jun 6, 2025, 12:16:12 AMJun 6
to Standard Ebooks
Hi Galen. I'm checking in to see how progress is going. Are you still working on this? Do you need any help?

Emma

Galen Hazelwood

unread,
Jun 6, 2025, 2:04:51 AMJun 6
to standar...@googlegroups.com
Real life hijacked my time for a while. I'm back on it, building a tool to help autobuild the glossary. I hope to have that done before too much longer.

--Galen

Galen Hazelwood

unread,
Jul 18, 2025, 2:24:01 PMJul 18
to standar...@googlegroups.com
All right, I've worked through the index and created a first pass at the Glossary of Proper Names. With that heavy lifting done, I've got a few questions as I start going through the rest of the process.

1. The poems often have parts where the original text is missing or illegible. The translation marks these bits with a series of 8 dots. Typogrify wants to convert them to two sequences of an ellipsis and a dot:

-                                               <span>.  .  .  .  .  .  .  .</span>
+                                               <span>… .⁠ ⁠… .</span>

I don't think this is right. The original matches what's in the physical books, and it makes logical sense to me. Can I leave these as is?

2. Typogrify also wants to remove commas before dashes, in places like the third line of Voluspo 12:

Vigg and Gandalf,    Vindalf, Thrain,
Thekk and Thorin,    Thror, Vit and Lit,
Nyr and Nyrath,—    now have I told—
Regin and Rathsvith—    the list aright.

Should I accept typogrify's fix here, or leave the poem as it was in the original? I also see the same thing being fixed in the introduction sections. Should I accept it only for the modern text, and leave the poems alone?

3. Semanticating italics. "Poetic Edda" is obviously a "book". The individual parts (Hovemol, Fafnismol, etc.) are also often italicized, so are they "poems"? The standard indicates in 8.2.11.3 that shorter works that don't stand alone should be quoted, not italicized, but this strikes me as a corner case, and italicizing them as poem names is defensible.

4. In the endnotes, a word being defined/glossed is italicized to differentiate it from the rest of the text. How should these be marked? Nothing in the se vocab seems to quite fit.

--Galen

Emma Sweeney

unread,
Jul 18, 2025, 3:57:55 PMJul 18
to Standard Ebooks
1. In poetry, we use the vertical ellipsis for missing lines (SEMoS 7.5.7).
2. Accept the changes made by `se typogrify` in the whole production.
3. These aren't book-length poems; they were probably italicized because they are non-English titles. The titles would be formatted like `“<span xml:lang="non">Voluspo</span>”`
4. You can use the `<dfn>` element for terms being defined in endnotes.

Emma

Galen Hazelwood

unread,
Jul 18, 2025, 4:51:25 PMJul 18
to standar...@googlegroups.com

Galen Hazelwood

unread,
Jul 18, 2025, 9:38:41 PMJul 18
to Standard Ebooks
Okay, regarding the ellipses, a follow-up question on Hovamol 79:

Certain is that   which is sought from runes,
    That the gods so great have made,
    And the Master-Poet painted;
. . . . . . . .    . . . . . . . .
    . . . . . . . of the race of gods:
    Silence is safest and best.

Here we have a missing line, but also half a missing line after it. Should I substitute a horizontal ellipsis on the half-missing line, like so?

Certain is that    which is sought from runes,
    That the gods so great have made,
    And the Master-Poet painted;
      ⋮
    … of the race of gods:
    Silence is safest and best

--Galen

Emma Sweeney

unread,
Jul 18, 2025, 11:50:49 PMJul 18
to Standard Ebooks
That looks correct.

Emma
Reply all
Reply to author
Forward
0 new messages