Working on ‘Why the Broom’s Neck is Tied’

Introduction Going into my first session of the Demarginalising Orature class I wasn’t really sure what to expect. I knew it was going to be something quite different from what I’d done before, and I was excited to learn something … Continue reading

Presenting our Codes

This week we presented the codes we did for homework and talked about difficulties and problems. Some of the problems mentioned were: making sure that all the tags are closed, finding quotes in the text so it can be properly coded and the order in which the divisions need to be closed.

We also decided that we are going to use the English terms for the animals in the folktales in the titles, to make it more accessible for readers who don’t understand the Likpakpaln language. In the stories themselves the Likpakpaln words will still be used because we don’t only want to share the folktales but also the culture that they originate from.

How to Code: Songs, Footnotes and Glossary

This week we started the session going over some common mistakes and mishaps from our homework. After Anne and Michael pointed out the mistakes we got some time to correct our codes so we could move on to the next tasks with a perfect code.

Then we learned how to code a song. This is special because the songs are displayed in two columns: one for the Likpakpaln transcript and one for the English translation. In order to do that we need to create a table in the code. This is the code we were taught to use:

<div type= “song”> 

<table type= “translation”>

<row role= “head”> 

<cell><hi rend= “bold”>Likpakpaln transcription</hi></cell> 

<cell><hi rend= “bold”>English translation</hi></cell>

</row> 

<row></row> 

<row> <cell><l>Maadim ee, bi koo’ pak Maadim ee too. (2x)</l></cell>

<cell><l>Maadim, all are full of praise for Maadim. (2x)</l></cell> </row>

</table>

</div>

In order for the lines of the song to be more legible we place an empty row between the lines.

We were also taught how to code footnotes and a glossary. Both codes work in a similar way where there needs to be a connection between the footnote or the word in the text and the corresponding number or explanation in the notes/glossary.

These are the examples we were given:

footnotes:

… <term xml:id=”footnote1″><hi rend=”superscript”>1</hi></term>

<div type=”Note”>

<head type=”subTitle”>Note</head>

<list type=”index”>

<label>1.</label><item><gloss target=”#footnote1″> explanation </gloss></item>

</list>

</div>

glossary:

<cell><l><term ref=”#gloss1″>Asantes</term> passed here</l></cell>

<div type=”glossary”>

<head type=”subTitle”>A Glossary of Likpakpaln Words</head>

<list type=”gloss”>

<label>Asantes:</label><item><gloss xml:id=”gloss1″>plural form of Asante.

The Asante people, who are commonly known as Ashanti people or Ashantis, are one of the ethnic groups in Ghana that make up the Akan group. They inhabit the southern part of Ghana, especially the Ashanti region.</gloss></item>

</list>

</div>

Finally, we were placed into groups of two for our group project.