- Home
-
Training Materials
- Keyboards and Fonts
- Linguistics
- Literacy
- Oral Translation
- Others
- Scripture Use
-
Translation
- Scripture Forge
- Adapt-It
- OmegaT Translation Memory Tool
-
Paratext
- Paratext 9 Materials
- Paratext 8 Course Manuals
- Paratext 7.5 Course and Handbook
- Paratext 7.1 Basic Training
-
Paratext Tutorials
- Basic Editing
- Language Source Tools in Paratext 7.6
- View menu tutorial
- Basic introduction to USFMs
- Tips and Tricks
- Introduction to Using Notes
- Cookbook for Consultants
- Menus vary by active project
- Vérifications
- Help! Paratext has stopped working
- Help, send and receive is not working!
- Bible Modules
- Which Paratext Tool When
- Paratext-FLEx Integration Tutorial
- Back Translations and Interlinearizer
- Send-receive and backing up your data
- ParaTExt 8 Test Projects
- New features in Paratext 8
- Voice Marking Tools
- Animated introduction to Paratext and the stages of a translation project
- Setting up a Paratext Project for Success
- Import TXT or Word DOC Files into Paratext Using SILAS
- Illustrations and Maps
- Advanced Unicode handling
- Create a Custom Python Script in the Paratext Menu
- Create a Custom Scripture Check in the Paratext Menu
-
Translator's Workplace
- Adding BdT Menu to Logos 10
- Adding TW Menu to Logos 10
- Logos Bible Software
-
Translator's Workplace Logos Edition
- Logos 8 Get Started Manual
- Opening Logos
- Opening a Resource
- Navigating a Resource
- Reading Multiple Versions
- Basic Search
- Bible Search
- Looking for Bible Facts
- Using the Home Page
- Using the Passage Guide
- Using the Exegetical Guide
- Using the Bible Word Study Guide
- Using the Sermon Starter Guide
- Using the Topic Guide
- Studying English Words Using the Bible Word Study Guide
- Studying Hebrew and Greek Words Using the Bible Word Study Guide
- Prepare a Bible Lesson Using the Sermon Starter Guide
- Look for Information on a Topic Using the Topic Guide
- Saving Your Workspace or Layout
- Arranging the Windows
- Study a Word Using a Reverse Interlinear
- Study a Word Using a Morphology Search
-
Logos edition
- Logos 8 Get Started Manual
- Set up TW Logos for Success
- Quickstart Guide
- Advanced Tips
- Scrolling with other Translation Programs
- Transition from TWFolio
- Troubleshooting
- External Resources
- Low Bandwidth Installation and Updates
- Turn off Logos internet use when visiting a low bandwidth area
- Logos for Beginners Video-based Training
- Translation Workplace - Folio edition
-
Consultant Training
-
Regional Workshops
- Africa Kenya Workshops(LTCT)
- 2021 Africa Virtual Workshop
- 2020 Africa Nairobi
- 2019 Africa Nairobi
- 2018 Africa Nairobi
- 2017 Africa Nairobi
-
2016 Africa Nairobi
- Course Objectives 2016
- Course Schedule 2016
-
Course Program 2016
- HearThis Session 4
- FLEx 8 Lexicon Edit
- FLEX 8 Using text to build lexicon
- LTCT2016 FLEx - Export
- Scripture App Builder Day 1
- LTCT2016 WeSay New Projct
- Create a new project from a FLEX Lift File
- LTCT2016 Wesay Wordlist
- LTCT2016 WeSay Collaboration
- Scripture App Builder Day 1B
- Scripture App Builder Day 1C
- Scripture App Builder Day1D
- Scripture App Builder Day 2A
- Scripture App Builder Day 2A
- Scripture App Builder Day 2B
- Scripture App Builder Day 2C
- Scripture App Builder Day 2D
- Scripture App Builder Day 3A
- Scripture App Builder Day 3B
- Scripture App Builder Day 3C
- Scripture App Builder Day 3D
- LTCT2016 RegExp
- LTCT2016 Paratext1
- Evening Sessions 2016
- Morning Sharing Time 2016
- Responsibilities 2016
- LTCT 2016 Evaluation
- 2015 Africa Nairobi
- 2014 Africa Nairobi
- 2014 Africa Kara, Togo
- 2013 Africa Nairobi
-
2012 Africa Nairobi
- Course Objectives 2012
- Course Program 2012
- LTCT2012 Friday Jan 20
- LTCT2012 Thursday Jan 19
- LTCT2012 Wednesday Jan 18
- LTCT2012 Tuesday Jan 17
- LTCT2012 Monday jan 16
- LTCT2012 Saturday Jan 14
- LTCT2012 Friday Jan 13
- LTCT2012 Thursday Jan 12
- LTCT2012 Wednesday Jan11
- LTCT2012 Tuesday Jan 10
- LTCT 2012 Monday Jan9
- LTCT2012 Evaluation
- Proactive Software Training
- Teaching a Workshop
-
Paratext for Consultants
- 1 Arranging your workspace
- 2 Consultant notes
- 3 Searching and Dictionaries
- 4 Send and receive
- 5 Taking notes during checking
- 6 Keeping track of Biblical term renderings
- 7 Using the Biblical terms tool
- 8 Seeing history and comparing versions
- 9 Understanding the vernacular text
- 10 Spell checking
- Video lessons
- Paratext Supporters
- Digital Publishing
-
Regional Workshops
- Webinars
- Resources
-
»
- How to directly insert images, illustrations, and figures into a Paratext project from a searchable database
Download and Unzip Image Files and Folders
- Visit the official SIL Sample Illustration Repository (hosted in Dropbox).
- Alternatively, you can check out the experimental space for sample illustrations at tiny.cc/sampleimages. This contains beta versions of the color images, and beta versions with keywords in other major languages. It's hosted on Google Drive.
- If using the official repository site:
- Download the folders that you want to use directly to a folder on your computer
OR - Download the folders that you want to use directly to your Dropbox
- Download the folders that you want to use directly to a folder on your computer
- If using the experimental Google Drive site:
- Either browse within the appropriate language folder for the sets of images you want, and download those OR
- Download all images by right-clicking on the language folder and selecting Download.
- Alternatively, you can add the relevant folder to your own Google Drive folder, and sync that to your local drive using Google File Stream (on corporate accounts) or Google Backup & Sync (on personal accounts)
- Note that these are low-resolution watermarked images.
- In all cases except for WBT image sets licensed under CC, the full-resolution originals are available only for bona fide typesetters, who will automatically substitute them for your sample images at typesetting time.
- Unzip this collection to a folder within your Pictures folder.
- This will ensure that the images are included in Windows’ search index.
- If you’d rather store these files in another location, add that folder to Windows’ search indexing. Here’s how to add it.
- Troubleshooting: On some systems, the Windows Search Index might be able to return results for filenames but not for key terms, such as "sheep" or "LUK02". This may be because it's been somehow corrupted or misconfigured.
- If you are unable to diagnose and correct the problem, one workaround is to open the File Explorer App, click on the "3 dots" menu (for More menu items), then click on Options to open the Folder Options dialog. Next, click on the Search tab. Finally, under the heading "When searching in non-indexed locations", check the option for "Always search file names and contents".
- Alternatively, you can explicitly search for key terms by prefixing them with "tags:". For example, "tags:sheep AND tags:LUK02"
Find and Insert Images in Paratext
- In Paratext, position the cursor in the passage where you want to insert a picture.
- Go to the Project menu > Insert > Figure...
- Click the Browse button:
- Navigate to the folder where you unzipped your collection.
- Click in the SEARCH box in the top right corner:
- Enter one or more terms to search for.
- There are a number of search terms/filters you can use:
Search Term/Filter Description Example(s) {keyword} Search for an image by keyword. dove
baptism
altarBible book Search for a book using the 3-letter Paratext book code. GEN
MRK
LUKChapter reference Search for a chapter using the 3-letter book code plus the 2-digit chapter number. GEN03
MRK01
JHN10OR search OR will include images with any of the search terms.
Example: Find images of a sheep or lambsheep OR lamb digital digital will include images with permission to use in a Scripture app.
Example: Find images of a lamb that can be used in a Scripture appsheep digital
minus {term} Using the minus sign in front of a term will exclude the term from the search.
Example: Find images of a sheep that are NOT pictures of a lambsheep -lamb color The color keyword will include color images (excluding black and white images).
Example: Find color images of a sheepsheep color black The black keyword will include black and white images (excluding color images).
Example: Find black and white images of a sheepsheep black - You can also combine these filters with parenthesis and additional terms.
- For example: Find images of sheep or lambs that can be used in a Scripture app: (lamb OR sheep) digital
Adjust Display Settings
- Typically, the first time you do a search, you'll need to adjust the display settings for the results.
- If your search results are not displayed with extra large icons:
- Optional View Settings:
- To make space for even more images, you may want to hide the navigation pane: go to Organize > Layout and uncheck Navigation pane.
- You can resize this window to fit more images by dragging a corner or edge, or by double-clicking on the title bar to maximize it.
- Double-click on an image from the search results to select it.
- Enter a Caption:
- Best Practice: If you only want this illustration to be used in print publications or you don't expect to receive permission to use it in app or Web, enter “p” for Location.
- Click OK.
Regarding Translating the Keywords into Languages of Wider Communication
Note that in many cases, Google Translate gets thrown off by the English wording. Titles in English often omit the articles (a/an/the) and use a present participle verb without the context of a complete sentence; Google Translate does poorly with such wording, so we are tidying up the English first to get Google's best translation. Then there are issues of Google Translate's skewing due to its training corpus: It wants to translate ram into Hindi as the name of the god Ram; or bush into Swahili as the former president Bush. The A.I. folks have said they can refine the Google Translate result for us to focus it on Biblical vocabulary. Finally, after these steps are complete, we'll need mother-tongue speakers of each language to review the results and manually correct them where needed. Please let us know if you'd like to contribute to this effort.
We also need to determine which languages are worth supporting here. I just picked Hindi, Swahili, French and Spanish out of thin air without any real data on number of translation teams that would be relying on each. If you have any estimate of the number of current and projected translation projects that would need keywords in any language of wider communication, please give me your estimates. It needs to either be a language supported by Google Translate or one that you have a way to process for us. (Tok Pisin??)
Contact Den at [email protected].