See in Reader
3.6 KiB
The Technical Nature of Translation
While a large part of translation has to do with language, words, and sentences, it is also true that a major aspect of translation is technical in nature. From creating alphabets, typing, typesetting, formatting, publishing, and distributing, there are many technical aspects to translation. In order to make all this possible, there are some standards that have been adopted.
USFM: Bible Translation Format
For many years, the standard format for Bible translation has been USFM (which stands for Unified Standard Format Markers). We have adopted this standard as well.
USFM is a type of markup language that tells a computer program how to format the text. This markup language uses a backslash ( \ ) with a short code to tell how each item in the Bible should be formatted. The code uses letters from the English alphabet. For instance, each chapter number is marked with "\c". Each verse number is marked with "\v". The beginning of each paragraph is marked with "\p". So a passage like John 1:1-2 will look like this in USFM:
\c 1
\p
\v 1 In the beginning was the Word, and the Word was with God, and the Word was God.
\v 2 This one, the Word, was in the beginning with God.
When a computer program that can read USFM sees this, it formats all of the chapter markers the same way (for instance, with a larger number) and all the verse numbers the same way (for instance, with a small superscript number).
Note: Making text bold, italic, or underlined in a word processor does not make it bold, italic, or underlined in a markup language. This type of formatting must be done by writing the designated symbols.
Bible translations need the USFM markers in order for Wycliffe Associates to make them accessible.
How To Do a Bible Translation in USFM
Most people do not know how to write using USFM markers. This is one of the reasons why BTT Writer was created. When you do a translation in BTT Writer, what you see looks very similar to a normal word processor document without showing the USFM markers. This way, when you upload your translation from BTT Writer, what is being uploaded is already formatted in USFM.
Converting a Translation to USFM
Though we strongly encourage translators to only do a translation using USFM markers, sometimes they do a translation without using USFM markers. This type of translation still can be used, but first the USFM markers must be added. One way to do this is to copy and paste it into BTT Writer, then place the verse markers in the correct place. When this is done, the translation will be able to be exported as USFM. This is a very arduous task, so we strongly recommend doing your Bible translation work from the beginning in BTT Writer or some other program that uses USFM markers.
Conclusion
The easiest way to get content marked up with USFM is by using an editor that is specifically designed to do that. If a word processor or a text editor is used, these markers must be manually entered.
When contemplating which software to use, please keep in mind that translation is not just about words; there are many technical aspects that need to be taken into consideration. Whatever software is used, just remember that Bible translations need to be written using USFM markers.
To see some common USFM markers, please read Common Markers for Formatting Scripture.
To read more about USFM notation, please read http://paratext.org/about/usfm.
For specific USFM formatting rules, you can use the interactive documentation at: https://ubsicap.github.io/usfm/about/index.html.