Paratext - Using Scripture Reference Settings and the References Check

Extracted text from Scripture_Reference_Settings_Shared.pptx:

Scripture Reference Settings New in Paratext 7.3

What is a Scripture Reference?

A scripture reference is any biblical text which directs the reader to a chapter or verse.

Many different forms:

1. Matthew 2

2. 1Co 13:8

3. 2Ki 23.2; 24.14, 15; 2Ch 36.9-10

What does the Scripture Reference Settings tool do?

The Simple Version:

It looks through a project to find any markers which contain references and tries to check if they are correct. John 3:16a Jonn 31:6 r

What does the Scripture Reference Settings tool do?

It allows us to specify rules about how references should appear in a project The Scripture Reference Settings dialog configures the References Check, which verifies whether all references: Are correct (spelling, punctuation) Are consistent (spelling, abbreviations, punctuation) Refer to locations which really exist (in the versification your project is using) Also ensures that cross reference callers appear in the text.

References Check

What do we mean by correct and consistent references? (spelling, punctuation)

1. 1 John
2. 1John 3. 1Jon

= correct long book name in this project (inconsistent) (incorrect)

4. 1 Jhn
5. Acts 2:4

(inconsistent) = correct c-v separator for this project

6. Acts 2.4

(inconsistent punctuation)

References Check

What do we mean by locations which really exist? Simple typos: Acts 3.4-8 1. Acts 3.4.8 2. Acts 3.48 3. Acts 34.8 Intended reference (invalid, non-existent) (non-existent) (non-existent) Possible to write

Mis-typed valid references may result in other unexpected valid references

The intended reference may have been Acts 3.1-8

References Check

More about locations which really exist: The tool checks whether verses CAN exist in this versification, not whether they DO exist: Are there DC books in this project? Be careful with imported references. They may use a different versification model Custom versification may affect the validity of references

What doesnt the Scripture Reference Settings tool do?

There are many styles/formats of scripture reference which a project could employ. Some are impossible to check completely. Because the tool is new, we are finding new challenges for it (for the developers) every day. It doesnt tell you whether your cross reference is a good choice in terms of content (it is not a database of approved x-refs) It wont do anything bad to your text.

Where is it?

PROJECT > SCRIPTURE REFERENCE SETTINGS

It is in two parts:

1. A place to visually specify the rules for appearance of references:

It is in two parts:

1. A place to visually specify the rules for appearance of references:

It is in two parts:

2. A place to run the check:

CHECKING > RUN BASIC CHECKS > REFERENCES

Do we need a tool for this?

Could we check a whole text manually? GNTUK \ior \r Number of References 431 680

\x \xo \xt \fr Total:

3608 3608 3608 (x?) 2301 14000+

A study bible may include many more

Do we need a tool for this? (continued)

Computers: Good at checking Good at identifying patterns. Bad at interpretation. See only what is really there. Quick and accurate at repetitive tasks. Humans: Bad at checking and being consistent Can understand complex patterns intuitively, if we know the general rules. But that means we often see what we expect to see, not what is really there. Not good at boring, repetitive tasks.

Getting Started:

We need to tell Paratext the rules

(you cant just open the tool, and click OK) The rules will be decided for a WHOLE project and are usually entered by one person. We need to decide the rules carefully.

Here is why

Scripture Reference Examples

Scripture References take MANY valid forms, Genesis 1 Genesis 1:10 Gen 1.10 (book, chapter only) (book, chapter verse) (abbreviated, punctuation)

Gen1.1-10 Gen 1:110

(range)

Gn 1:1,10

(sequence)

Gen 1:1-10,12; 12:1-3; Exo 1:1 (combination)

Making sure it works

With so many correct ways to represent scripture references, we need to know: What type of references (markers) exist which can be checked by Paratext What they should look like in this project

Scripture References which Paratext will check: Marker \ior

Description Describes a section of scripture in a book introduction A parallel passage reference usually in a section heading Cross reference The origin verse of a cross reference The target verse for a cross reference The verse(s) which a footnote refers to

Example \io1 Jesus' public ministry in Galilee \ior (1:149:50)\ior* \s1 The Preaching of John the Baptist \r (Mark 1.1-8; Luke 3.1-18; John 1.19-28) \x + \xo 1.2 \xt Act 18.1.\x* \x - \xo 1.2 \xt Act 18.1.\x* \x - \xo 1.2: \xt Act 18:1\x* \f + \fr 2.10: \fq But; \ft some manuscripts have \fq For.\f*

\r

\x \xo \xt \fr

(being checked in PT7.5 [and 7.4?])

What are you working with? New Project Format of references (in Paratext) is flexible Existing Project Format/style of references already exists Determine whether this format can be checked fully. Consider modifying style if checking is desirable/necessary.

Develop a format which can be checked

Things to consider: The visual style of text in Paratext is not final.

A type-setter may be able to change the appearance of references when the project is printed without affecting the text.

Lets see how it works

Lets See How it Works...

Defining Scripture Reference Format

In existing projects, \toc markers have usually defined the names and abbreviations used for references in a text. If your project already has \toc markers, the tool will see them and use them However, \toc markers are no longer necessary in a text. Entries in the book names tab of the scripture reference settings tool supercedes \toc markers

Open Scripture Reference Settings:

Click on a project window, go to: PROJECT > SCRIPTURE REFERENCE SETTINGS

Getting Started: Defining Book Names

Current styles for \r and \x in project determine what to choose here

Getting Started: Defining Scripture Reference Format

Examine parallel passages and cross references to see which \toc markers they use:

Parallel passage references: \r

These references look like \toc3

Getting Started: Defining Scripture Reference Format

Cross references: \x \xo \xt This looks like \toc3

In Scripture Reference Settings:

Convention of references in the text should follow convention in the table of contents.

The format of: Parallel Passage References (\r)

and Cross References (\x \xo \xt)

Should be the same as book names in either: \toc2 or \toc3

Getting Started: Defining Reference Format

WYSIWYG. For existing projects:

Get started with the tool by making items in this Verses which span books window look like cross references in your project. or chapters

Verses within a chapter

If youre not sure whether youve entered everything correctly here run the check and look at the type and amount of errors generated.

Some traps to avoid: Think ahead

Using the settings shown above, both of the following examples are valid: Mat 1.1-3 Mat 1.1,3 However if the user was trying to type Mat 1.1-3, the second reference would be an undetectable typing error (and vice versa). Paratext would check these references and detect no problem.

Some traps to avoid: Think ahead

Dash with a space = error Comma with no space = error Otherwise, every range or list of verses could be valid

Recommended Solution: Include a space after the comma for List of Verses: Mat 1.1, 3

Some traps to avoid: Think ahead

a. Range of Verses:

Mat 1.1-3

(hyphen)

b. Range of Chapters: Mat 1.1-3.1 (hyphen) With these settings, Paratext would not be able to determine whether b is a correct range of chapters OR a range of verses with something accidentally typed on the end (should it be: Mat 1.1-31?)

Range of Chapters:

Mat 1.13.1 (en-dash)

Now Paratext knows that example b isis either a range Reminder : The style of text in Paratext not final and of chapters written incorrectly (no en-dash) or its a could prevent checking. range of verses containing a typo (final .1). A type-setter can change the appearance of some choices when the project is printed.

Ready for checking

Think ahead wherever possible, adapt settings if necessary. Choose unambiguous settings which will enable Paratext to identify errors.

Spaces, dashes and special punctuation can be modified by type-setter without affecting the text were not choosing styles in Paratext.

Summary so far

By applying rules for how your project will handle references, it is possible to ensure all cross references and parallel passages are consistent and valid. Agree on rules Enter choices in scripture reference settings Input project text Run References Check References will be valid, locations accurate.

Checking Scripture References

Run Basic Checks > References

Checking Scripture References

Checking Scripture References Errors have meaningful descriptions to help you resolve them. Multiple similar errors may indicate a problem with choices in scripture reference settings. If you fix an error, but it doesnt go away, there may have been more than one error in that reference. References containing more than one error will show only the first error Paratext detects.

Finally

1. Ensure Scripture Reference Settings is configured correctly for your project and uses a checkable format. Remember that how things look in Paratext does not determine how things look in a printed text. Paratext is for getting content right, not format.
2. Run the References check on and resolve errors. Re-run the check often to see whether errors have crept in.