Esc +L and [mor- xb] Not Picking Up Errors

[Sophie Brook]

Thank you for your swift and helpful response! 


*Yes you have understood correctly :) *
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). 

*Question 1*
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)?

*Question 2*
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? 

*Question 3*
Is there a difference between the code you've typed (freq +s"[\* *]") and 
the one I typed freq +s"\[\* *\]" +t*PAR * +d2 ?

Thanks. 

Sophie
(she/her/hers) 

On Wednesday, October 2, 2024 at 12:22:58 PM UTC+1 Leonid Spektor wrote:

> Hi Sophie,
>
> 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?
>
> 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.
>
> 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.
>
>
>
> Leonid. 
>
> On Oct 2, 2024, at 06:51, Sophie Brook <sophiem... at gmail.com> wrote:
>
> Hi there, 
>
> *What I did*
> I used this code: 
>
> freq +s"\[\* *\]" +t*PAR * +d2
>
> to output frequencies of different errors e.g., phonological [* p:w] [* 
> p:n] , morphological, semantic and neologisms etc etc 
>
> *The problem*
>
> 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. 
>
> I have been manually changing the CHAT files after combing through the 
> columns to see which transcriptions have found these "illegal error codes". 
>
>
> *Question *
>
> Why is this happening?
>
> Is there a way around this?
>
>
>
>
> Thank you!!! :) 
>
> Best, 
>
> Sophie Brook 
>
> (she/her) 
>
>
>
>
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "chibolts" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to chibolts+u... at googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/chibolts/ae6e75f8-9e56-4e2c-9f55-82d1fc59bee3n%40googlegroups.com 
> <https://groups.google.com/d/msgid/chibolts/ae6e75f8-9e56-4e2c-9f55-82d1fc59bee3n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "chibolts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chibolts+unsubscribe at googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chibolts/a871e343-d13d-4312-a964-a4428448dce9n%40googlegroups.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.linguistlist.org/pipermail/chibolts/attachments/20241003/342e284e/attachment-0001.htm>