- 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
-
»
- 8 Package for Distribution
You want to make sure your keyboard is properly documented. You also want to include documentation files in your keyboard package.
Package - Export your On Screen keyboard
- Open your Keyman Project and then open the .kmn file that goes with it.
- Click on the On-Screen area tab
- Click the Export button
- Navigate to the source folder under your project name
- Change Save as type to Image (*.png)
- Type your project name (all lowercase) for the filename
- Click Save
- Select One file per shift state
- Click OK
Package - Steps to document and package
- Open your project folder in Windows Explorer. You can access this from Keyman Developer as follows:
- Go to the open project tab (.kpj extension)
- Click on Packaging tab
- Click the Options button to the far right of the named .kps file
- Select Open containing folder
- Go up one level to the named project folder
- Open Notepad (Windows key, type Notepad) and position it beside the open folder
- Drag README.md to Notepad
- Update description (e.g. Hazargi keyboard based on Persian)
- Save it
- Drag HISTORY.md to Notepad and make any needed changes
- Drag LICENSE.md to Notepad and make any needed changes
- Change to the source folder
- Drag readme.htm to Notepad and make any needed changes
LICENSE.md will need copyright information updated: both date(s) and copyright holder (which must be the name of a person or the name of a legally recognized entity). If you specify the copyright information when using the "New Project" wizard, it will take care of putting the copyright information where it needs to go.
- Drag welcome.htm to Notepad
- Copy and paste this text under where it says: Insert keyboard layout…
Copy to clipboard<p><b>Unshifted</b></p> <img src='hazargiU_.png' alt='Keyboard Layout'> - Change hazargi to your keyboard name
- Paste again below, but change Unshifted to Shifted and hazargiU_.png to hazargiU_S.png, again replacing hazargi with your keyboard name. (Note: this matches the image file name)
- The hazargiU_SC.png file may be deleted as it only contains invisible characters.
Repeat these steps for additional layers besides Unshifted and Shifted if you have them, such as RightAlt
- We can document the invisible characters in the first paragraph. E.g.:
Use Ctrl-Shift-1 for the zero-width joiner, … - You can add a link to a pdf file in your welcome.htm file. E.g:
Copy to clipboard<p>See <a href="file:my_doc.pdf">this document</a> for all the key combinations.</p>
- Test it now by double-clicking on welcome.htm
- Create a folder within the source folder called help
- Change to the help folder
- In Windows Explorer, Right-click and select New > Text Document
- Name the file hazargi.php (name of your project)
- Drag hazargi.php to Notepad
- Copy and paste the following into the new document
HTML to copy and paste:Copy to clipboard<?php $pagename = 'Hazargi Keyboard Help'; $pagetitle = $pagename; // Header require_once('header.php'); ?> <p> Hazargi keyboard based on Persian. </p> <h1>Keyboard Layout</h1> <h2>Desktop Keyboard Layout</h2> <div id='osk' data-states='default shift shift-ctrl'> </div> <h2>Mobile/Tablet Keyboard Layout</h2> <p>Due to the size and number of keys, some characters are hidden in the long press. Press and hold on the key with a little dot on the top right to reveal them.</p> <div id='osk-phone' data-states='default shift numeric'> </div>
- Modify as needed, particularly the correct data-states
- In Keyman Developer, click on the open project tab (.kpj extension)
- Now click on the Packaging tab and then the named project .kps link
- Click Add (assuming you are on the Files tab) and add the two .png files we created above
- On-screen bitmaps should go in your source folder and also be added to the package
- Remember to finalize your Icon
- You may want to copy information from welcome.htm to your .php file, for example (from step 13): "Use Ctrl-Shift-1 for the zero-width joiner, ..."
Explanation of Files and What They are Used for
These are the files you need to edit outside of Developer:
- In the top-level folder (where your .kpj file is located)
- README.md
- HISTORY.md
- LICENSE.md
- In the source folder
- readme.htm
- welcome.htm
- In the 'help' folder (must be created under the 'source' folder)
- keyboardname.php
README.md
This file gives an overview of the keyboard for someone looking at the keyboard source files
The end user won't see this
HISTORY.md
This file gives the history of changes to the keyboard
For a brand new keyboard, just use version 1.0
If you are preparing an existing keyboard for inclusion in the Keyman keyboards collection, you may want to move the history to this document, and your version number may be based on the version number in the existing keyboard
LICENSE.md
To be included in the Keyman keyboards collection, you need to release the keyboard under the MIT license.
readme.htm
This file is displayed when a user begins installation of the keyboard in a desktop environment
The purpose is to give a brief description of the keyboard
welcome.htm
This file needs to provide enough information so that the user can figure out how to use all the features of the keyboard
You can use keyboard images (.png files created from Keyman Developer) and/or typing charts
keyboardname.php
It needs to be in the help folder under the source folder
Often it is based on the welcome.htm file