- 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
-
»
- KDT15 Session 9
Keyman Developer Tutorial
Distributing the Keyboard
Session 9
This session we will discuss how to distribute a keyboard.
Introduction
After compiling, we can test the package installation in Keyman Desktop, by clicking Install Package. We should test that all the keyboards and fonts install successfully, that the Readme and Welcome files are displayed during the install, and that the documentation is accessible to the end user. We should make sure that the On-Screen Keyboards install with the keyboard.
Distributing Keyboard on the Keyman Cloud Keyboard Repository (recommended)
Once we have tested the package to our satisfaction, it is time to distribute it. We recommend uploading our keyboard package to the Keyman Cloud Keyboard Repository. The instructions can be found at Keyman website at this link. There are some restrictions on names allowed for keyboard project folders. Name must be unique in the repository, and the characters in the folder/project name must be drawn from the set of underscore plus lowercase alphabetic characters.
Distributing Keyboard via an External Storage device.
Once the keyboard package KMP file is created, we can share it via external storage devices (USB drive, SD card, etc.). If the user has Keyman installed on the device, Keyman should be able to install the package KMP file on the device.
Distributing Keyboard via a Web Site
If that is not an option, we can upload the KMP file to a public facing website. We would need to upload the KMP file to the website. Below is a simple example for including the Dagbani keyboard in the web site.
<html>
<head>
head>
<body>
<a href="https://url.com/.../dagbani.kmp">Download Dagbani Keyboarda>
body>
html>
Distributing to an Android device
Upload the web page to the public facing website. Once done, we can install the keyboard package onto the mobile devices by following these steps:
Here are the Instructions for installing keyboards to an Android device
Package file contents
A package can have a variety of different files contained within. The following files and file types are recognized by the package installer:
KMX file (Desktop)
Keyboard files. Each of these will be installed. Keyman Configuration will not allow installation or uninstallation of a single keyboard from a package. They will always be treated as a group for installation and uninstallation.
KVK file (Desktop)
On Screen Keyboard files, associated with each keyboard file.
JS file (mobile only)
Touch layout Keyboard files. When Keyman mobile applications install a keyboard package, all included keyboards will be installed as a group.
welcome.htm
Help for the keyboard, HTML format. This will normally be displayed when the package is installed by the user and is also the entry point for help when accessed via Keyman's help system or Keyman Configuration.
readme.htm
Displayed before a package is installed, together with brief metadata about the package, to allow the user to determine if they wish to continue installation of the package.
kmp.inf (Desktop only)
A Windows INI format file that lists each of the files in the package, together with metadata.
kmp.json (mobile only)
A JSON format file contains metadata for the keyboard package such as package version, keyboard versions, and lists each of the files in the package. For more explanation of the structure of the JSON file, please read the metadata documentation.
TTF, OTF and TTC files
Truetype font files that will be installed with the package and uninstalled when the package is removed. On mobile, these fonts will be available only within the Keyman app and the on-screen-keyboard, not in other apps.
Notes
The Keyman package (KMP) file can be installed by Keyman (version 10 or later) on any platform, whether on Windows, Mac, Linux, Android or iOS. Distributing the package can be tricky, since it is a zip type file containing javascript, which is suspect to many email servers. But it can be shared by uploading it to a Google drive, then sending links to the file.