The Line Endings and Formatting dialog is used to specify what line ending to use and, eventually, if any formatting should be applied to that paragraph, depending on the corresponding Special Case Condition being true.
The simplest line endings are :
|Soft Return||This setting separates the current line generated by the GenTokens Options from the next using a soft return. Visually this looks like a paragraph, but in reality it is only a change of line, which means that any paragraph attributes such as rules above/below and space before/after do not occur between lines separated with a soft return.|
|Hard Return||This setting separates the current line generated by the GenTokens Options from the next using a hard return. Note that this setting does not mean plain paragraph, it means same paragraph attributes as the original token. All the paragraph attributes of the original [GenTokens] token, such as rules above/below and space before/after will occur for lines generated using the hard return line ending setting. If there is not paragraph mark after the GenTokens token, any rules above/below that are part of the paragraph attributes of the token will not be visible in the GridTemplate, but will become visible in the output file because each generated line ends with a line ending (even the last generated line).|
|Tabulation||Strictly speaking, this is not a line ending, but it can be useful to separate days of the week for cases when you might want to build a minicalendar, date-by-date, using [GenTokens]. In that case you would specify the tabulation as the default line ending and use formatting or Xpress tags (see below) for Sundays.|
The soft and hard returns options are ideally suited to simple grids where a simple pattern is turned on (using a hard return) or off (using a soft return) alternatively.
There are 4 other simple line endings that are seldom used, but very powerful when required :
|Nothing||Strictly speaking, this is not a line ending, but it can be useful to create your own duration tokens made up of multiple tokens.|
|Next Column||This setting lets you change from one column to another, rather than having the series of tokens on separate lines. Each line is separated by a next column special character.|
|Next Box||This setting lets you change from one linked/chained textbox to another, rather than having the series of tokens on separate lines. Each line is separated by a next (linked) box special character.|
|Skip Line||This setting means that if the corresponding Special Case Condition is true then the current line (text and line ending) will be skipped. This would, for example allow you to use a GenTokens token to create a more powerful holiday or Moon duration token by skipping days when there is no holiday (or Moon phase).|
For more power and control, Formatting is the best suited option, allowing you to use all the settings that you would find in the Paragraph Attributes dialog of QuarkXPress. Selecting the Formatting type of line ending displays the Paragraph Formatting page control with 3 tabs :
|Formats||The settings of this tab are the same as those of the corresponding tab in QuarkXPress. Note that the Language specified for each paragraph is set to English, to ensure compatibility with users who do not have the Passport version of QuarkXPress. In any event the language used makes no difference to a paragraph mark.|
|Tabs||This tab is quite different from the corresponding tab in QuarkXPress. You can specify a series of tabs, their position, alignment and fill characters, and you can additionally insert many tabs at once, using either of the Add Multiple Tabs or Add Tabs from Xtags buttons.|
|Rules||The settings of this tab are the same as those of the corresponding tab in QuarkXPress. Note that to be able to specify a negative offset the offset units must be set to mm (not %). Note that, beginning with build 16861, the various styles of dashes and stripes that you may have created in your template, will be available to select in the Styles dropdown combo.|
For each of the above 3 tabs, you are given the option to Override the attributes of the original token. If you leave any of these checkboxes unchecked, then the corresponding attributes used for the current line ending will be those of the original [GenTokens] token. Any attribute whose Override checkbox is unchecked will behave as described in the discussion on Hard Return option, above. Note that the measurements of these 3 tabs are specified using the very powerful Quark Measurements Editors which can save you a lot of time when setting up a GridTemplate. If you are not familiar with the properties of these edit controls, click on their link to learn more about them.
Finally, for those cases where the condition or the line ending is too complex, you can use either of the other 2 options :
|Macro Token||For cases where the condition that determines the type of paragraph formatting is very complex, you can choose to place a macro token at the end of each generated line, a macro token presumably to be replaced by Xtags Text. It is important to note that this macro token will be converted as any other macro token, which means that you must include a return character in either sResult or the Xtags Text used.|
|Xpress Tags||This option allows you to specify virtually any Xpress Tags text as line ending to separate the current line from the next. This option is powerful and lets you specify line separations such as double returns that cannot be achieved with the Formatting options above (which is limited to a single line ending). However you should feel at ease with Xpress Tags before attempting to insert raw Xpress Tags into this field as results from incorrect text can range from bizarre output to a solid QuarkXPress crash. An excellent reference on the Xpress Tags descriptor language can be downloaded from www.emsoftware.com.|
If you need to show different text and tokens, depending on the corresponding Special Case Condition, then you can specify that the default text and tokens of the current GenTokens should be overridden:
Note that overriding the text and tokens only applies to the text to be displayed on the current line, and that it still allows you to select the line ending of your choice (the option to override text and token is not available, for obvious reasons, if the line endings are set to Macro Token, Xpress Tags, or Skip Line, as described above).
Finally, to avoid having to copy multiple settings manually between the various GenTokens, you can use the Copy to/from button located at the top right of the tabsheet to copy GenTokens options and sub-options all at once.