Custom (Blank) Checking Tool

[cckozie]

No description provided.

[jag3773]

Idea from April meetup:

[jag3773]

For a TSV format to support lots of different things, here is what I'm thinking for columns:

• Book - USFM book code name (e.g. TIT)
• Chapter - Chapter number (e.g. 01)
• Verse - Verse number (e.g. 03)
• ID - Four character alphanumeric string unique within the verse for the resource (e.g. a8n4)
• SupportReference - A link to a supporting reference text to show in the helps pane.
  • This should be an RC link to an existing resource (e.g. rc://en/ta/man/translate/figs-metaphor)
  • Possibly allow the SupportReference text to be provided in a separate Markdown file with the TSV?
• OrigQuote - Original language quote (e.g. ἐφανέρωσεν ... τὸν λόγον αὐτοῦ)
  • tC uses this for highlighting
  • An elipsis (...) indicates that the quote is discontinuous, software should interpret this in a non-greedy manner
• Occurrence - Specifies which occurrence in the original language text the entry applies to.
  • -1: entry applies to every occurrence of OrigQuote in the verse
  • 1: entry applies to first occurrence of OrigQuote only
  • 2: entry applies to second occurrence of OrigQuote only
  • etc.
• GLQuote (OPTIONAL) - Gateway language quote (e.g. he revealed his word)
  • tC will not use this field
  • Possibly rework so that this can be used instead of OrigQuote?
• OccurrenceNote (OPTIONAL) - Paul speaks of God's message as if it were an object that could be visibly shown to people. AT: "He caused me to understand his message"
  • Max character limit of 250?
  • If provided, will show up as a checking note for this check occurrence

---

I think that the above accounts for our use cases in tN and tW. Any thoughts @benjore or @klappy or others?

It may need some further refinement to allow for broader use, in particular the requirement of the OrigQuote might be too stringent?