Formatting Sermons

Paragraphs

Paragraphs are the easiest formating to create in a sermon file. Every line of text is a new paragraph and blank lines are ignored. Each consecutive paragraph after the first will be automatically indented.

This is the first paragraph.
This is the second paragraph. This paragraph will be indented.

This is the third paragraph. This paragraph will be indented. Also, the blank line between this paragraph and paragraph two will be ignored.

Headings

Headings provide a title to the text that follows.

Headings also have special meaning in sermon files; headings are automatically used in the Contents Pane when you compile the sermon file resource.

To create a heading, start a line of text with one or more exclamation points (!) followed by a space.

Heading 1
!! Heading 2
!!! Heading 3
!!!! Heading 4
!!!!! Heading 5
!!!!!! Heading 6

Emphasis

Normal Emphasis

To apply normal emphasis to text, place a slash (/) immediately before and after the text.

Normal emphasis is rendered with /italics/.

Strong Emphasis

To apply strong emphasis to text, place an asterisk (*) immediately before and after the text.

Strong emphasis is generally rendered as *bold text*.

Lists

Lists are used to represent lists of information. Lists can be unordered (bulleted) or ordered (numbered).

To create an unordered list, start each line of text with an asterisk (*) followed by a space.

* one
* two
* three

To create an ordered list, start each line of text with a “number sign” (#), a period (.), and a space.

1. one
   #. two
   #. three

Nested lists are also supported; simply indent lines with spaces, and make sure that lines that should be part of the same list have the same indentation.

1. one
   #. two
     * inner
     * list
   #. three

Line Breaks

To add a line break to a stream of text, use two backslashes (\\) with a space on either side.

* first item
* second item
with a line break
* third item

Tables

To create a table, start a line with a “vertical line” (|) followed by a space. The text after the vertical line will be displayed in the first cell of the first row of the table. To add another cell to the first row, the line must contain another vertical line with a space on either side. The text after the second vertical line will be displayed in the second cell of the first row of the table. This can be repeated for any number of cells.

To end the first row, the line must end with a vertical line. To add another row to the table, simply create another row of cells in the same fashion on the next line in the Wiki document.

Horizontal Lines

Horizontal lines provide a rudimentary way to separate the text above the line from the text below the line.

To create a horizontal line, simply type four hyphens (-) alone on a line.

Paragraph above.
----
Paragraph below.

Hyperlinks

Hyperlinks are a way to put additional information in your resource by linking to relevant material inside Libronix.

·                     Each hyperlink is delimited on the left by two left square brackets ([) and on the right by two right square brackets (]).

·                     Each hyperlink can contain an optional vertical line (|), which separates the displayed text—the text before the vertical line—from the data type reference—the text after the vertical line. If the vertical line is not provided the data type portion will be rendered in its long form (Bible:Jhn 1:1 will show as “John 1:1”).

·                     Each hyperlink must contain a data type reference, which should be written in one of two forms.

o                                        Parsed Reference – There are two parts to a parsed reference, which are separated by a colon (:). The first part is the data type; in the case of a Bible verse, the data type would be Bible. The second part is the text that should be understood as a reference of that data type; in the case of a Bible verse, it could be something like John 1:1 or Jhn 1 1.

o                                        Data Type Reference – This syntax uses the internal Libronix data type reference, for example bible.19.23.1, which means “Psalm 23:1”.

Open your bible to Jhn 1:1.
Open your bible to Gen 1:1.
Open your bible to John 1:1.
Open your bible to bible.1.1.1.

Segments

Each segment is delimited on the left by two left curly brackets ({) and on the right by two right curly brackets (}). Segments require at least one attribute.

Segment Attributes

The segment attributes are added immediately after the second left curly bracket ({). The segment attributes should always be separated from any following text by a single space.

Cue Attribute

The Cue attribute is a visual style associated with the segment.

To specify the Cue style, use an “at” symbol (@) followed by Cue.

Ask the audience to rise for the reading of scripture.

Language Attribute

The language of the text contained by a segment can be specified with this attribute.

To specify the language, use a colon (:) followed by the two- or three-letter language code. Only one language should be specified per segment.

Do you speak español?

Blockquotes

Blockquotes are delimited above with a line of three left curly brackets ({) followed by a quotation mark (”) and below with a line of three right curly brackets (}).

Paragraph above.
}
Paragraph below.

Escaped Characters

Place a tilde (~) immediately before a punctuation mark to prevent it from being recognized as Wiki markup.

~* I don~'t ~/want/ this
~* to be a list, so I use
~* a tilde (~~).[1]

----

[1]Logos Research Systems, I. Libronix DLS Sermon File Addin Help.