- 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
-
»
- 3 Creating your Keyman Project
Start with an existing Windows keyboard
This tutorial refers to a Google Shared Drive which was part of a workshop training. You can save your Keyman projects in your preferred location.
A Keyman Project contains the various parts of your keyman keyboard definition that are required for creating a distributable or downloadable package. These files and the project file itself are stored on your hard drive in the folder with the same name as your project.
- Start Keyman Developer
- Project > New Project
- Click on the icon Import Windows Keyboard, then
- Complete information as follows:
- Choose Persian (Standard). Find by typing p and choosing the 2nd one, click
- Fill out - Name:Hazargi, Copyright: 2020 My Company, Author: Me
- Target: any
- Languages: remove fa, Add haz, leave defaults, click
- Browse, go to the shared Google folder
- ID: hazargi (lowercase!)
Make sure that all the options are correct here because this dialog box can't be re-opened after you click OK. To make changes later, you would have to either edit the XML file manually or delete the project file and start over.
- Click -- now you have a project
- Click on the Keyboards tab
- Click the plus sign next to hazargi.kmn
- Click on hazargi.kmn blue link (now you have two top tabs)
- Name: Hazargi, Targets: Any, click Keyboard is right-to-left.
- Modify the layout:
- Click on the Layout big button
- Click on e key, note the Unicode value and output char. below
- Click in text box for Output char., erase what’s there
- Go to Character Map, type peh
- Double-click to insert it.
- Go to Build Area
- Click Compile Keyboard - should get Success (twice)
- Click Keyboard > Test
- Install the Debug Host Keyboard (if necessary)
- Type the e key and you should see پ (U+067E)
- To stop testing select Debug > Stop Debugger
Start with a blank keyboard
- Start Keyman Developer
- Project > New Project
- Click on the icon Basic, then click
- Complete information as follows:
- Fill out - Name: Hazargi Phonetic
- Target: any
- Languages: Add haz, leave defaults, click
- Browse, go to Google Shared folder
- ID: should be hazargi, click -- now you have a project
- Click on the Keyboards tab
- Click on hazargi_phonetic.kmn blue link
- Targets: Any, RTL box
- Modify the layout:
- Click on Layout
- Click on p key, note: Unicode value and output character are blank
- Click in the text box for Output ch.
- Go to Char. Map, type peh
- Double-click to insert it (067E).
The project is a place where various parts of your keyman keyboard definition are accessible. On your hard drive the files, including the project file, live under the folder with the same name as your project.
If you have an existing Keyman keyboard, use the Add existing keyboard... button to add it.
- Go to Build Area
- Click Compile Keyboard - should get Success (twice)
- Click Keyboard > Test
- Type the p key and you should see پ (U+067E)
Start with an English US Windows keyboard
No visual keyboard layout display. Why? Because there’s complex code.
- Start Keyman Developer
- Project > New Project
- Click on the icon Import Windows Keyboard, then click
- Type US and go down one to the US (KBDUS.DLL) row, then click
- Complete information as follows:
- Fill out - Name: Fulfulde
- Target: any
- Languages: Add ffm, leave defaults, click
- Browse, go to Google Shared folder
- ID: should be fulfulde, click -- now you have a project
- Click on the Keyboards tab
- Click on fulfulde.kmn blue link
- Targets: Any
- Click on Layout (It takes you automatically to the code view)
- Click Design and see the error message
- Try cutting the code out temporarily. Design can be used.
- Change K_1 to map to ‘P’. Click On-Screen button, then Fill from layout. Click to overwrite. See the ‘P’ on the 1 key. F7 to compile. Debug > Stop Debugger