See in Reader
193 lines
20 KiB
ReStructuredText
193 lines
20 KiB
ReStructuredText
:github_url: https://git.door43.org/unfoldingWord/en_glm/src/branch/master/docs/gl_checking.rst
|
|
|
|
.. _glchecking:
|
|
|
|
Gateway Language Checking
|
|
=========================
|
|
|
|
.. _glchecking-checkingult:
|
|
|
|
Checking the GLT
|
|
----------------
|
|
|
|
.. note:: This module answers the question, "What are the guidelines for checking the Gateway Language Literal Text (GLT)?"
|
|
|
|
.. seealso:: :ref:`gltranslation-transult`, :ref:`gltranslation-adaptult`, :abbr:`TA (translationAcademy)` module `Steps in Checking a Translation <https://door43.org/u/unfoldingWord/en_ta/master/04-checking.html#vol2-steps>`_, :abbr:`TA (translationAcademy)` module `Things to Check <https://door43.org/u/unfoldingWord/en_ta/master/04-checking.html#vol2-things-to-check>`_
|
|
|
|
When checking the :abbr:`GLT (Gateway Language Literal Text)`, remember that the :abbr:`GLT (Gateway Language Literal Text)` needs to retain the original grammatical forms (as far as possible), the idioms, and the figures of speech of the original so that the :abbr:`OL (Other Language)` translator can consider them and use them if they communicate the right thing in the target language. If those forms get changed in a :abbr:`GL (Gateway Language)` translation of the :abbr:`ULT (unfoldingWord Literal Text)`, then the :abbr:`OL (Other Language)` translator will never see them and the notes about them will not make sense.
|
|
|
|
When you are checking the :abbr:`GL (Gateway Language)` translation of the :abbr:`ULT (unfoldingWord Literal Text)`, you must only compare it to the English :abbr:`ULT (unfoldingWord Literal Text)`. Do not refer to any other version of the Bible when checking the :abbr:`ULT (unfoldingWord Literal Text)`. The :abbr:`GL (Gateway Language)` translation of the :abbr:`ULT (unfoldingWord Literal Text)` may not be as smooth and clear as the :abbr:`GL (Gateway Language)` Bible that you are used to, because it is showing the :abbr:`OL (Other Language)` translator the forms of the original biblical languages. Please do not try to make the :abbr:`GLT (Gateway Language Literal Text)` sound like your favorite translation of the Bible in your language.
|
|
|
|
What Should Be Checked in the GLT?
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
.. include:: /includes/typesofthingstocheck.txt
|
|
|
|
#. **Idioms** - If there is an idiom in the source :abbr:`ULT (unfoldingWord Literal Text)`, then that same idiom should be in the target :abbr:`GLT (Gateway Language Literal Text)`. If the idiom does not make sense in the target language, make sure that there is a note that explains its meaning. If there is not a note for it, then write one in the :abbr:`GL (Gateway Language)` :abbr:`TN (translationNotes)` that explains its meaning.
|
|
#. **Figures of Speech** - If there is a figure of speech in the source :abbr:`ULT (unfoldingWord Literal Text)`, then that same figure of speech should be in the target :abbr:`GLT (Gateway Language Literal Text)`. If the figure of speech does not make sense in the target language, make sure that there is a note that explains its meaning. If there is not a note for it, then write one in the :abbr:`GL (Gateway Language)` :abbr:`TN (translationNotes)` that explains its meaning.
|
|
#. **Grammatical Forms** - Check to see if the grammatical form, that is, the order of words in the sentence or the way that the words are arranged, is the same in the target GLT as they are in the English source :abbr:`ULT (unfoldingWord Literal Text)`. If the words are arranged differently, ask yourself if they could be arranged the same as the words in the English :abbr:`ULT (unfoldingWord Literal Text)` and still make good sense, or if it is necessary for them to be arranged in a different way in the GLT. If they would still make good sense in a way that an Other Language translator would understand, then put them in the same arrangement as in the English. This is because the English :abbr:`ULT (unfoldingWord Literal Text)` is attempting to reproduce the grammar of the original, as much as possible, so that the :abbr:`OL (Other Language)` translator can see it. But if the words are in a different arrangement because that is what makes sense in the target :abbr:`GL (Gateway Language)`, then leave them in the different arrangement.
|
|
|
|
What Should Not Be Checked in the GLT?
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
It is not necessary to check the :abbr:`GLT (Gateway Language Literal Text)` for naturalness with speakers of the :abbr:`GL (Gateway Language)`. The :abbr:`GLT (Gateway Language Literal Text)` will not be natural in some cases because it is designed to retain the forms of the biblical languages, as far as the :abbr:`GL (Gateway Language)` allows.
|
|
|
|
.. seealso:: :ref:`gltranslation-transtn`, :ref:`glchecking-checkingtn`, :ref:`glchecking-checkingust`
|
|
|
|
.. _glchecking-checkingust:
|
|
|
|
Checking the GST
|
|
----------------
|
|
|
|
.. note:: This module answers the question, "What are the guidelines for checking the GST (Gateway Language Simplified Text)?"
|
|
|
|
.. seealso:: :ref:`gltranslation-transust`, :abbr:`TA (translationAcademy)` module `Steps in Checking a Translation <https://door43.org/u/unfoldingWord/en_ta/master/04-checking.html#vol2-steps>`_, :abbr:`TA (translationAcademy)` module `Things to Check <https://door43.org/u/unfoldingWord/en_ta/master/04-checking.html#vol2-things-to-check>`_
|
|
|
|
When checking the :abbr:`GST (Gateway Language Simplified Text)`, remember that the :abbr:`GST (Gateway Language Simplified Text)` does not use figures of speech, idioms, abstract nouns, or grammatical forms that are difficult to translate into many languages. The purpose of the :abbr:`GST (Gateway Language Simplified Text)` is to change all of these problematic grammatical forms into more universal ones to make them easier to translate, and to make the meaning as clear as possible.
|
|
|
|
When you are checking the :abbr:`GL (Gateway Language)` translation of the :abbr:`UST (unfoldingWord Simplified Text)`, you must only compare it to the English :abbr:`UST (unfoldingWord Simplified Text)`. Do not refer to any other version of the Bible when checking the :abbr:`GST (Gateway Language Simplified Text)`. The :abbr:`GL (Gateway Language)` translation of the :abbr:`UST (unfoldingWord Simplified Text)` may not be as smooth and natural as the :abbr:`GL (Gateway Language)` Bible that you are used to, because it does not use many of the forms of expression that make a language sound natural. These forms of expression are different for every language. So please do not try to make the :abbr:`GST (Gateway Language Simplified Text)` sound like your favorite translation of the Bible in your language.
|
|
|
|
What Should Be Checked in the GST?
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
.. include:: /includes/typesofthingstocheck.txt
|
|
|
|
#. **Sentence length** - If you see any long or complex sentences in the :abbr:`GST (Gateway Language Simplified Text)`, see how you might break them up into shorter sentences.
|
|
#. **Passive voice** - If you see a passive voice construction in the :abbr:`GST (Gateway Language Simplified Text)`, check to see what it was in the English source :abbr:`UST (unfoldingWord Simplified Text)` and change it so that it is active.
|
|
#. **Abstract Nouns** - If you see an abstract noun in the :abbr:`GST (Gateway Language Simplified Text)`, check to see what it was in the English source :abbr:`UST (unfoldingWord Simplified Text)` and change the abstract noun back to an action or description word.
|
|
#. **Events out of order** - Make sure that the events in your :abbr:`GST (Gateway Language Simplified Text)` are in the order that they occurred. Also make sure that the logical flow of arguments, such as occur in many of the New Testament letters, is in a natural order that makes sense in the :abbr:`GL (Gateway Language)`.
|
|
#. **Figures of speech and idioms** - Make sure that the :abbr:`GST (Gateway Language Simplified Text)` does not contain any figures of speech or idioms. Instead, it should use only plain, clear language.
|
|
|
|
If you see any of these forms in the English :abbr:`UST (unfoldingWord Simplified Text)`, email <help@door43.org> to let them know of the error.
|
|
|
|
It is also useful to check the :abbr:`GST (Gateway Language Simplified Text)` for clarity with speakers of the :abbr:`GL (Gateway Language)`, but do not confuse clarity with naturalness (see below). You can read a passage from the :abbr:`GST (Gateway Language Simplified Text)` to a speaker of the :abbr:`GL (Gateway Language)` and ask if the meaning is clear. If they say, "Yes," that is enough. If they also say, "But I would say it differently," that is fine. We expect that they would say it differently. But the :abbr:`GST (Gateway Language Simplified Text)` needs to say it in a plain way. As long as the meaning of the :abbr:`GST (Gateway Language Simplified Text)` is clear, it is a successful translation.
|
|
|
|
.. seealso:: :ref:`gltranslation-transust`
|
|
|
|
What Should Not Be Checked in the GST?
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
It is not necessary to check the :abbr:`GST (Gateway Language Simplified Text)` for naturalness with speakers of the :abbr:`GL (Gateway Language)`. The :abbr:`GST (Gateway Language Simplified Text)` will very often not be completely natural because it avoids some forms that languages naturally use such as idioms and figures of speech. The :abbr:`GST (Gateway Language Simplified Text)` must avoid these because they are specific to individual languages and do not translate well from one language to another.
|
|
|
|
.. seealso:: :ref:`gltranslation-transtn`, :ref:`glchecking-checkingtn`
|
|
|
|
.. _glchecking-checkingtn:
|
|
|
|
Checking the GL translationNotes (GTN)
|
|
-------------------------
|
|
|
|
.. note:: This module answers the question, "What are the guidelines for checking the GL translationNotes?"
|
|
|
|
.. seealso:: :ref:`gltranslation-transtn`, :abbr:`TA (translationAcademy)` module `Steps in Checking a Translation <https://door43.org/u/unfoldingWord/en_ta/master/04-checking.html#vol2-steps>`_, :abbr:`TA (translationAcademy)` module `Things to Check <https://door43.org/u/unfoldingWord/en_ta/master/04-checking.html#vol2-things-to-check>`_
|
|
|
|
When checking :abbr:`GTN (Gateway Language translationNotes)`, remember that :abbr:`GTN (Gateway Language translationNotes)` are very closely tied to the text of the :abbr:`GLT (Gateway Language Literal Text)`. The purpose of :abbr:`GTN (Gateway Language translationNotes)` is to explain any phrases or sentences in the :abbr:`GLT (Gateway Language Literal Text)` that are hard to understand or hard to translate.
|
|
|
|
What Should Be Checked?
|
|
^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
.. include:: /includes/typesofthingstocheck.txt
|
|
|
|
#. Make sure that the phrase in each note that translates the phrase from the English :abbr:`ULT (unfoldingWord Literal Text)` is exactly the same as the corresponding phrase in its translation in the Gateway Language Literal Text (GLT). In other words, the phrase in the :abbr:`GL (Gateway Language)` Notes must quote the phrase from the GLT accurately. The words must be exactly the same.
|
|
#. Check the meaning of the note in the English UTN and make sure that the :abbr:`GTN (Gateway Language translationNotes)` has the same meaning.
|
|
#. In the same way, make sure that any quotations of the :abbr:`GST (Gateway Language Simplified Text)` have the exact wording of the :abbr:`GST (Gateway Language Simplified Text)`.
|
|
#. Check that the :abbr:`GTN (Gateway Language translationNotes)` makes sense with the GLT. It is possible that the :abbr:`GL (Gateway Language)` translator made a good translation of the English UTN but when the note is read with the new GLT, it might not explain the GLT in the right way, or it might not make sense with the GLT. In that case, you will need to discuss the problem with the translator. Then you will need to decide how to change the note so that it explains the GLT in a way that will be helpful to the :abbr:`OL (Other Language)` translator.
|
|
#. Check that all references in the Notes to the :abbr:`GST (Gateway Language Simplified Text)` make sense when read with the GST.
|
|
#. If the :abbr:`GL (Gateway Language)` translator has decided that a note does not apply to the GLT and has deleted the note from the :abbr:`GTN (Gateway Language translationNotes)`, check to make sure that the note was not needed.
|
|
#. If the :abbr:`GL (Gateway Language)` translator has written a new note, check to make sure that it was needed, and that it makes sense with the GLT.
|
|
|
|
In order to check the :abbr:`GTN (Gateway Language translationNotes)` for naturalness and clarity, you will need to have people read them together with the :abbr:`GLT (Gateway Language Literal Text)` and :abbr:`GST (Gateway Language Simplified Text)`. Then ask them to mark anything that is not clear to them, or that they would say in a different way. Then give this feedback to the translator so that he can make those places clearer and more natural.
|
|
|
|
.. seealso:: :ref:`gltranslation-transtn`, :ref:`glchecking-checkingult`, :ref:`glchecking-checkingust`
|
|
|
|
.. _glchecking-finishingchecking:
|
|
|
|
Finishing Checking
|
|
------------------
|
|
|
|
.. note:: This module answers the question, "How do I know when I have finished checking the GL resources?"
|
|
|
|
.. seealso:: :ref:`gltranslation-whatneedstrans`, :abbr:`TA (translationAcademy)` module `Steps in Checking a Translation <https://door43.org/u/unfoldingWord/en_ta/master/04-checking.html#vol2-steps>`_, :abbr:`tA (translationAcademy)` module `Things to Check <https://door43.org/u/unfoldingWord/en_ta/master/04-checking.html#vol2-things-to-check>`_
|
|
|
|
It can be difficult to know when you have sufficiently checked a text for errors or for ways that it could be improved. In a sense, this process is never completely finished, and people continually find ways to improve texts that have been checked already by many people. For example, there are many Bible translations in English that have been checked by many biblical scholars and are considered to be excellent translations. Yet it is possible to find places where they could be made better, and over time, they are continually revised, and new versions are published. This is the process that you should expect to happen with these Bible translations as well.
|
|
|
|
Checking Evaluation Lists
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
The following lists can help you to consider whether or not you have checked a :abbr:`GL (Gateway Language)` resource sufficiently.
|
|
|
|
For the Translator
|
|
""""""""""""""""""
|
|
* Review the guidelines for translation of the specific materials in the Gateway Language Manual. Make sure that you have translated the material according to those guidelines. Correct anything that does not conform.
|
|
* Carefully compare your translation with the source text. Correct any inaccuracies.
|
|
* Read the resource that you have translated alongside the related resources, either in English or, if they have been translated, in the :abbr:`GL (Gateway Language)`. Make sure that the resources are clear and make good sense together. The GLT and GST should be read alongside each other, the Notes, Words, and Questions alongside the GLT and GST.
|
|
* Submit your translation for review by a partner on the translation team.
|
|
|
|
|
|
For the Translation Team
|
|
""""""""""""""""""""""""
|
|
* Review and discuss the resource together as a team, comparing it to the source
|
|
* Check the GLT and the GST with the English Words and Notes checks in translationCore
|
|
* Check the GLT for accuracy and literalness with the aligning tool
|
|
* Check the GST for completeness with the aligning tool
|
|
* Check the :abbr:`GL (Gateway Language)` Notes and :abbr:`GL (Gateway Language)` Words by reading them with the GLT and GST. Improve anything that is not clear or not helpful.
|
|
|
|
|
|
For the Broader Translation Oversight Committee
|
|
"""""""""""""""""""""""""""""""""""""""""""""""
|
|
* After orienting a group of pastors (preferably representing various denominations) to the goals and guidelines of the :abbr:`GL (Gateway Language)` resources, assign them to review the resources, especially the GLT and GST.
|
|
* When they are satisfied with the resources, have them communicate this by affirming the following:
|
|
|
|
* the translation conforms to the Statement of Faith (see http://ufw.io/faith/) and Translation Guidelines (see http://ufw.io/guidelines/)
|
|
* the translation accurately communicates the content of the source document in the target language
|
|
* the style of the translation conforms to the guidelines set forth for translation of this resource in the Gateway Language Manual
|
|
* the translation team has edited the Translation to their satisfaction
|
|
* Arrange for Bible scholars to review the alignments of the GLT and GST with the original biblical languages.
|
|
* Arrange for leaders of different church networks or denominations to review the :abbr:`GL (Gateway Language)` resources and affirm the validity and usefulness of the resources. This works best if they have been involved in the project from the beginning and know and trust those who have done the work.
|
|
|
|
|
|
Additional questions that can help you to evaluate if the translation has been sufficiently checked are in the :abbr:`TA (translationAcademy)` module `Self-Assessment Rubric <https://door43.org/u/unfoldingWord/en_ta/master/04-checking.html#self-assessment>`_. Just be aware that the :abbr:`ULT (unfoldingWord Literal Text)` and the :abbr:`UST (unfoldingWord Simplified Text)` are not intended to be completely natural in the :abbr:`GL (Gateway Language)`. (Again, this is not intended to be and "end-user Bible.")
|
|
|
|
The most rigorous testing of your work will come when :abbr:`OLs (Other Languages)` teams begin to use it for Bible translation. Be prepared to make many more corrections at that time!
|
|
|
|
.. seealso:: :abbr:`TA (translationAcademy)` module `Self-Assessment Rubric <https://door43.org/u/unfoldingWord/en_ta/master/04-checking.html#self-assessment>`_
|
|
|
|
Source Text Creation
|
|
--------------------
|
|
|
|
.. note:: This module answers the question, "How do I make my Gateway Language translation a source text?"
|
|
|
|
Source Text Process
|
|
^^^^^^^^^^^^^^^^^^^
|
|
|
|
Source text publishing is required for all Gateway Languages so that they can be used as source texts by Other Languages. Note that this process only applies to Gateway Languages.
|
|
|
|
Prerequisites
|
|
"""""""""""""
|
|
|
|
Before a Gateway Language translation can become a source text, the following prerequisites must all be met:
|
|
|
|
* **Whole Resource** - The whole resource (a whole book) must have completed the [Translation and Checking Process](../translation-overview/01.md). Parts of resources (e.g. half of the Open Bible Stories, only a few chapters of a book of the Bible) cannot be published.
|
|
* **Checking** - A translation must have been put through the checking process and been validated by Gateway Language church leadership. See [Validation Checking](../../checking/level3/01.md).
|
|
* **On Door43** - Door43 must have the version that will be published. If the work was done on multiple devices, then it may need to be merged together. Get the help of a Content Tech to make merging easier (either email <help@door43.org> or start a conversation on the [Door43 Forum](https://forum.door43.org)).
|
|
* **Agreements** - Everyone involved in the translation and checking must have agreed to the [Statement of Faith](../../intro/statement-of-faith/01.md), the [Translation Guidelines](../../intro/translation-guidelines/01.md), and the [Open License](../../intro/open-license/01.md). Attesting to agreement can be done by either creating Door43 accounts or by physically signing the documents, digitizing them (scanning or photos), and submitting them as explained below. See http://ufw.io/forms for downloadable agreement forms.
|
|
|
|
|
|
Source Text Request Form
|
|
""""""""""""""""""""""""
|
|
|
|
Once you have completed the prerequisites, you may fill out the source text request form at http://ufw.io/pub/. A few notes about the form:
|
|
|
|
* You must have a Door43 account to create a request.
|
|
* You must include the names or pseudonyms of everyone involved. You must also include their Door43 usernames if you are not attaching signed license agreements for them.
|
|
* Note that the information you enter will be public and will become a part of the front matter of the source text.
|
|
|
|
After your form has been submitted, you will be contacted if anything is missing. Once the request has been approved, it will go into the publishing queue where a developer will work to make the translation a source text. You may also be contacted by the developer if there are any issues encounted during the publishing process. You will be notified when the process is completed, and you may review a PDF of the work.
|
|
|
|
Finishing the Source Text Process
|
|
"""""""""""""""""""""""""""""""""
|
|
After the source text publishing process is completed, your work will then be available:
|
|
|
|
* Online on the unfoldingWord website
|
|
* As a PDF, downloadable from unfoldingWord
|
|
* In translationStudio as a source text for Other Languages to use (may require a tS update first)
|