At Faith Comes By Hearing, we are dedicated to making the Bible accessible to people around the world in their native languages. We strive for excellence in our mission, leveraging technology and collaboration to achieve our goals.

The role of the Text Processor requires adaptability and problem solving to help the Script Assembly team complete CORE Scripts efficiently and with excellence, as well as, the preparation of texts for use on Bible Brain and in other formats for distribution of the Bible in its written form.

Responsibilities Include:

• Database Language research: specifics of the language for text preparation, appropriate agreements or restrictions for public display. Also research any language specific notes and fonts for language folders. This may require communication with the Global Partnerships Department (GP), as well as Language Recording Department (LRD);
• Online research: fonts, orthography, or other language questions;
• Be able to scan a text and perform optical character recognition (OCR), while building an alphabet and dictionary for better results;
• Take a scanned text or other digital text that is not ready for use in our programs and add the proper formatting and marking necessary for use in the Paratext program;
• In Paratext, remove components of the text that are not used in the recording process such as footnotes, cross references, section headings, etc. The removal of specific markers may require the creation of formulas when current formulas are unable to do so;

• Use Glyssen or other appropriate programs for splitting out the speaking parts and identifying the correct characters, while also trouble shooting problems that may arise due to the unique characteristics of a language and any display issues;
• Be proficient with the use of Nitro to check for additional problems and divide any lines that are too long for the average reader.
• Produce a CORE-Script for use in a recording for field teams, partner recordings, and virtual recording – helping the developers with continual feedback;
• File conversion: such as SFM files to USFX/XML; Non Unicode files to Unicode; and non-standard encoding to UTF-8;
• Organizing skills: creation of language folders with MS Word Document, the CORE Script template, the Possible Issues Report, Font files, and language specific notes from research for the scripter as well as DBP;
• Troubleshoot other challenges including lack of punctuation or quotation in Biblical text, poor quoting, orthographies that are unique to one individual language, scanning and converting printed texts which contain smudges and missing print, attempting to solve unique font issues for languages to be used on Bible.is application, etc.);
• Problem solve when necessary, by communicating with LRD or GP in order to find necessary information (e.g. finding punctuation markers, word meanings, fonts, etc.);
• Apply quality control checks on each completed CORE Script for accuracy in formatting, text, etc.;
• Prepare electronic texts for the Bible Brain, posting in the appropriate folder and sending notifications to appropriate departments;
• Checking live texts to verify correct display of the text;

Database entries from information gathered on all prepared texts, including verification of texts from the checking of live texts on the listed browsers;