Loading...
 

Setting up a Paratext Project for Success

Project Members

Who will be using the project?

  • Setup the Users, Roles, and Permissions
  • Make sure all users have the resources they need
  • Consider creating a "Simplified Menu" for users who get lost in Paratext

Resources

Have you downloaded all the available resources that are available to you in Paratext?

Are there still resources that you would like access to that are not available in Paratext?

  • You may consult this page about resources in Paratext, and use the link to a form at the bottom to request new resources.

Supporting projects

What additional projects should be created to support the primary project?

  • Back translation project
  • Auxilliar projects?
  • Transliteration project

Project Associations

Is there a dictionary to be linked to the project?

  • Link a FieldWorks dictionary in the Project in Project Properties and Settings, Associations tab.

What Biblical Terms list will be used for the project?

  • Will you use the default major Biblical terms list, or a customized list for the project?

    • Set the Biblical Terms list in Project Properties and Settings, Associations tab.

Project Notes

Notes are a major part of every project.  Don't settle for the default red flags! Redflag

  • Configure the notes icons and styles for your project on the Notes tab under Project Properties and Settings

Workspace

Text Combination Windows

  • Configure how the windows are arranged on the desktop.
  • Save the configuration for later

Text Collections

  • To save screen space, arrange the resource texts most frequently used in a text collection window, and save the collection.

Data Entry

Do you have what you need to enter characters efficiently?

Full keyboard solutions

Using AutoCorrect.txt

You can create a keyboard substitutions inside of Paratext by inserting an AutoCorrect.txt file inside the Paratext Project directory.  Instructions on how to do this can be found here:

Language settings

Is the correct language identifier being used for the language?  This is very important as it helps identify which languages have work being done.

Language identifier

BCP-47 Standard should include the 2 or 3 letter language code, and additional codes, only if they are needed to uniquely identify the language or script by distinguishing it from others in existance.

  • Script
  • Region
  • Variant

Language Settings Dialog

  • Alphabetic Characters
    • Set all of the alphabetic characters here, following the instructions in the User Guide.
  • Other Characters
    • Give special attention to Word-medial punctuation.  Any non-alphabetic characters that may appear inside of a word (such as a dash joining compound words), must be added here.  Otherwise, the word will be broken into two words.
  • Font
  • Font Features
    • Do you want to use the literary characters "ɑɡ" instead of the typographic characters "ag".  These and other character preferences can be selected if using one of the SIL fonts with font features enabled.

Preparing for automated checking

It is a dynamic process

  • When a project is brand new, there aren't a lot of settings that can be set in concrete.
  • As the project matures, some of the inventories begin to make sense.

What quotation system will be used?

  • Set up the quotation rules
    • Think about your rules
    • Test what you have
    • Adjust the rules
    • Make corrections to the rules or text as necessary

When you have some text data

Begin setting up the inventories

  • Characters
  • Characters Inventory: Either combine letters with diacritics or display characters separately.
  • Punctuation Inventory
    • Select Show sequences to view sequences of punctuation characters.
    • Clear Show sequences to view individual punctuation characters categorized by the contexts in which they occur (for example, Word Final). An underscore character preceding or following an item in the Punctuation column represents a space.
    • If the project does not have Quotation Rules set, a reddish bar will appear under the title bar of the inventory. Click Quotation Rules to the right of the reddish bar to set the Quotation Rules.
  • Markers Inventory: Standard Format markers. The stylesheet determines validity.
  • Unmatched Pairs of Punctuation: Unmatched punctuation characters (punctuation which is typically one of a pair, but is not matched by its counterpart).
  • Repeated Words: Words followed by repeated occurrences of themselves (for example, had had or the the).
  • Markers Missing Final Sentence Punctuation.
    • Select Show All Final Punctuation to display the individual characters that are the final characters of text that is preceded by a paragraph style marker.
    • Clear Show All Final Punctuation to group together all characters that are not sentence-final punctuation characters, but are final characters of text that is preceded by a paragraph style marker.
  • Markers Followed by a Lower Case Letter: Standard Format markers which are typically sentence-initial, but are followed by a lowercase letter.
  • Punctuation Followed by a Lower Case Letter:
    • Select Show sequences to view unique sequences of punctuation that are followed by a lower case letter.
    • Clear Show sequences to view individual punctuation characters which are typically sentence-final, but are followed by space, and then a lowercase letter.
  • Mixed Capitalization: Words which have capitalization other than initial uppercase followed by all lowercase.

Scripture Reference Settings

Even before books are translated, you will be writing cross-references or notes which refer to passages in them.  For this to succeed later on, you will need to name those books in advance.

  • What book names are you using?
  • What is the format for a reference?
  • Where will you put the origin of notes?
Contributors to this page: dhigby .
Page last modified on Monday December 3, 2018 12:39:55 GMT-0000 by dhigby.

License

Creative Commons License
All content on this LingTranSoft wiki are by SIL International are licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.