Introduction

Have you ever discovered quoted text in a footnote, but can’t find that text in the verse? This happens when the verse text is updated and the footnote is no longer relevant.   Have you ever struggled to verify the references cited in a footnote, or had trouble keeping book abbreviations consistent?  This article will show you how to make your footnotes in a way that Paratext can help you check them for problems like these.

Quoted Text in a Footnote

Any time you quote words from the translated text in your footnote, you should mark them with the quoted text marker “fq”.  This will let Paratext know that the word or phrase is a quotation and the quoted text check will alert you when the verse and footnote no longer match. During the life of a project, it is very common to change the renderings of biblical terms of modify the spellings, causing footnotes to be out of date.  Running the Basic Checks on your project will ensure that the quoted text always matches what is in the verse.

How to Mark Text with fq Marker

There are two main ways to apply the quoted text marker.  The first is insert the footnote while the word or phrase you wish to comment on is highlighted.  This method copies the text from the verse, and pastes it into the footnote with the appropriate fq markers.  The second is to manually insert the markers and type the text into the footnote. We will show the first method below:

Insert Footnote after Highlighting Text

1. Highlight the text you want to appear in the footnote:
2. Right-click on the selection and choose Insert Footnote:
   
   Paratext creates the footnote inserting the reference, the fq marker and the word or phrase from the text.
3. Type what you want to say about the text. If the footnote will include an alternative to the text as it appears in the verse, use the Quoted Text Alternative marker fqa.  Because fqa  text is different, Paratext will not compare it with the verse text.
   
   When you use fq markers for footnote text, Paratext will ensure that the quoted text matches what is in the verse and will alert you if they are out of sync.
   

Don’t like how Footnotes Look?

A common objection to using the fq marker is that it  produces italicized text, and many users want the word or phrases cited to appear in bold.  The key-term marker fk produces a bold text so it is often used in this context.  You can change the default appearance of a style by creating a custom stylesheet for your project.   Find information about customizing stylesheets in the Paratext Help.  Of course, when publishing your text you can ask the typesetter to use the style of your choice for the fq marked text.

When Not to Use the fq Marker

In certain places, the quotation in the footnote is of an alternate rendering.  It follows the same pattern as the Scripture text, but is an alternate text.  Because this text will not be found in the verse, it must be marked with fqa.  Paratext will format it the same as fq but will not check to see if it matches the verse text.

Scripture References in a Footnote

Footnotes sometimes cite other verses in the Bible.  These references should use the same book abbreviations as the rest of your Bible, and they should not refer to verses that do not exist (e.g. 1 John 20:4).  Checking these references is very tedious work but Paratext will do it automatically if you mark the references in your footnotes with the Target Reference marker xt.

The example below shows a footnote that refers to a Psalm that supports an alternate reading of the text.

You’ll notice that the xt marker activated the Scripture reference check. (Note: The Scripture reference check will only work if the Scripture Reference Settings have been configured.  See Paratext Help for more information on Scripture Reference settings.)  The red x on the book icon indicates that there is a problem with the reference.  In the Scripture reference settings for the project, Psa is indicated as the short name for Psalms. Correcting Ps to Psa will remove the red x as the reference now passes the automatic Scripture Reference check:

Conclusion

By using the fq and fqa markers, you can more easily keep the contents of my footnotes up-to-date.  Finding all the places where the footnotes need changes after a  ten-year project would be vary hard.  Consider using these markers if you are not doing so already and see how much they can help you.

Keeping book abbreviations and the format of references consistent and correct throughout an entire project is a big challenge.  Consider using the cross reference-target reference marker xt in footnotes that cite another reference.  I think you will find that you will be able to correct many errors in your footnotes.

 

The Paratext website is an obvious place to list training events for people to learn Paratext or improve their skills.  To facilitate this, we have launched an events section on the website where Paratext training events will be listed, starting with a Paratext Training Course in Dallas, Texas, December 3-10.  Since there are so many organizations using Paratext, we can’t know about all of the training events going on around the world. So we are including a link on our events page for training event submissions. If your organization is hosting a training event and is able to make it open to others, we would encourage you to list it here.

If you have a larger group that needs training, please write to help@paratext.org and we will see if there is a trainer who is available to travel to your area.  Our goal is for every Paratext user to be working effectively with the software.

Whether you can attend a training event or not, you can always take advantage of our online training videos, found at https://vimeo.com/channels/paratext

We will continue to keep these videos up-to-date with future versions of Paratext, and are currently making localized versions in Spanish, French, Russian, Portuguese, Chinese, and Indonesian.

—

The Paratext Support Team

Do you find yourself stuck trying to type characters into Paratext that are infrequent but hard to find?  Have you ever gone to a Word document to find a character and paste it into your translation? Have you ever memorized the Alt + Number pad sequence for a special character and typed it in?  Then this article is for you.  Read on!

When many accented or special characters are needed, you should use a custom keyboard from Keyman, or Microsoft Keyboard Layout Creator (MSKLC). However, many projects only need to type a few characters that are not on the physical keyboard. These would include special punctuation such as the em dash, ellipsis, curly quotes, and one or two accented characters. In cases like this, you can use Paratext’s autocorrect feature instead.

Autocorrect

Just like Word, Paratext has an autocorrect feature that the user can configure. You may not have heard of it because there is no option on the menu called autocorrect.  It is explained in the help file, but we will show you what to do here.

You can have one autocorrect file for each project, and so the file must be stored in that project’s folder.  Create a new text file with notepad.exe and save it in your project folder \My Paratext 8 Projects\[project name]. When saving the file, you must select Encoding: UTF-8 and the file must be named “autocorrect.txt”.

The basic form of each entry is:

word-->changed word

• There should not be any extra spaces unless you want them to appear in the changed word.
• You can use the actual characters or the Unicode numerical values in the format \uxxxx in the entries.

Here are several examples to clarify how it works:

Typing em dash

\u002D\u002D-->\u2014

When two hyphens (U+002D) are typed, autocorrect will change them to one em dash (U+2014).

Typing ellipsis

\u002E\u002E\u002E-->\u2026

When three periods (U+002E) are typed, autocorrect will change them to an ellipsis (U+2026).

Typing smartquotes

One of the most useful autocorrect examples comes straight from the Paratext help file.  How to create smartquotes “ ” just by typing angle brackets << >> and how to add hair spaces between quotation marks.

# Change space (\u0020) between quotes to hair spaces (\u200A)

“\u0020<-->“\u200A‘
‘\u0020‘<-->‘\u200A“
’\u0020’>-->’\u200A”
”\u0020>-->”\u200A’

# Change angle brackets into curly quotes

<-->‘
‘‘-->“
>-->’
’’-->”
---->–
–--->—

Typing Accented Vowels like É

e´-->\u00E9

When an “e” and an acute accent are typed, autocorrect will change them to a lower case composed é (U+00E9).

E´-->\u00C9

When and “E” and an acute accent are typed, autocorrect will change them to an upper case composed é (U+00C9.)
Note: Lower and upper cases have to be defined separately because they each have their own Unicode code points.

Typing Accented Consonants like Ŵ

w^-->\u0175
W^-->\u0174

Typing ꞌ as the Character for Glottal Stop

Many languages need to type a character for glottal stops. It is not recommended to use the apostrophe (U+0027) or the right single quotation mark (U+2019) since they are punctuation. Instead it is recommended that you use either the Latin Small Letter Saltillo (U+A78C) or the Modifier Letter Apostrophe (U+02BC) since they are word forming characters and not punctuation.
To implement this auto correction you will need to select a key on your keyboard that will then be corrected. Typically, a key that looks like the character you want to type is easiest to remember. So the acute accent key “`” or the apostrophe key “’” are the keys on the English keyboard that most look like the glottal stop character. You could use whatever key is easy for you to remember.

`-->\uA78C

Now, when an “`” acute accent is typed, autocorrect will change it to a Saltillo (U+A78C).

      –or–

'-->\uA78C

Now, when an “’” apostrophe key is typed, autocorrect will change it to a Saltillo (U+A78C).
Note: If you would prefer to use the Modifier Letter Apostrophe instead of the Saltillo, then replace \uA78C with \u02BC.

Typing ꞌ as Part of Velar Nasal Character (ngꞌ)

Many languages need to type ngꞌ to represent a velar nasal. We recommend you use one of the two characters shown in the above section for this.

Activate your autocorrect.txt file

After putting the lines of code into the autocorrect.txt file and saving it as a UTF-8 text file in the project directory, there is one more thing to do.  You must close Paratext if it was open and restart it.  Then you can test your file in any window that accepts the vernacular text.  If the results aren’t what you expected, you can close Paratext, modify the file, and open Paratext again until you get it right.

We hope this will save you many many keystrokes!

And how to fix them if it’s too late

Now that we have been doing migrations of Paratext data for quite some time, we have put together a list of things that should be considered at the time of migration.  This is great news if you are at the point of migrating your Paratext 7 project to Paratext 8. But don’t worry, even if you have already completed the migration, we’ve provided instructions for you too. It isn’t too late, but you might have some extra steps involved. Please read through the list below, and follow these topics to the website for more information if you should deal with any of these issues.

One of the powerful new features in Paratext 8 is the ability to track your progress and to automate checks through the Assignments and Progress window. Progress tracking requires that a project has been assigned a project plan.  If you are the project administrator, you can learn how to do this from our Project Plan video tutorials. If a project plan is in place, this blue icon will appear in the upper right-hand corner of the project window.

Clicking the blue icon will open the Assignments and Progress window for the current book, and depending on whether you are a translator or an administrator, you will see either My Tasks or All Tasks. Tasks are marked complete here one at a time.  Below is an example for the book of Genesis.

This process is fine for new work, but what if you have several books completed when the project was migrated to Paratext 8?  It can be time consuming to individually mark all the tasks for all the books that you have already completed.  Fortunately, there is a much faster way!

Stages Table

There is a table that allows you to mark stages as complete per book. You can select the stages table view by clicking on the drop down arrow to the right of All/My Tasks and selecting Stages Table.    Below is an example of the stages table for an older project. (The project is using the 6-stage SIL project plan.)

In this view, the project administrator can mark whole stages and all the tasks they contain as complete–much faster than marking tasks one at a time!  As stages are checked off, Paratext runs all the checks for the next stage. It is common for Paratext to find issues as it runs the checks on older projects, because Paratext has more rigorous checks than previous versions. In the above example you can see that Matthew, Mark, Luke and John all have issues in the third stage that need to be corrected.  Starting that process is as easy as clicking on the blue links in the In Progress column and resolving the issues found by each check.

If the project plan that was applied to your migrated project does not accurately reflect the completed work, you or your project administrator can quickly bring it up to date with the Stages Table.