WA-Catalog
/
en_tm
forked from WycliffeAssociates/en_tm
5
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 20:42:29 +00:00
parent 304c186257
commit 13cff6848f
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -7,7 +7,7 @@ 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. 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 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: 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". 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 \c 1
\p \p