From 710ab2408cc9205b76c2fc9dc4d811d81bd1c9a8 Mon Sep 17 00:00:00 2001 From: SusanQuigley Date: Fri, 21 Feb 2020 20:43:54 +0000 Subject: [PATCH] Update 'translate/file-formats/02.md' --- translate/file-formats/02.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/translate/file-formats/02.md b/translate/file-formats/02.md index d4ff2ec..e73dd06 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 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: +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 @@ -34,6 +34,6 @@ The easiest way to get content marked up with USFM is by using an editor that is 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 see more USFM markers, please read [USFM Markers]. To read more about USFM notation, please read http://paratext.org/about/usfm . \ No newline at end of file