<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><b>Question 1</b><div>Unfortunately There is no way to avoid making typos.</div><div><br></div><div><br></div><div><b>Question 2</b></div><div>There are two ways to check for typos. One is with command:</div><div><br></div><div><font color="#ff2600">freq +s"[\* *]" +u +o3 *.cha</font></div><div><br></div><div>This command will combine all error codes found in all transcripts specified by *.cha on all speaker utterances into one small list. This assumes that all your transcripts are in one working directory. If your transcripts are in multiple sub-directories, then set working directory to the top directory level and add +re option to FREQ command. You can also add +d option to see which file and utterance a particular code is located on. The +d2 option just adds unnecessary complexity.</div><div><br></div><div><br></div><div>The other way is to list only legal error codes in "depfile.cut" that CHECK and ESC-L commands use to validate CHAT files. The "depfile.cut" file is located in "CLAN/lib" directory of your CLAN distribution. Inside the "depfile.cut" look for <font color="#ff2600">[\* _*]</font> string. This allow any error code by way of "_*" symbols, i.e. star (*) character means any string combination. You can edit "depfile.cut" and replace the <font color="#ff2600">[\* _*]</font> string with just error codes that you want to allow, i.e. <font color="#ff2600">[\* p:w] [\* p:n] [\* p:m]</font> . There are a lot of error codes in CLAN CHAT manuals. You can list all of them or just few that are pertinent to your corpus. After you save the "depfile.cut" file. CHECK and ESC-L commands will report an error if any other error codes are found in your transcripts. </div><div><br></div><div>We do not recommend changing "depfile.cut", because it is easy to make mistake that will allow errors in transcripts. Also, because your copy of "depfile.cut" will be replaced by standard distribution copy if and when you update CLAN on your computer.</div><div><br></div><div><br></div><div><b>Question 3</b></div><div>The difference between your command and mine is that your command has two "\" characters that are redundant. Also, your command will only check *PAR speakers. It will not detect errors on other speaker's utterances.<br><div>
<br class="Apple-interchange-newline"><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Arial; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Arial; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; display: inline !important; float: none;">Leonid.</span>
</div>
<div><br><blockquote type="cite"><div>On Oct 3, 2024, at 04:20, Sophie Brook <sophiemeibrook@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div>Thank you for your swift and helpful response! <div><br></div><div><br><div><b>Yes you have understood correctly :) </b><br></div><div>In this case, we don't want to create new error codes (because any "new codes" is a result of typos as opposed to purposely wanting to create new codes). </div><div><br></div><div><b>Question 1</b></div><div>So to check I have understood correctly, the way to make sure error codes are only from the CLAN manual is by careful transcription (aka not making typos)?</div><div><br></div><div><b>Question 2</b></div><div>We can catch error codes we do not want in our transcripts but the way to check for unwanted codes is to manually look at this spreadsheet output made by the code above? </div><div><br></div><div><b>Question 3</b></div><div>Is there a difference between the code you've typed (freq +s"[\* *]") and the one I typed <span style="font-family: Calibri; font-size: 16px; background-color: rgb(255, 255, 0);">freq +s"\[\* *\]" +t*PAR * +d2 ?</span></div><div><font face="Calibri"><span style="font-size: 16px;"><br></span></font></div><div>Thanks. </div><div><br></div><div>Sophie</div><div>(she/her/hers) <br><br></div></div><div class="gmail_quote"><div dir="auto" class="gmail_attr">On Wednesday, October 2, 2024 at 12:22:58 PM UTC+1 Leonid Spektor wrote:<br></div><blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div style="line-break:after-white-space">Hi Sophie,<div><br></div><div><span style="white-space:pre"> </span>I don't understand what the problem is. Is it that FREQ command finds error code that you are not looking for or is it that data files have error codes that you consider illegal?</div><div><br></div><div><span style="white-space:pre"> </span>CLAN does not check spelling of error codes. It assumes that if you have [* ...], then you want it to be an error code. It is up to transcriber to follow valid error codes convention and to use only valid error codes in transcripts.</div><div><br></div><div>This approach allows transcriber to create new error codes that are specific to their transcription and to not be limited by just few choice error codes. If you run command (freq +s"[\* *]"), similar to the one you have in your email, then you can catch any error codes that you do not want in your transcript.</div><div><br></div><div><br></div><div><div><br style="font-family: Arial; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; text-decoration: none;"><span style="font-family: Arial; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; text-decoration: none; float: none; display: inline !important;">Leonid.</span>
</div>
<div><br><blockquote type="cite"></blockquote></div></div></div><div style="line-break:after-white-space"><div><div><blockquote type="cite"><div>On Oct 2, 2024, at 06:51, Sophie Brook <<a href="" data-email-masked="" rel="nofollow">sophiem...@gmail.com</a>> wrote:</div><br></blockquote></div></div></div><div style="line-break:after-white-space"><div><div><blockquote type="cite"><div>Hi there, <div><br></div><div><b>What I did</b></div><div>I used this code: </div><div>
<div title="Page 4">
<div>
<div><p><span style="font-size:12pt;font-family:Calibri;background-color:rgb(255,255,0)">freq +s"\[\* *\]" +t*PAR * +d2</span></p><p>to output frequencies of different errors e.g., phonological [* p:w] [* p:n] , morphological, semantic and neologisms etc etc </p><p><b>The problem</b></p><p>I found mistypes within the errors in the output eg [* p:nw] was not found to be an error even though this error code is not a valid one recognised by CLAN. Or another example, missing square brackets and colons in error codes. </p><p>I have been manually changing the CHAT files after combing through the columns to see which transcriptions have found these "illegal error codes". <br></p><p><b><br></b></p><p><b>Question </b></p><p>Why is this happening?</p><p>Is there a way around this?</p><p><br></p><p><br></p><p><br></p><p>Thank you!!! :) </p><p>Best, </p><p>Sophie Brook </p><p>(she/her) </p><p><b><br></b></p><p><b><br></b></p><p><br></p>
</div>
</div>
</div></div><div><br></div></div></blockquote></div></div></div><div style="line-break:after-white-space"><div><div><blockquote type="cite"><div>
-- <br>
You received this message because you are subscribed to the Google Groups "chibolts" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="" data-email-masked="" rel="nofollow">chibolts+u...@googlegroups.com</a>.<br>
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/chibolts/ae6e75f8-9e56-4e2c-9f55-82d1fc59bee3n%40googlegroups.com?utm_medium=email&utm_source=footer" target="_blank" rel="nofollow" data-saferedirecturl="https://www.google.com/url?hl=en&q=https://groups.google.com/d/msgid/chibolts/ae6e75f8-9e56-4e2c-9f55-82d1fc59bee3n%2540googlegroups.com?utm_medium%3Demail%26utm_source%3Dfooter&source=gmail&ust=1728029677632000&usg=AOvVaw0h415AtJLQms-JaSsDSPKy">https://groups.google.com/d/msgid/chibolts/ae6e75f8-9e56-4e2c-9f55-82d1fc59bee3n%40googlegroups.com</a>.<br>
</div></blockquote></div><br></div></div></blockquote></div><div><br class="webkit-block-placeholder"></div>
-- <br>
You received this message because you are subscribed to the Google Groups "chibolts" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:chibolts+unsubscribe@googlegroups.com">chibolts+unsubscribe@googlegroups.com</a>.<br>
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/chibolts/a871e343-d13d-4312-a964-a4428448dce9n%40googlegroups.com?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/chibolts/a871e343-d13d-4312-a964-a4428448dce9n%40googlegroups.com</a>.<br>
</div></blockquote></div><br></div></body></html>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups "chibolts" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:chibolts+unsubscribe@googlegroups.com">chibolts+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/chibolts/ED2AC3C0-4584-49C1-8FE0-CAC0F8CE63CD%40andrew.cmu.edu?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/chibolts/ED2AC3C0-4584-49C1-8FE0-CAC0F8CE63CD%40andrew.cmu.edu</a>.<br />