Perry J Oakes
||1 day ago|
|checking||11 months ago|
|intro||2 years ago|
|process||11 months ago|
|translate||1 day ago|
|.gitignore||2 years ago|
|LICENSE.md||1 year ago|
|README.md||2 years ago|
|manifest.yaml||2 months ago|
|media.yaml||1 year ago|
unfoldingWord® Translation Academy
unfoldingWord® Translation Academy (UTA) is a modular handbook that provides a condensed explanation of Bible translation and checking principles that the global church has implicitly affirmed define trustworthy translations. It enables translators to learn how to create trustworthy translations of the Bible in their own language.
If you want to download unfoldingWord® Translation Academy to use, go here: https://www.unfoldingword.org/uta. UTA is also included in tS and tC.
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.
UTA is written in a simple Markdown format and organized according to the Resource Container Manual type. See that link for more information but here is a quick summary.
Each manual has its own directory in this repository (for example, the Checking Manual is in the checking directory). Each module has its own directory inside of these manual directories. Inside each of these are three files:
01.md— This is the main body of the module
sub-title.md— This file contains the question that the module is intended to answer.
title.md— This contains the title of the module
There are also YAML formatted files in each manual’s directory. The
toc.yaml file is for encoding the Table of Contents and the
config.yaml file is for encoding dependencies between the modules.
UTA Translation Philosophy
To learn the philosophy of how to translate the UTA please see the Translate unfoldingWord® Translation Academy article in the Gateway Language Manual.
NOTE: The Bible was originally written in Hebrew, Aramaic, and Greek. In these languages, masculine pronouns and terms can apply to both men and women. The same is true in English, and in this manual we often use masculine terms to refer to both men and women. For example, in this manual we often use masculine pronouns to refer to people like you (and other translators) who will use this manual. But we do not intend to say that only men can use this manual or to say that only men can translate the Bible. We are simply using masculine terms to refer to both men and women.
If you are translating online, please fork the Door43-Catalog/en_ta repository, following this workflow: Translate Content Online.
Technical Information for Translating UTA
- Do not rename any files or directories. Only translate what is inside the files.
toc.yamlfiles do not need to be changed unless you add a new module. When you are finished translating, you may want to update the
titlefields in the
toc.yamlfile, but you shouldn’t make any other changes in those files.
- Images that are included in UTA should be no more than 600px wide. NOTE: If you use the images already in UTA, you do not need to translate the names of the image files. They will work in their current format.
- Hyperlinks (links to other articles or to other pages on the internet) follow this pattern:
[text to display](https://www.example.com). You can translate the “text to display” inside the square brackets but not the web address that follows inside the parentheses.
You are free to add additional modules. In order for the new modules to be included, all of the following conditions need to be satisfied:
- You must create a directory in one of the manual directories (like the translate directory) that has the short name of the module you want to write. For example, to create a new module on “testing” in the Translation Manual, you will want to put the file in “translate/testing/01.md.”
- The file must be included in the table of contents,
toc.yamlfor the appropriate manual.
- The value of the slug in the
toc.yamlfile and the directory (without the extension) must be the same as the directory name (
testingin this example).
- The slug must be unique, and not used in any of the other manuals. This is a requirement so that it is possible to create unambiguous links to each module.
See the LICENSE file for licensing information.