- 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
-
»
- KDT Session 1
Keyman Developer Tutorial
Create New Project
Session 1
This session we will create a keyboard project for the Dagbani language of Ghana. We will call the project DagbaniTutorial. We will create the project based upon the US keyboard. In this session we will also create a keyboard project for the Kamba language of Kenya. We will call the project KambaTutorial. We will create this project from a blank keyboard.
Create project from an existing Windows keyboard
1. Start Keyman Developer.
2. In the Project menu, click New Project.
3. Click Import Windows Keyboard, then click OK.
4. In the Select an underlying system keyboard list-box, select US (KBDUS.DLL), and then click OK.
5. In the New Basic Keyboard Project dialog box, do the following
- In the Keyboard Name box, enter DagbaniTutorial. Normally we would enter the language name.
- In the Copyright box, enter 2021 MyOrg. Normally we would enter the current year and the name of our organization or our own name.
- In the Version box, we will accept the default, since this is the first keyboard.
- In the Author box, enter Me. Normally we would enter our name.
- In the Targets box, set any. In this way it can work for all devices.
- In the Languages box, remove en (English) from the list and add the BCP 47 Tag of the desired language to the list. In our case we will add dag (Dagbani) to the list.
The dialog box should appear as below.
- Then click OK.
6. In the Project - Information dialog box, Click Keyboards. The Project – Keyboards dialog box appears, as below.
7. Then click dagbanitutorial.kmn. The Details pane appears, as below.
Click the Save icon to save our work. The project has been created.
8. We may want to change the size of the character font to meet our viewing needs. In the View menu, click on the Character Font. The Character Font dialog box appears. Make whatever changes we desire. Then click OK. This impacts the font that is used in the testing box.
9. We may want to change the size of the code font to meet our viewing needs. In the View menu, click on the Code Font. The Font dialog box appears. Make whatever changes we desire. Then click OK. This impacts the font that is used in the Keycoding box.
10. Click Layout. The Layout pane appears. Note that we see all this code that came from the US keyboard. In the next session, we will need to modify this code for Dagbani language.
11. To exit the program, in the File menu, click Exit.
Create a project from a blank keyboard
We will now create the KambaTutorial project
1. Start Keyman Developer.
2. In the Project menu, click New Project.
3. Click on Basic, then click OK.
4. In the New Basic Keyboard Project dialog box, do the following
- In the Keyboard Name box, enter KambaTutorial. Normally we would enter the language name.
- In the Copyright box, enter 2021 MyOrg. Normally we would enter the current year and the name of our organization or our own name.
- In the Version box, we will accept the default, since this is the first keyboard.
- In the Author box, enter Me. Normally we would enter our name.
- In the Targets box, set any. In this way it can work for all devices.
- In the Languages box, add the BCP 47 Tag of the desired language to the list. In our case we will add kam (Kamba) to the list.
The dialog box should appear as below.
- Then click OK.
5. In the Project - Information dialog box, Click Keyboards. The Project – Keyboards dialog box appears, as below.
6. Then click kambatutorial.kmn. The Details pane appears, as below.
7. Click on Layout. The Layout pane appears. Note that this time we see a keyboard layout image. This is because this keyboard is not based upon any other keyboard which is too complicated for Keyman Developer to display.
Click Code tab. We see just a few line codes that initialize an empty keyboard, as below. We do not see any code that would come from another keyboard.
8. Click the Save icon to save our work. The project has been created.
9. To exit the program, in the File menu, click Exit.