omegatwb
/
fr_tm
forked from WA_Training/fr_tm
1
0
Fork 0
Files Issues Pull Requests Releases Wiki Activity See in Reader

Update 'translate/file-formats/02.md'

This commit is contained in:
SusanQuigley 2020-02-21 16:32:59 +00:00
parent bef6f66d98
commit 82c125beb4
1 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
translate/file-formats/02.md
View File

@ -7,18 +7,16 @@ While a large part of translation has to do with language, words, and sentences,
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. For instance, each chapter is marked like this ''\c 1'' or ''\c 33''. Verse markers might look like ''\v 8'' or ''\v 14''. Paragraphs are marked ''\p''. There are many other markers like this that have specific meaning. So a passage like John 1:1-2 in USFM will look like this:
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 Roman letters. 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''. There are many other markers like this that have specific meaning. 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.
\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 is able to format 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).
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).
**Bible translations need to be written with USFM markers in order for Wycliffe Associates to make them accessible!**
To read more about USFM notation, please read http://paratext.org/about/usfm .
**Bible translations need the USFM markers in order for Wycliffe Associates to make them accessible! **
#### How To Do a Bible Translation in USFM
@ -35,3 +33,7 @@ The easiest way to get content marked up with USFM is by using an editor that is
*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.*
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 more USFM markers, please read [USFM Markers].
To read more about USFM notation, please read http://paratext.org/about/usfm .