Go to file
larrysallee dbe2f5f73c Edit 'tq_JAS.tsv' using 'tc-create-app' 2024-06-06 16:16:24 +00:00
.github Small syntax fixes for v19 (#61) 2020-12-10 04:55:25 +00:00
.gitignore Add missing end breaks (#25) 2020-01-15 19:50:15 +00:00
LICENSE.md Version 30 (#108) 2022-03-19 20:08:18 +00:00
README.md Fixed punctuation in 1Co answer, and removed dead link from README (#96) 2021-11-18 14:36:15 +00:00
manifest.yaml Version 38 2022-10-11 23:01:20 +00:00
media.yaml Version 30 (#108) 2022-03-19 20:08:18 +00:00
tq_1CH.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_1CO.tsv Corrected questions and answers for 1 Corinthians 2022-12-13 11:30:39 -05:00
tq_1JN.tsv Removed stay line breaks 2024-06-05 11:15:15 -04:00
tq_1KI.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_1PE.tsv Removed stay line breaks 2024-06-05 11:15:15 -04:00
tq_1SA.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_1TH.tsv Removed stay line breaks 2024-06-05 11:15:15 -04:00
tq_1TI.tsv Removed stay line breaks 2024-06-05 11:15:15 -04:00
tq_2CH.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_2CO.tsv Edit 'tq_2CO.tsv' using 'tc-create-app' 2022-12-27 16:15:04 +00:00
tq_2JN.tsv Edit 'tq_2JN.tsv' using 'tc-create-app' 2024-03-08 16:49:32 +00:00
tq_2KI.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_2PE.tsv Removed stay line breaks 2024-06-05 11:15:15 -04:00
tq_2SA.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_2TH.tsv Edit 'tq_2TH.tsv' using 'tc-create-app' 2024-05-31 20:21:21 +00:00
tq_2TI.tsv Removed stay line breaks 2024-06-05 11:15:15 -04:00
tq_3JN.tsv Edit 'tq_3JN.tsv' using 'tc-create-app' 2024-03-08 16:48:07 +00:00
tq_ACT.tsv Applied Jane's proofreading suggestions to Acts 2022-10-12 15:41:21 -04:00
tq_AMO.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_COL.tsv Removed stay line breaks 2024-06-05 11:15:15 -04:00
tq_DAN.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_DEU.tsv Edit 'tq_DEU.tsv' using 'tc-create-app' 2022-08-25 19:01:07 +00:00
tq_ECC.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_EPH.tsv Edit 'tq_EPH.tsv' using 'tc-create-app' 2024-04-24 14:12:35 +00:00
tq_EST.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_EXO.tsv Corrected questions numbering in Exodus 2022-06-27 10:54:46 -04:00
tq_EZK.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_EZR.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_GAL.tsv Removed stay line breaks 2024-06-05 11:15:15 -04:00
tq_GEN.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_HAB.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_HAG.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_HEB.tsv Applied Jane's proofreading suggestions to Hebrews 2022-11-18 11:23:47 -05:00
tq_HOS.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_ISA.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_JAS.tsv Edit 'tq_JAS.tsv' using 'tc-create-app' 2024-06-06 16:16:24 +00:00
tq_JDG.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_JER.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_JHN.tsv Fixed verse range in John 18 2022-08-18 10:04:29 -04:00
tq_JOB.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_JOL.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_JON.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_JOS.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_JUD.tsv Edit 'tq_JUD.tsv' using 'tc-create-app' 2024-03-08 16:44:32 +00:00
tq_LAM.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_LEV.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_LUK.tsv Corrected straight punctuation marks in Luke (#94) 2021-09-29 16:29:24 +00:00
tq_MAL.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_MAT.tsv Corrections to Matthew TQ's 2022-10-11 13:22:13 -04:00
tq_MIC.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_MRK.tsv Removed stay line breaks 2024-06-05 11:15:15 -04:00
tq_NAM.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_NEH.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_NUM.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_OBA.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_PHM.tsv Removed stay line breaks 2024-06-05 11:15:15 -04:00
tq_PHP.tsv Removed stay line breaks 2024-06-05 11:15:15 -04:00
tq_PRO.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_PSA.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_REV.tsv Edit 'tq_REV.tsv' using 'tc-create-app' 2023-01-18 17:28:51 +00:00
tq_ROM.tsv Edit 'tq_ROM.tsv' using 'tc-create-app' 2022-12-17 19:52:15 +00:00
tq_RUT.tsv Jane's edits to RUT (#156) 2023-02-16 22:03:10 +00:00
tq_SNG.tsv Corrected two notes in Song of Songs 2022-09-12 09:33:01 -04:00
tq_TIT.tsv Edit 'tq_TIT.tsv' using 'tc-create-app' 2024-04-24 13:35:56 +00:00
tq_ZEC.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00
tq_ZEP.tsv Version 27 converted from markdown (#92) 2021-09-29 00:13:50 +00:00

README.md

UTQ Logo

unfoldingWord® Translation Questions

This is the repository for the unfoldingWord® Translation Questions (UTQ) resource.

Description

unfoldingWord® Translation Questions are comprehension and theological questions for each chapter of the Bible. It enables translators and translation checkers to confirm that the intended meaning of their translations is clearly communicated to the speakers of that language.

Downloading

If you want to download the UTQ to use, go here: https://www.unfoldingword.org/utq/. The UTQ are included in tS and will soon be in tC.

Improving the tQs

Please use the issue queue to provide feedback or suggestions for improvement.

If you want to make your suggested changes then you may use the online editor to do so. See the protected branch workflow document for step by step instructions.

Editing the UTQ

To edit the UTQ files there are three options:

  • Use LibreOffice (Recommended)
  • Use a text editor on your computer
  • Use the online web editor in DCS

Each of these options and their caveats are described below.

The first two options require you to clone the repository to your computer first. You may do this on the command line or using a program such as SmartGit. After making changes to the files you will need to commit and push your changes to the server and then create a Pull Request to merge them to the master branch.

Alternately, you may download the master branch as a zip file and extract that locally. After editing you would need to use the upload file feature in DCS to get your changes ready for a Pull Request.

Editing in LibreOffice

This is the recommended way to edit the TSV files. You may download LibreOffice for free.

After you have the file on your computer, you may open the respective TSV file with LibreOffice. Follow these notes on the Text Import Screen:

  • Set “Separated by” to “Tab”
  • Set “Text Delimiter” to blank, you will need to highlight the character and use backspace or delete to remove it

When you are done editing, click Save and then select “Use Text CSV Format” on the pop up dialogue. Note that even though it says CSV, it will use tab characters as the field separators.

Note: Other spreadsheet editors should not be used because they will add or remove quotation marks which will affect the notes negatively.

Editing in a Text Editor

You may also use a regular text editor to make changes to the files.

Note: You must be careful not to delete or add any tab characters when editing with this method.

Editing in DCS

If you only need to change a word or two, this may be the quickest way to make your change. See the protected branch workflow document for step by step instructions.

Note: You must be careful not to delete any tab characters when editing with this method.

Structure

The UTQ are structured as TSV files to simplify importing and exporting into various formats for translation and presentation.

TSV Format Overview

A Tab Separated Value (TSV) file is like a Comma Separated Value file except that the tab character is what divides the values instead of a comma. This makes it easier to include prose text in the files because many languages require the use of commas, single quotes, and double quotes in their sentences and paragraphs.

The UTQ are structured as one file per book of the bible and encoded in TSV format, for example, tq_GEN.tsv. The columns are Reference, ID, Tags, Quote, Occurrence, Question, and Response.

UTQ TSV Column Description

The following lists each column with a brief description and example.

  • Reference: Chapter number (e.g. 1) then colon then verse number (e.g. 3) or intro
  • ID: Four character alphanumeric string unique within the verse for the resource (e.g. swi9)
    • This will be helpful in identifing which notes are translations of the original English tQs and which notes have been added by GLs.
    • The Universal ID (UID) of a note is the combination of the Book, Chapter, Verse, and ID fields. For example, tit/1/3/swi9.
      • This is a useful way to unambiguously refer to notes.
      • An RC link can resolve to a specific note like this: rc://en/tq/help/tit/01/01/swi9.
  • Tags: not currently used for Translation Questions
  • Quote: currently only used for OBS Translation Questions
  • Occurrence: Specifies which occurrence in the original language text the entry applies to.
    • -1: entry applies to every occurrence of Quote in the verse
    • 0: entry does not occur in original language (for example, “Connecting Statement:”)
    • 1: entry applies to first occurrence of Quote only
    • 2: entry applies to second occurrence of Quote only
    • etc.
  • Question: The character Markdown formatted question.
  • Response: Optional character Markdown formatted response.
    • The Question and Response text should only be characters Markdown formatted, which means the following are also acceptable:
      • Plaintext—if you have no need for extra markup, just use plain text in this column
      • HTML—if you prefer to use inline HTML for markup, that works because it is supported in Markdown
      • No paragraph Markdown formats

GL Translators

UTQ Translation Philosophy

To learn the philosophy of how to translate the UTQs please see the Translate the unfoldingWord® Translation Questions article in the Gateway Language Manual.

If you are translating online, please fork the Door43-Catalog/en_tq repository, following this workflow: Translate Content Online.

License

See the LICENSE file for licensing information.