{"id":994,"date":"2023-11-06T15:57:42","date_gmt":"2023-11-06T14:57:42","guid":{"rendered":"https:\/\/blogs.phil.hhu.de\/ctsdus\/?p=994"},"modified":"2023-11-07T11:37:07","modified_gmt":"2023-11-07T10:37:07","slug":"coding-for-term-refgloss1-blutige-anfanger-term","status":"publish","type":"post","link":"https:\/\/blogs.phil.hhu.de\/ctsdus\/2023\/11\/06\/coding-for-term-refgloss1-blutige-anfanger-term\/","title":{"rendered":"Coding for <term ref=gloss1> blutige Anf\u00e4nger <\/term>"},"content":{"rendered":"\n
<\/figure>\n\n\n\n

<TEI xmlns=”http:\/\/www.tei-c.org\/ns\/1.0″><\/p>\n\n\n\n

    <teiHeader><\/p>\n\n\n\n

        <fileDesc><\/p>\n\n\n\n

            <titleStmt><\/p>\n\n\n\n

<title> Coding for <term ref=gloss1> blutige Anf\u00e4nger <\/term> <\/title><\/strong><\/p>\n\n\n\n

                <author> Jule Wolters <\/author><\/p>\n\n\n\n

                  >\/titleStmt><\/p>\n\n\n\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/teiHeader><\/p>\n\n\n\n

<text><\/p>\n\n\n\n

         <body><\/p>\n\n\n\n

         <div type=”introduction”><\/p>\n\n\n\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<head type=\u201dsubTitle\u201d> Introduction<\/head><\/p>\n\n\n\n

<p><\/p>\n\n\n\n

Hello everyone! Welcome to my blog entry about our second Coding lesson in the seminar \u201eDemarginalising Orature: Translating Minor Forms into the Digital Age\u201c. To be completely honest with you, I had very little to no hope for today\u2019s class. I feel more at home in books and the literary aspect of my course of study than in anything regarding linguistics, statistics, etc. But I was extremely positively surprised at the outcome and would like to share with you my biggest take-aways, or maybe tips and tricks in a way, in the hopes that they might aid us all when we start coding our folktales.<\/p><\/p>\n\n\n\n

<\/div><\/p>\n\n\n\n

<div type=\u201dstory\u201d><\/p>\n\n\n\n

<head type=subtitle>Story<\/head><\/p>\n\n\n\n

<p><\/p>\n\n\n\n

1. Closing your tags<\/strong><\/p>\n\n\n\n

We spoke about this in our first session, but I had no idea what it meant. Thankfully, during our \u201cFind the errors\u201d exercise, I understood that \u201cclosing it\u201d stands for:<\/p>\n\n\n\n

– repeating your tag<\/p>\n\n\n\n

– but adding a \/ before the word and behind the <<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

I found it very helpful that Visual Studio Code immediately creates the closing tag when you open one, even though I did start writing them manually and then got confused why I had multiple closing tags.<\/p>\n\n\n\n

2. Finding said tags<\/strong><\/p>\n\n\n\n

Also in our \u201cFind the errors\u201d exercise, there were intentionally rows left blank which then looked like this:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

As a <term ref=gloss1> blutiger Anf\u00e4nger <\/term>, I was obviously confused about this. We\u2019re at the end of the Header in my example photo, so it is likely that a tag needs to be closed here. I wasn\u2019t sure which one though. But then I noticed the lines going up on the left and subsequently found out that:<\/p>\n\n\n\n