1 Introduction

One of the nice features of XLingPaper is that since it requires one to mark-up the document data, that data is then “actionable” (Simons and Black 2009, Black 2009). Perhaps the easiest way to see how such data is “actionable” is via the use of publisher style sheets. Each publisher style sheet dictates how an XLingPaper document is to be formatted. The page size and margins, order of front matter and back matter, layout of reference material, etc., etc., can be determined by a publisher style sheet.

Thus, one can write one's document and then associate it with a publisher style sheet to get it to format the way that a given publisher wants it. If at any point you decide to use a different publisher, you merely associate your document to the publisher style sheet for that other publisher (assuming one exists). The result is that an author has a lot less work to do when changing publishers.

This document describes how to edit an XLingPaper publisher style sheet. It assumes that the reader is using the XMLmind XML Editor. Since most users do not need to design publisher style sheets, this documentation is not as detailed as the general user documentation. Making changes to a publisher style sheet is also not necessarily as easy as making changes in an XLingPaper document.

Also, when you need to make a change to a publisher style sheet from your main document, click in the publisher style sheet (it will have a bluish background color) and then use Edit menu item / Reference / Edit Referenced Document (or type Ctrl+Shift+E). After making your changes, save them and then use Edit menu item / Reference / Edit Referencing Document (or type Ctrl+Shift+B). This will take you back to your main document.

Please keep in mind that the way XLingPaper works is that the publisher style sheet gives formatting information for various kinds of XLingPaper elements. If a given XLingPaper document does not happen to have an element that the publisher style sheet describes, that is not a problem. That part of the publisher style sheet is ignored. Thus, the publisher style sheet is a kind of template with many optional components.

There are several elements at the beginning of a publisher style sheet. They are all optional. Example (1) lists them in the order in which they occur and what they are for. None of them are ever used in any output.

This document is organized as follows. The basic page layout information that can be controlled via a publisher style sheet is given in section 2. How to control front matter is shown in section 3. The layout information for the main body of a document is discussed in section 4. The back matter information is in section 5. Information about the document content not already handled in 2 is given in section 6. Common sets of attributes are described in section 7. Finally, there is section 8 which gives hints on how to do things users have asked about. In addition, you can use the Index to look for things. (If you are looking for how to do something and neither section 8 nor the Index help, please write to us to we can add what you were looking for to the documentation.)

2 Page Layout

This section covers the basic layout of pages.

2.1 Page Size and Margins

The size of the page and its margins are set by the items shown in (2). The inside margin value refers to how much space there is on the inside of a page (right-hand side of the left page and the left-hand side of the right page). Similarly, the outside margin value refers to how much space there is on the outside of a page (left-hand side of the left page and the right-hand side of the right page).

(2)

Note that for the Web Page output, you can have the output ignore the page width by clicking on the pageLayout element and setting its ignorePageWidthForWebPageOutput attribute to yes. In this case, there will be no fixed page width in the web page output (i.e., it “fills” the width like the web page output does when there is no associated publisher style sheet). The ignorePageWidthForWebPageOutput attribute is ignored by both the XeLaTeX and the RenderX XEP ways of producing PDF.

Click in the black text to change a value. You may use any of the units of measure given in (3).

There should be no space between the number and the abbreviation.

If you check the “Use thesis submission style, ” then the result will be "single-sided" pages (like in theses and dissertations).

2.2 Paragraph Indents

Any indentation on a paragraph and any indentation (at both ends) for a block quote is controlled by the values shown in example (4). If you need to have different values for the left and right indents of a block quote, set the rightIndent attribute of the blockQuoteIndent element to the value for the right indent.

(4)

You can use the units of measure shown in (3) or ems. The unit of measure used for paragraph indent and for the block quote indent do not have to be the same. Do not put any spaces between the number and the unit.

Indents for hanging indent paragraphs are controlled by the values shown in example (5). These values are not normally shown. You will need to click on the blockQuoteIndent element and do an insert after command. You can then insert these elements. These can be overridden by the initialIndent and hangingIndent attributes of any hangingIndent element.

(5)

These use the same units of measure as the paragraph and block quote indents do.

The default XeLaTeX way of producing PDF normally justifies text. To get left-justified (or ragged right) output, you can insert a paragraphAlignment element after the above elements and set its textalign attribute to left.

2.3 Line Spacing

You control the line spacing via the items shown in example (6).

(6)

If you choose single spacing (the default), then the check box items are ignored. If you choose either space and a half or double spacing, then you can have the elements listed with check boxes be single spaced (as long as the check box is checked).

Please note that whenever an example is embedded within a table, the line spacing for tables will normally be used, not the line spacing for examples.

2.4 Default Font Information

The default font information for the entire document is set via the items shown in example (7).

(7)

Click in the black portion to change these values. For the font family, type in the font family name.[1] If you need Graphite capability for the default font, set the XeLaTeXSpecial attribute of the defaultFontFamily element to the appropriate values. It is crucial that you also have at least one language or type element with the exact same font family name and the exact same value of the XeLaTeXSpecial attribute. Otherwise, XLingPaper will fail to produce the default PDF output. You do not have to actually use such a language or type element, but it must be present.

Note that points are assumed for the basic point size and for the footnote size (i.e., the number must be in terms of points).

2.5 Space between footnote number and footnote content

Some publishers prefer to include extra spacing between the footnote number and its content (at the bottom of the page). If you set the contentBetweenFootnoteNumberAndFootnoteContent attribute of the pageLayout element to contain, say, a space, then this space will appear between the footnote number and the content of the footnote.

2.6 Content between consecutive footnote numbers in text

On the rare occasions when there are two consecutive footnote numbers in text, the default is to insert a comma followed immediately by a non-breaking space character. Some publishers prefer to have just the comma. If you set the contentBetweenMultipleFootnoteNumbersInText attribute of the pageLayout element to contain, say, a comma, then only this comma will appear between the consecutive footnote numbers. We recommend, however, that you use a comma followed by a word joiner character. This is so that no output formatter will break a line after the comma, resulting in the following footnote number showing at the beginning of the next line. Doing this is a bit tricky, however:

1. Click somewhere where you can type text.
2. Using the Character Tool of the XMLmind XML Editor,[2] click on the drop-down box and select the “0x2000 (General Punctuation)” section.
3. Hover your mouse over each blank box near the middle. The tool hint message should be blank, but at the bottom when it begins with “0x2060”, click.
4. This inserts a word joiner special character at the cursor. Be aware that you will not see anything different!
5. Immediately press the Shift key and then the Left Arrow key.
6. Cut. This will put the word joiner character on the clipboard.
7. Click on the pageLayout element.
8. Using the Attributes Tool of the XMLmind XML Editor, click on contentBetweenMultipleFootnoteNumbersInText in the Attribute column.
9. In the text box above the Attribute/Value table portion of the Attributes Tool, click after the comma.
10. Paste.
11. Press the Enter key.

This should then have the (invisible to us) word joiner character after the comma.

2.7 Footnote indent

Some publishers want a specified indent in the footnote text before the (superscript) footnote number. Use the footnoteIndent element to set this value overtly instead of the normal default value. You will need to overtly insert this element (it appears between footnotePointSize and footnoteLine; you will probably have to click on one of these two and then do an insert after or insert before command to get the footnoteIndent element). It will look like this:

(8)

Type your indent in the black portion. Be sure to use a number followed immediately by a unit of measure. You can use the units of measure shown in (3) or ems. Do not put any spaces between the number and the unit.

Please note that this only works for footnotes. It does not work when you use endnotes.

2.8 Footnote line separator

Many formatted articles and books use a line to separate footnote material from text and other materials on a page. The next item that controls this kind of information is given in example (9).

(9)

The RenderX XEP way of producing PDF pays attention to these attributes, except forcefootnotestobottomofpage. The XeLaTeX way of producing PDF can only process the spacebetweentextandline and forcefootnotestobottomofpage attributes. The XHTML way ignores them all. The attributes are described in example (10)

2.9 Link layout

XLingPaper has a number of hyper-link elements which can greatly aid a reader in finding material in a document. The link layout portion of a publisher style sheet controls whether or not such a hyper-link should be output in a special color and/or with some special “decoration” (such as an underline). Example (11) shows where to control these.

(11)

If you click on the first line, you can set what the default color and text decoration should be for those links which are to have some of this special marking. The various links are then shown one after the other. Those in gray are turned “off” - that is, they will not show with any special color or marking. Those in black will.

Example (12) shows the attributes you can set.

2.10 Header and Footer Layout

You can control what information goes in running headers and footers. For papers, the header and footer information is usually in the page layout section. For books, it is in the front matter layout section as well as in the body layout section, although if a different style is needed for back matter, you can also put one in the back matter. The reasoning is that papers either have one kind of header/footer for every page or at most three kinds of pages: one for the first, another for even-numbered pages and a third for odd-numbered pages. Books tend to have the last three plus the title page, but things like page numbers tend to differ between front matter (usually lower-case roman numerals) and the rest of the book (usually Arabic numbers).

There is a headerFooterPageStyles element. The attributes on this element define the default font information for all of the embedded items. See section “Font Information Attributes” for what these attributes are.

Within this headerFooterPageStyles element, one can have any of the combinations of elements shown in example (13)

When you use (13a), every page in the document will have the headers and footers indicated in this “regular” style. If you want all pages but the first to have the same header and footer, use the two elements shown in (13b).

To get different header and footer styles for odd and even pages, use (13c). If in addition, you want something different for the first page, then use (13d).

Each of the elements shown in (13) have the attributes given in section “Font Information Attributes” as well as a textalign attribute which has the values shown in example (14).

The "regular” page header and footer information is shown in example (15). There are two rows. The first is for the header and the second is for the footer. There are three columns. The first is what will show in the left part of the header/footer, the second is what will show in the middle (center) of the header/footer, and the third is what will show in the right part of the header/footer. The left material is left-aligned. The right material is right-aligned.

(15)

What is to be shown in each of these six places is controlled by putting one or more of the elements in the appropriate spot in the table. Example (16) shows the possible elements to put in these six places. When you are editing a style sheet via the XMLmind XML Editor, you will need to click on an item and then do a Replace or Convert operation. Please note that if it is empty (because it is a nothing element, you may have to click to the left (for the left-most cell), the middle (for the middle cell), or to the right (for the right-most cell) in order to select the element.

The other basic kind of page styles is to use a different first page and also use odd and even pages. This looks something like what is shown in (17). Like for “regular” pages, each of the six slots can be filled with any of the elements given in example (16).

(17)

You can also have a horizontal line appear between the header and text or between the text and the footer. You enable this by setting the attributes shown in examples (18) (for the header element) and (19) (for the footer element).[5] An easy way to select the header (or footer element) is to click on some item in it and then click on “header” (or “footer”) in the node path bar. Please note that if you are using even/odd paging, then you will need to set these on the first header and/or the first footer element (that is, for the even page). The rule will appear for both odd and even pages for the default XeLaTeX way of producing PDF. For the RenderX XEP way of producing PDF, you will need to set these for both even and odd pages.

2.11 Add line numbers to output

When submitting an article for review, some publishers want the PDF to have continuous line numbers throughout the document. Presumably this is to make it easier for reviewers to identify the location in the document for a comment. If you set the showLineNumbers attribute of the pageLayout element to yes, then the default PDF will have line numbers appear in the left margin. Please note that if you installed XLingPaper before version 2.27.0, you will also need to get and install the XeLaTeX upgrade package at http://software.sil.org/xlingpaper/resources/xelatex-upgrade/.

3 Front Matter Layout

This section discusses layouts for front matter. Typically, front matter is different for papers and books. The publisher style sheet for XLingPaper seeks to be flexible enough to handle both situations.

In reading this section, please keep in mind that while a given publisher style sheet often has formatting information for most, if not all, XLingPaper front matter elements, when a given XLingPaper document is formatted per such a publisher style sheet, only those elements contained in the XLingPaper document are actually processed.

With the exception of the title and any subtitle which always come first, the order the other front matter elements appear in the output is given by the order they appear in the front matter section of the publisher style sheet. We therefore describe the title first in section 3.1, but you can rearrange the other elements in any order you wish. These elements are discussed in section 3.2.

3.1 Title Layout

For books, there is often a separate title page containing just the title, followed by another page that has the title and some other information like author. To allow for this, you can begin a front matter layout with a titleHeaderFooterPageStyles element. It determines the headers and footers for the initial title page(s). See section 2.10 for the kinds of elements which can go within the titleHeaderFooterPageStyles element. You can then put the titleLayout element next. If there is a subtitle, you can put a subtitleLayout element either before or after the titleLayout element. The titleLayout has an useFootnoteSymbols attribute. If you set it to yes, then any footnote in the title will use a symbol instead of a number.

After these, you can put the normal front matter header/footer page style information. See section 2.10 for more on these.

For papers, you normally just begin with the titleLayout element. Like for books, you can put a subtitleLayout element either before or after the titleLayout element.

3.2 Other Front Matter Layout Elements

The non-title-related elements can be arranged in any order. Example (20) lists out these publisher style sheet elements.

Some of the XLingPaper front matter elements can occur more than once in a document (i.e author, affiliation, emailAddress and preface). If you have only one publisher style sheet layout element for these, then all instances of them will use the same formatting. If you have two or more publisher style sheet layout elements for any of these, then the first will be used for the first instance in the document, the second for the second, etc. If there are more instances in the document than there are corresponding publisher style sheet layout elements, then the last publisher style sheet layout element will be used for all of the extra instances in the document.

3.2.1 Author Contact Info Layout

Each author contact information item will be formatted in a vertical list. For the default way of producing PDF, each such vertical list is justified horizontally, with any extra ones automatically wrapping (for cases where there are many authors). For the other outputs, each such vertical list is formatted in a single table and, if there are many authors, it may run off the page.

The content of each vertical list is controlled by the set of elements contained within the authorContactInfoLayout element. The possible elements are shown in example (21).

In addition, the authorContactInfoLayout element has one attribute: textalign. This has the values shown in section 7.3 here. Note that these only work with the XeLaTeX way of producing PDF and, in addition, only work when there is but one authorContactInfo element.

4 Body Layout

This section discusses layouts for the main body of the document. For papers, this is just how the six section level elements are to be formatted. For books, you may normally want to first describe the header and footer styles for pages in the body and the back matter (unless you overtly give other header and footer style information in the back matter section). Then you can define how to format parts, chapters, and the six section levels.

For the special case of a book which is a collection of papers (i.e., it uses chapterInCollection elements instead of chapter elements), one can also describe how to format front matter and back matter embedded within each chapter. These often have different formatting than the front matter and back matter for the entire book.

All of the kinds of layouts in the body portion of a document are numbered (except, of course, for any embedded front matter and/or back matter). In some styles, one wants to format the number in a different way than the title. In other cases, one wants the number to be formatted the same way. XLingPaper allows both ways. If you need to format the number differently, then you use a numberLayout element along with the corresponding title element for the type of element being formatted (part, chapter, section1, ..., section6).

4.1 Header and Footer Styles for the Body

To set the header and footer styles for the material in the body of the document, insert a headerFooterPageStyles element at the beginning of the body layout section. See section 2.10 for information on how to set the header and footer content.

4.2 Embedded Front Matter in a Chapter in a Collection

For the special case of a book which is a collection of papers (i.e., it uses chapterInCollection elements instead of chapter elements), one can use the chapterInCollectionFrontMatterLayout element. It contains instances of the normal front matter layout elements described in section 3.2. These layout elements define how any front matter items embedded within the chapter are to be formatted.

4.3 Part Layout

For books, which can have parts, you can describe how to format the part number and title. The partLayout element contains a partTitleLayout element and an optional numberLayout element. Both of these have “title format information” attributes. See section 7.4 for more on these attributes.

In addition the partLayout element itself has one attribute as shown in example (22).

4.4 Chapter Layout

For books, which have chapters, you can describe how to format the chapter number and title. The chapterLayout element contains a chapterTitleLayout element and an optional numberLayout element. Both of these have “title format information” attributes. See section 7.4 for more on these attributes.

In addition the chapterLayout element itself has three attributes as shown in example (23).

The chapterTitleLayout element also has the attributes given in (24).

4.5 Chapter in Collection Layout

For books which are collections of papers (i.e., use chapterInCollection elements instead of chapter elements), you can describe how to format the chapter number and title. The chapterInCollectionLayout element contains a chapterTitleLayout element and an optional numberLayout element. Both of these have “title format information” attributes. See section 7.4 for more on these attributes.

In addition the chapterInCollectionLayout element itself has one attribute as shown in example (25).

4.6 Section Level Layouts

For sections, each level has its own section layout element. Within this layout element, one has a sectionTitleLayout and an optional numberLayout. The sectionTitleLayout element indicates how the title is to be formatted while the numberLayout element indicates how the number of the section is to be formatted.

The attributes for the main section layout elements (i.e., section1Layout, section2Layout, section3Layout, section4Layout, section5Layout, and section6Layout) are shown in example (26).

In addition the section1Layout element has an attribute startSection1NumberingAtZero which can be set to either yes or no. The default value is no. If it is set to yes, then the first section level one element will have a number of 0 (zero), the second will have a number of 1, etc.

The attributes for the embedded sectionTitleLayout element and any numberLayout element are given in section 7.4. In addition, the sectionTitleLayout element has another attribute: useperiodafternumber. If there is no numberLayout element and you need to have a period appear after the section number, set useperiodafternumber to yes.

4.7 Short Subsections Layout

If your document needs to format short subsections, you can insert a shortSubsectionLayout element after the section6Layout element. It has one element within it (shortSectionTitleLayout) which indicates how the title of any and all short subsections should be formatted.[7] This has the the same set of attributes as a sectionTitleLayout element except the useperiodafternumber attribute is not present. See section 7.4. In addition, the shortSubsectionLayout element has all of the attributes given in example (26) except that the showNumber attribute's value is always set to no.

4.8 Embedded Back Matter in a Chapter in a Collection

For the special case of a book which is a collection of papers (i.e., it uses chapterInCollection elements instead of chapter elements), one can use the chapterInCollectionBackMatterLayout element. It contains instances of many of the normal back matter layout elements described in section 5. These layout elements define how any back matter items embedded within the chapter are to be formatted. Note that there is no instance of headerFooterPageStyles since the paging used will be that of the body. In addition, for references, one only uses the referencesTitleLayout element. The formatting of the reference material itself uses the reference formatting of the entire volume (this guarantees consistency throughout the volume).

Finally, there is no indexLayout. The assumption is that if the volume has an index, it will be for the entire volume, not for a given paper/chapter.

5 Back Matter Layout

This section discusses layouts for back matter. In reading this section, please keep in mind that while a given publisher style sheet often has formatting information for most, if not all, XLingPaper back matter elements, when a given XLingPaper document is formatted per such a publisher style sheet, only those elements contained in the XLingPaper document are actually processed.

Normally, the header and footer page styles of the back matter is the same as that of the body of the document. If you need different header and footer styles for the material in the back matter, insert a headerFooterPageStyles element at the beginning of the back matter layout section. See section 2.10 for information on how to set the header and footer content.

The order the back matter elements appear in the output is given by the order they appear in the back matter section of the publisher style sheet. Example (27) lists out these publisher style sheet elements.

Some of the XLingPaper back matter elements can occur more than once in a document (i.e., appendix, glossary, and index). If you have only one publisher style sheet layout element for these, then all instances of them will use the same formatting. If you have two or more publisher style sheet layout elements for any of these, then the first will be used for the first instance in the document, the second for the second, etc. If there are more instances in the document than there are corresponding publisher style sheet layout elements, then the last publisher style sheet layout element will be used for all of the extra instances in the document.

5.1 Appendices Title Page Layout

Some publishers or educational institutions want a separate page containing the words “Appendices” before the first appendix (when there are more than one). You can describe how to format this appendices title page via the appendicesTitlePageLayout element. It has “title format information” attributes. See section 7.4 for more on these attributes.

In addition the appendicesTitlePageLayout element itself has one other attribute as shown in example (28).

5.2 Appendix Layout

You can describe how to format the appendix “number” and title. The appendixLayout element contains an appendixTitleLayout element and an optional numberLayout element. XLingPaper expects the latter to be used with books. Both of these have “title format information” attributes. See section 7.4 for more on these attributes.

In addition the appendixLayout element itself has one attribute as shown in example (29).

Also, the appendixTitleLayout element itself has two other attributes as shown in example (30).

5.3 References Layout

This section outlines how to control the way reference material is to be formatted in a references section of a document. Since this portion of a publisher style sheet can be in an independent file, it has several top level elements as shown in example (31). They are all optional. None of them are ever used in any output.

The key idea to keep in mind when creating reference layout information in an XLingPaper publisher style sheet is that the layout elements are used to define patterns. When a given referenced work is to be output, XLingPaper compares the information in the referenced XLingPaper refWork element to these patterns and uses the pattern that matches the information in the referenced work. If no pattern is found, then XLingPaper will output a message for this work indicating that no pattern was found and also indicating which elements the referenced work needs to be in a pattern. You can then use this message information to construct the missing pattern.

We recommend ordering the patterns for a given layout in longest first order.

Unlike other items in the back matter, the reference layout information must be ordered in a pre-specifed way. Each subsection below describes each one of these elements in turn. In the tables, there are four columns. The first gives the element name used in the publisher style sheet. The second describes what that element controls. The third refers to the set of attributes that element has for controlling formatting. The fourth gives the canned text that will appear for this element in the XMLmind XML Editor.

In addition, section 5.3.17 delineates the attributes which can be on the referencesLayout element itself.

5.3.1 Author layouts

The refAuthorLayouts element contains one or more refAuthorLayout elements, each of which provides a pattern for the author- and date-related information of a referenced work. An author pattern defined within a refAuthorLayout can consist of one or more of the elements given in example (32).

After the set of refAuthorLayout elements, one may also insert a refAuthorLastNameLayout element. This controls the layout of any refAuthorLastName elements. See section “Font Information Attributes” for the available options.

5.3.2 Article in a Journal Layouts

The articleLayouts element contains one or more articleLayout elements, each of which provides a pattern for the information of an article referenced work. An article pattern defined within an articleLayout can consist of one or more of the elements given in example (33).

For backwards compatibility purposes, there also are two other elements: urlItem and dateAccessedItem. You are advised, however, to not use either of these elements directly. Instead, use the urlDateAccessedLayoutsRef element. It will mean defining fewer patterns.

5.3.3 Book Layouts

The bookLayouts element contains one or more bookLayout elements, each of which provides a pattern for the information of a book referenced work. A book pattern defined within a bookLayout can consist of one or more of the elements given in example (34).

For backwards compatibility purposes, there also are two other elements: urlItem and dateAccessedItem. You are advised, however, to not use either of these elements directly. Instead, use the urlDateAccessedLayoutsRef element. It will mean defining fewer patterns.

5.3.4 Paper in a Collection Layouts

The collectionLayouts element has one attribute: flipFirstAuthorName which can have one of two values: yes or no. The default is yes. If the value is no, then collection editors' names are not reversed, but will appear in the order they occur in the corresponding refAuthor element.

The collectionLayouts element contains one or more collectionLayout elements, each of which provides a pattern for the information of a collection referenced work. A paper in a collection pattern defined within a collectionLayout can consist of one or more of the elements given in example (35).

For backwards compatibility purposes, there also are two other elements: urlItem and dateAccessedItem. You are advised, however, to not use either of these elements directly. Instead, use the urlDateAccessedLayoutsRef element. It will mean defining fewer patterns.

5.3.5 Dissertation Layouts

The dissertationLayouts element contains one or more dissertationLayout elements, each of which provides a pattern for the information of a dissertation referenced work. A dissertation pattern defined within a dissertationLayout can consist of one or more of the elements given in example (36). Please note that every dissertation pattern is expected to have a dissertationLabelItem element in it.

For backwards compatibility purposes, there also are two other elements: urlItem and dateAccessedItem. You are advised, however, to not use either of these elements directly. Instead, use the urlDateAccessedLayoutsRef element. It will mean defining fewer patterns.

5.3.6 Field Notes Layouts

The fieldNotesLayouts element contains one or more fieldNotesLayout elements, each of which provides a pattern for the information of a fieldNotes referenced work. A field notes pattern defined within a fieldNotesLayout can consist of one or more of the elements given in example (37).

For backwards compatibility purposes, there also are two other elements: urlItem and dateAccessedItem. You are advised, however, to not use either of these elements directly. Instead, use the urlDateAccessedLayoutsRef element. It will mean defining fewer patterns.

5.3.7 Manuscript Layouts

The msLayouts element contains one or more msLayout elements, each of which provides a pattern for the information of a ms referenced work. A manuscript pattern defined within a msLayout can consist of one or more of the elements given in example (38).

For backwards compatibility purposes, there also are two other elements: urlItem and dateAccessedItem. You are advised, however, to not use either of these elements directly. Instead, use the urlDateAccessedLayoutsRef element. It will mean defining fewer patterns.

5.3.8 Paper Presented at a Conference Layouts

The paperLayouts element contains one or more paperLayout elements, each of which provides a pattern for the information of a paper referenced work. A paper presented at a conference pattern defined within a paperLayout can consist of one or more of the elements given in example (39).

For backwards compatibility purposes, there also are two other elements: urlItem and dateAccessedItem. You are advised, however, to not use either of these elements directly. Instead, use the urlDateAccessedLayoutsRef element. It will mean defining fewer patterns.

5.3.9 Paper in a Proceedings Volume Layouts

The proceedingsLayouts element contains one or more proceedingsLayout elements, each of which provides a pattern for the information of a proceedings referenced work. A paper in a proceedings volume pattern defined within a proceedingsLayout can consist of one or more of the elements given in example (40).

For backwards compatibility purposes, there also are two other elements: urlItem and dateAccessedItem. You are advised, however, to not use either of these elements directly. Instead, use the urlDateAccessedLayoutsRef element. It will mean defining fewer patterns.

5.3.10 Thesis Layouts

The thesisLayouts element contains one or more thesisLayout elements, each of which provides a pattern for the information of a thesis referenced work. A thesis pattern defined within a thesisLayout can consist of one or more of the elements given in example (41). Please note that every thesis pattern is expected to have a thesisLabelItem element in it.

For backwards compatibility purposes, there also are two other elements: urlItem and dateAccessedItem. You are advised, however, to not use either of these elements directly. Instead, use the urlDateAccessedLayoutsRef element. It will mean defining fewer patterns.

5.3.11 Web Page Layouts

The webPageLayouts element contains one or more webPageLayout elements, each of which provides a pattern for the information of a webPage referenced work. A web page pattern defined within a webPageLayout can consist of one or more of the elements given in example (42).

For backwards compatibility purposes, there also are two other elements: urlItem and dateAccessedItem. You are advised, however, to not use either of these elements directly. Instead, use the urlDateAccessedLayoutsRef element. It will mean defining fewer patterns.

5.3.12 Published Dissertation or Thesis Layout

The section describes the publishedLayout element which is used to create a common pattern for published dissertations and theses. The pattern consists of one or more of the elements given in example (43).

5.3.13 Location and/or Publisher Layouts

The locationPublisherLayouts element contains one or more locationPublisherLayout elements, each of which provides a pattern for the information of those reference work elements that contain a location and/or publisher element or neither. A locationPublisherLayout can consist of one or more of the elements given in example (44).

5.3.14 URL and/or Date Accessed Layouts

The urlDateAccessedLayouts element contains one or more urlDateAccessedLayout elements, each of which provides a pattern for the information of those reference work elements that contain a url and/or dateAccessed element and/or doi element or none of these. A urlDateAccessedLayout can consist of one or more of the elements given in example (45).

5.3.15 ISO 639-3 Code Layout

The iso639-3codeItem is optional and only needed if any of your documents will show one or more ISO 639-3 codes for each reference work. In addition to the attributes given in section “Format Information Attributes”, it has the attributes shown in example (46).

5.3.16 Change in Authors' names

When there are two or more authors in a cited work, sometimes a publisher will want you to use "and" before the last author and sometimes they will want you to use "&". XLingPaper now has a way for you to key these one way and change them on a per publisher style sheet basis. You do this by inserting a refAuthorNameChange element at the end of the “References Layout” portion of the publisher style sheet. The refAuthorNameChange element has two attributes: from and to. Key the material to match in the from attribute and then key the replacement in the to attribute

You should add a space before and after the values to make sure there are no unintentional changes.

Further, this only works for the name and citename attributes of a refAuthor element. For other instances such as for editor related elements, we suggest you create a new type element for this and set its before attribute to the value you usually use. Then replace all instances in editor-related elements to use an object element set to this type. When it needs to change, modify the before attribute of this type element to be what you need.

5.3.17 Attributes on the referencesLayout element

Besides the various reference types discussed in sections 5.3.1–5.3.15, there are some special attributes on the referencesLayout element itself. These control more global characteristics of the reference material. These attributes are shown in example (47).

6 Document Content Layout

This section discusses layout information for various items occurring within the content of a document. The only element in this section that is required is exampleLayout. All others are optional. They are described in the order in which they must appear. See appendix A for hints about where to insert a new element in this portion of a publisher style sheet. Also, see appendix B for what values will be used if an element is not present.

6.1 Controlling the Display of Paragraphs

Some style sheets require extra space before and after paragraphs. One can use the spacebefore and spaceafter attributes of the paragraphLayout element to set these values. See these attributes in section “Front Matter Format Information Attributes”.

6.2 Controlling the Display of Examples and Example Numbers

The exampleLayout element determines how examples and their numbers are to be displayed. The attributes involved are given in example (48).

6.3 Controlling the Display of Lists

Some style sheets require specific indents for lists. One can use the indent-before attribute of the listLayout element to set this indent. See this attribute in section “Controlling the Display of Examples and Example Numbers”. If you need a list indent of 0pt, please use something slightly different such as 0.0pt or 0in. This will guarantee that it comes out with no indent.

Another attribute available for controlling list output is the spacebetween attribute. Enter the amount of extra vertical space needed between list items such as 6pt.

6.4 Controlling the Display of Section References

There are two elements that control how section reference numbers and section reference titles are displayed.

6.4.1 Section Reference Number Layout

The sectionRefLayout element determines how section reference numbers are to be displayed. The attributes involved are given in example (49).

6.4.2 Section Reference Title Layout

The sectionRefTitleLayout element determines how section reference titles are to be displayed. All of its attributes are described in section “Format Information Attributes”.

6.5 Controlling the Display of Appendix References

There are two elements that control how appendix reference letters/numbers and appendix reference titles are displayed.

6.5.1 Appendix Reference Number Layout

The appendixRefLayout element determines how appendix reference letters/numbers are to be displayed. The attributes involved are given in example (50).

6.5.2 Appendix Reference Title Layout

The appendixRefTitleLayout element determines how appendix reference titles are to be displayed. All of its attributes are described in section “Format Information Attributes”.

6.6 Controlling the Display of Interlinear Source Style

How an interlinear source reference (i.e., the interlinearSource element in an XLingPaper document) is to be displayed is controlled by the interlinearSourceStyle element. Its attributes are given in section “Format Information Attributes”, except that none of these attributes show in the XMLmind XML Editor for the interlinearSourceStyle element. What does show is given in example (51).

(51)

There are three choices for where the interlinear source information is to appear as described in example (52). Click on the one that you want to use.

6.7 Controlling the Display of Interlinear Reference Citation Titles

The interlinearRefCitationTitleLayout element determines how interlinearRefCitation elements are to be formatted when their showTitleOnly is set to either short or full. All of its attributes are described in section “Format Information Attributes”, except that none of these attributes show in the XMLmind XML Editor for the interlinearRefCitationTitleLayout element.

6.8 Controlling the Spacing between Aligned Words in Interlinears

You can control how much spacing there is between aligned word units in an automatically wrapped interlinear via the interlinearAlignedWordSpacing element. It only has the three “special” attributes although currently only the XeLaTeXSpecial attribute will make a difference and that only with the interlinear-aligned-word-skip attribute value set equal to a TeX ‘glue’ value: a basic point value plus a stretch point factor minus a shrink point factor. The default ‘glue’ value used by XLingPaper is 6.66666pt plus 3.33333pt minus 2.22222pt (this is what is used by Kew & McConnel 1990:56). If this is too much or too little for the publisher, you can change it. For example, if you wanted to reduce the default value by one point in all three factors, you would set the XeLaTeXSpecial to interlinear-aligned-word-skip='5.66666pt plus 2.33333pt minus 1.22222pt'.

6.9 Controlling the Indent for and Spacing Between Non-initial Interlinear Line Groups

Sometimes one wants to control the indent and/or the vertical spacing between line groups when there is more than one such line group within an interlinear display.

Both of these are attributes on the interlinearMultipleLineGroupLayout element. The indentOfNonInitialGroup attribute sets the indent. Use a number followed immediately by a unit of measure (see example (3)).

The vertical spacing between units is controlled by the spaceBetweenGroups attribute. Use a number followed immediately by a unit of measure (see example (3)). Note that this attribute does not work for web page or EBook outputs.

6.10 Controlling the Formatting of Interlinear Texts

Sometimes one wants to control the vertical spacing between interlinear items in an interlinear text. Use the interlinearTextLayout element.

The vertical spacing between units is controlled by the spaceBetweenUnits attribute. Use a number followed immediately by a unit of measure (see example (3)).

The amount to indent the first line of an interlinear text can be overridden by setting the indentOfInitialGroup attribute. Use a number followed immediately by a unit of measure (see example (3)). This only works for the XeLaTeX way of producing PDF and only when doing automatic wrapping of the interlinear.

One can also control the text that comes before and after the text reference number. Use textbeforeReferenceNumber and textafterReferenceNumber, respectively.

6.11 Controlling the Display of Endnote References

The endnoteRefLayout element determines how endnoteRef elements are to be formatted. All of its attributes are described in section “Format Information Attributes”, except that none of these attributes show in the XMLmind XML Editor for the endnoteRefLayout element. In particular, if you want to change the text that comes before the referred to endnote number, use the textbefore attribute (the default value is “See footnote ”).

6.12 Controlling the Display of Figures

The next three main elements describe how figures are to be displayed and how figure references are to be handled.

6.12.1 Figures

The figureLayout dictates how figure elements are to be displayed. This can look like what is shown in example (53).

(53)

The align attribute of the figureLayout element can be set to define the default alignment of all figures in the document as shown in example (54).

There are actually four parts here.

6.12.1.1 Figure and its Caption

If you click on the first line, you control the figureLayout element. This has five attributes as shown in (55).

6.12.1.2 Figure Label Layout

If in example (53), you click on the word “Figure” in the second line, you can control information about how the label of the figure is to be formatted. The attributes for this figureLabelLayout element are given in example (56).

6.12.1.3 Figure Number Layout

If in example (53), you click on the digit “1” in the second line, you can control information about how the number of the figure is to be formatted. The attributes for this figureNumberLayout element are given in example (57).

6.12.1.4 Figure Caption Layout

If in example (53), you click on “Caption goes here” in the second line, you can control information about how the captions of figures are to be formatted. The attributes for this figureCaptionLayout element are given in section “Format Information Attributes”.

6.12.2 Controlling the Display of Figure References

There are two elements that control how figure reference numbers and figure reference captions are displayed.

6.12.2.1 Figure Reference Number Layout

The figureRefLayout element determines how figure reference numbers are to be displayed. The attributes involved are given in example (58).

6.12.2.2 Figure Reference Caption Layout

The figureRefCaptionLayout element determines how figure reference captions are to be displayed. All of its attributes are described in section “Format Information Attributes”, except that none of these attributes show in the XMLmind XML Editor for the figureRefCaptionLayout element.

6.13 Controlling the Display of Numbered Tables

The next three main elements describe how numbered tables are to be displayed and how references to numbered tables are to be handled.

6.13.1 Numbered Tables

The tablenumberedLayout dictates how tablenumbered elements are to be displayed. This can look like what is shown in example (59).

(59)

The align attribute of the tablenumberedLayout element can be set to define the default alignment of all numbered tables in the document as shown in example (60).

There are actually four parts here.

6.13.1.1 Numbered Table and its Caption

If you click on the first line, you control the tablenumberedLayout element. This has five attributes as shown in (61).

6.13.1.2 Numbered Table Label Layout

If in example (59), you click on the word “Table” in the second line, you can control information about how the label of the numbered table is to be formatted. The attributes for this tablenumberedLabelLayout element are given in example (62).

6.13.1.3 Numbered Table Number Layout

If in example (59), you click on the digit “1” in the second line, you can control information about how the number of the numbered table is to be formatted. The attributes for this tablenumberedNumberLayout element are given in example (63).

6.13.1.4 Numbered Table Caption Layout

If in example (59), you click on “Caption goes here” in the second line, you can control information about how the captions of numbered tables are to be formatted. The attributes for this tablenumberedCaptionLayout element are given in section “Format Information Attributes”.

6.13.2 Controlling the Display of References to Numbered Tables

There are two elements that control how references to the numbers of numbered tables and references to the captions of numbered tables are displayed.

6.13.2.1 Reference to Numbered Table Number Layout

The figureRefLayout element determines how references to the number of a numbered table are to be displayed. The attributes involved are given in example (64).

6.13.2.2 Reference to Numbered Table Caption Layout

The tablenumberedRefCaptionLayout element determines how references to the captions of numbered tables are to be displayed. All of its attributes are described in section “Format Information Attributes”, except that none of these attributes show in the XMLmind XML Editor for the tablenumberedRefCaptionLayout element.

6.14 Table Caption Layout

The tableCaptionLayout element describes how the caption in a table element should appear. Note that this is not for numbered tables, but is for “plain” tables and for tables in examples. The attributes for this tableCaptionLayout element are given in example (65).

6.15 Magnification Factor

When one is producing a paper for a poster session, sometimes one wants to enlarge the text of the document while maintaining the same page size. This is what the magnificationFactor element is for. Enter the factor you want (e.g., 1.5 or 2). The factor should be a number.

6.16 Special Overrides for langData Elements

Sometimes one wants language data to appear one way when it is in prose and another way in examples and/or tables. The langDataLayout element controls this. When you add it, you will see what is in example (66).

(66)

The top line has one attribute: language. Normally this attribute is empty. If you have a case where you need some langData elements to be formatted one way (say, as phonetic data) and others to be formatted another way (say, as phonemic data), then you can create two or more langDataLayout elements and set the language attribute of them to the id attribute of the language element designed for it. (This will be the same value as you use for the lang attribute of the langData element.) XLingPaper will use the first langDataLayout element that has its language attribute set to the lang attribute of the current langData element being formatted. If there is no langDataLayout element with a corresponding language attribute, then the first langDataLayout element is used.

The other three use the attributes shown in example (67).

For a given langData element, the formatting that is used depends on what the closest element to that langData element is. If an example is closest, then the formatting for an example is used. If a table is closest, then the formatting for a table is used. If an endnote or any other element is closest, then the formatting for prose is used.

Occasionally one finds that there are rare instances in a document where the textbefore and/or the textafter attributes of the special override are/is not correct for the context. In such cases, one can override the style sheet override by setting the textbefore and/or textafter attribute of the langData element in the document itself where that langData element occurs.

6.17 Special Overrides for gloss Elements

Sometimes one wants gloss data to appear one way when it is in prose and another way in examples and/or tables. The glossLayout element controls this. When you add it, you will see what is in example (68).

(68)

The top line has no attributes. The other three lines use the attributes shown in example (69).

There is actually a fourth element called glossInListWordLayout that controls how gloss elements are formatted in either listWord or word examples. You can insert it before the “gloss in example” line.

For a given gloss element, the formatting that is used depends on what the closest element to that gloss element is. If you are using a glossInListWordLayout element, then if either a listWord or a word element is closest, then the formatting of the glossInListWordLayout element is used. If an example is closest, then the formatting for an example is used. If a table is closest, then the formatting for a table is used. If an endnote or any other element is closest, then the formatting for prose is used.

Occasionally one finds that there are rare instances in a document where the textbefore and/or the textafter attributes of the special override are/is not correct for the context. In such cases, one can override the style sheet override by setting the textbefore and/or textafter attribute of the gloss element in the document itself where that gloss element occurs.

6.18 Special Overrides for free Elements

Sometimes one wants to override the default formatting for data in free translations (i.e in free elements). The freeLayout element controls this. It has the attributes shown in example (70).

Occasionally one finds that there are rare instances in a document where the textbefore and/or the textafter attributes of the special override are/is not correct for the context. In such cases, one can override the style sheet override by setting the textbefore and/or textafter attribute of the free element in the document itself where that free element occurs.

6.19 Special Overrides for literal Elements

Sometimes one wants to override the default formatting for data in literal translations (i.e in literal elements). The literalLayout element controls this. It contains two elements: literalLabelLayout and literalContentLayout.

The literalLabelLayout element allows you to type in a label that will appear at the beginning of every literal translation (e.g., “Lit. ”). It has the attributes described in section “Font Information Attributes”. You can use these attributes to format the label as needed. Example (71) shows the content of the label. Notice that the red cursor is at the end of the label.

(71)

The second element, literalContentLayout, has the attributes shown in example (72). You use these to control formatting of the content ot the literal elements.

6.20 Special Overrides for citation Elements

Sometimes one wants to override the default formatting for data in citations.

The citationLayout element has the attributes shown in example (73). You use this to control formatting of the content of citation elements.

6.21 Controlling the Display of Abbreviations in a Footnote

Sometimes one wants to control how the list of abbreviations come out when they are in a footnote. You do this via the abbreviationsInFootnoteLayout element. This element has one attribute: textBetweenAbbreviationAndDefinition which one can use to set the text that will be output between the abbreviation and its definition. If the textBetweenAbbreviationAndDefinition attribute is empty, then XLingPaper will use “ = ” as the text between an abbreviation and its definition.

6.22 Controlling the Display of Abbreviations in a Table

Sometimes one wants to control how the list of abbreviations come out when they are in a table. You do this via the abbreviationsInTableLayout element. The abbreviationsInTableLayout element has the attributes shown in example (74).

6.23 Controlling the Display of Glossary Terms in a Definition List

Sometimes one wants to control how the list of glossary terms come out when they are in a definition list (each term in a hanging indent paragraph, with the term appearing first, followed by the definition). You do this via the glossaryTermsInDefinitionListLayout element. It shows as shown in example (75).

(75)

The glossaryTermsInDefinitionListLayout element has the attributes shown in example (76).

Inside of the glossaryTermsInDefinitionListLayout are two others: glossaryTermTermInDefinitionListLayout and glossaryTermDefinitionInDefinitionListLayout. These allow you to control the formatting of the glossary term itself and also its definition. Both of them use the attributes in section “Format Information Attributes”.

6.24 Controlling the Display of Glossary Terms in a Table

Sometimes one wants to control how the list of glossary terms come out when they are in a table. You do this via the glossaryTermsInTableLayout element. The glossaryTermsInTableLayout element has the attributes shown in example (77).

6.25 Controlling the Display of ISO 639-3 Codes in a Table

Sometimes one wants to control how the list of ISO 639-3 codes come out when they are in a table. You do this via the iso639-3CodesInTableLayout element. The iso639-3CodesInTableLayout element has the attributes shown in example (78).

6.26 Controlling the Display of Prose Text

Sometimes one wants to override the default formatting for data in prose-text elements.

The prose-textTextLayout element has the attributes shown in example (79). You use this to control formatting of the content of prose-text elements.

6.27 Controlling the Display of Quotes

Sometimes one wants to override the default quotation marks before and after data in q elements.

The quoteLayout element has the attributes shown in example (80). You use these to control what comes before and after the content of q elements

6.28 Controlling the Display of Block Quotes

Sometimes one wants to override the default vertical spacing before and/or after a block quotation (blockquote elements).

The blockQuoteLayout element has the attributes shown in example (81). You use these to control the vertical spacing before and after the content of blockquote elements

See also section 2.2 for controlling the indent of blockquote elements.

6.29 Controlling the Display of Annotations

Sometimes one wants to override the default formatting for the paragraph in annotation elements (which appear via annotationRef elements).