From 13cff6848f37985211c8a3c97aabd852dc2ba84d Mon Sep 17 00:00:00 2001 From: SusanQuigley Date: Fri, 21 Feb 2020 20:42:29 +0000 Subject: [PATCH] Update 'translate/file-formats/02.md' --- translate/file-formats/02.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/translate/file-formats/02.md b/translate/file-formats/02.md index fcfa1e8..d4ff2ec 100644 --- a/translate/file-formats/02.md +++ b/translate/file-formats/02.md @@ -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. -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 \p