Paratext allows users to create custom Python scripts and to add them to its Custom Tools menu. These scripts are found in the cms folder inside your My Paratext Projects folder. This tutorial will show you how to write these scripts and how to share them with other Paratext users.
What is it for?
These scripts were originally designed to allow Paratext users to create their own custom Scripture checks. The scripts can read the translation text, check for issues, and generate a report. However, your creativity may discover other uses for these tools.
import _ _builtin_ _
Standard scripts to help with Paratext functions
- Sets up the registry to run a checklists test
This module contains all the Python objects necessary to access Paratext 6 project data:
- Reference - A point in the text, e.g. MAT 3:11
- Tag - Information for a single marker from the stylesheet
- ScriptureText - The text itself
- Language - Information about the language for this text
Not funtional. Proper names and biblical term renderings were accessed via this module when kb2 files were used to store Biblical terms. Currently Biblical terms are stored in TermRenderings.xml. Maybe somone can rewrite this to work?
Creating your CMS file
This is followed by a space and the name of the check. This check will be featured in the project menu of Paratext under Tools -> Custom tools
The description will show in the dialog that pops up when selecting the check from the menu:
You can create a new submenu for your scripts or include them in one of the existing submenus just by naming it here. Many scripts are listed in the Unsupported menu, but we are not a fan of unsupported products. If your script is designed to help people, wouldn't you want to follow through?
This determines where your plugin shows in the list. Rank 1 is near the top. If only Google made it this easy...
Places the Book selector on the dialog:
Collecting user input
The following options are available for collecting user input: