Scripture URL Strategy on Scriptures.lds.org

by Larry Richman on January 29, 2007

For instructions on URLs for the languages on the new scriptures site, see the post on December 7, 2010.

The Church recently released an upgrade of the scriptures program at scriptures.lds.org. The following information explains the logic of the URLs to assist those who have referenced scriptures on their Web sites.

Example: http://scriptures.lds.org/en/2_ne/1/13-14,16#13

Domain name: scriptures.lds.org

Language: In the example above, en stands for English. The language codes for other languages currently available at scriptures.lds.org are as follows: en for English, de for German, es for Spanish, fr for French, and it for Italian. We use the ISO 639.2 language codes. If the language is not specified, it will default to English.

Reference: In the example above, 2_ne/1/13-14,16 is the book, chapter, and verse, patterned after printed references, with a forward slash separating each element.

  • Book name: To see the list of the abbreviations of book names to use in the URL, click here, then click the word Abbreviations.
  • Chapters are simply entered as the chapter number.
  • Verses can be entered as a single verse (for example: 1), or as a contiguous set of verses using a single hyphen (for example: 13-14), or as a set of verses separated by commas (for example: 8,12). You can also create combinations of contiguous verses and single verses (for example: 1-8,12-15,20). There should be no spaces when entering verses. If you provide verse numbers, these verses will be automatically highlighted in the chapter.
  • Automatic Scroll. You can also add a Goto marker (for example, 2_ne/1/13-14,16#13) to automatically scroll to a particular verse in the chapter. This is optional and not required, but can be very helpful to direct the user to a specific verse.

You can also reference a footnote in a scripture as follows: http://scriptures.lds.org/en/2_ne/9/51b

In this example, 2 Nephi 9:51 has footnote b for verse 51 which is Eccl. 1:3.

{ 16 comments… read them below or add one }

Leave a Comment

Previous post:

Next post: