#1759 Obadiah 1:9 - Abstract Noun, Possible Error in tC Menu Column

Open
opened 2 months ago by ghayden · 1 comments
ghayden commented 2 months ago
Owner

While doing the tools check for Obadiah, Oba 1:9 appears twice in the Menu column in tC under "Abstract Nouns" when there is only one abstract noun in that verse.

Please check the attached screenshot "tC_tN_Oba_ch_1_verse_9.PNG"

I checked on this with @Grant_Ailie and Grant mentioned the following:

This looks like an error in the tC menu column because after looking at the Hebrew text of OBA 1:9 I see that there is only one occurrence of an abstract noun in OBA 1:9, so the the highlighting is correct in only highlighting the one Hebrew word and so I don't think the menu should display 2 occurrences of 1:9.

@richmahn provided the following info:

According to the entn repo for Obadiah, this is correct in two abstrauct nouns. This where he can make an issue, but according to the seoncd abstrauctnoun, it is referring to a noun that can also be in the v10, violence: https://git.door43.org/unfoldingWord/en_tn/blame/branch/master/en_tn_31-OBA.tsv#L71

But it is odd that it then references the same Hebrew word, and same occurrence, thus maybe confusing the checker. An issue can be made here: https://git.door43.org/unfoldingWord/en_tn/issues/new

Please advise if it is expected for Obadiah 1:9 to appear twice simultaneously under Menu > Abstract Nouns in tC

Thank you!

While doing the tools check for Obadiah, Oba 1:9 appears twice in the Menu column in tC under "Abstract Nouns" when there is only one abstract noun in that verse. Please check the attached screenshot "tC_tN_Oba_ch_1_verse_9.PNG" I checked on this with @Grant_Ailie and Grant mentioned the following: > *This looks like an error in the tC menu column because after looking at the Hebrew text of OBA 1:9 I see that there is only one occurrence of an abstract noun in OBA 1:9, so the the highlighting is correct in only highlighting the one Hebrew word and so I don't think the menu should display 2 occurrences of 1:9.* @richmahn provided the following info: > *According to the entn repo for Obadiah, this is correct in two abstrauct nouns. This where he can make an issue, but according to the seoncd abstrauctnoun, it is referring to a noun that can also be in the v10, violence:* https://git.door43.org/unfoldingWord/en_tn/blame/branch/master/en_tn_31-OBA.tsv#L71 > > *But it is odd that it then references the same Hebrew word, and same occurrence, thus maybe confusing the checker. An issue can be made here:* https://git.door43.org/unfoldingWord/en_tn/issues/new Please advise if it is expected for Obadiah 1:9 to appear twice simultaneously under Menu > Abstract Nouns in tC Thank you!
ghayden added the
bug
label 2 months ago
ghayden commented 3 days ago
Poster
Owner

Based on the information from Chris Kosieracki and Birch:

The issue reported here is a limitation in tCore. When the same original language word has more than one reference to the same category/figure of speech in tN, then tCore is unable to distinguish between the references. This can occur for any language and not necessarily for Russian. Please note that this might occur more as the tNotes become more extensive. From a tools perspective, identical checks (i.e. two or more tNotes checks with the same category and same original language word) with different identifiers should be treated as separate tN checks. This limitation in tCore would not be addressed in tCore anytime soon.

Based on the information from Chris Kosieracki and Birch: The issue reported here is a limitation in tCore. When the same original language word has more than one reference to the same category/figure of speech in tN, then tCore is unable to distinguish between the references. This can occur for any language and not necessarily for Russian. Please note that this might occur more as the tNotes become more extensive. From a tools perspective, identical checks (i.e. two or more tNotes checks with the same category and same original language word) with different identifiers should be treated as separate tN checks. This limitation in tCore would not be addressed in tCore anytime soon.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.