Please enable JavaScript to view this site.

 

Navigation: Scripts > Diary Generation > Diary Generation Options

Diary Generation Options - During Generation

Scroll Prev Up Next More

During Generation

 

The Generation tab of the diary generation options dialog below are used to tweak the way Q++Studio behaves during diary generation and correspond to options of the Generation Options property.

 

Keep log of errors

This options should always be set to true unless you are experiencing a particular problem and technical support has instructed you to turn this option off.

Trim Blank Pages

Use this option, true by default, to have diary generation stop at the last non-blank page of the diary (follow the link to the corresponding property on the left for more details on what constitutes a blank page). This option can speed up diary generation, particularly step 3, page copying, for large diaries that contain over 200-300 pages.

Hide PlaceHolder labels

By default, this option is set to false, and Q++Studio generates a textbox on each PlaceHolder page, displaying the page number within the PlaceHolder (ie. page 3/8), the text of the label property and comments property for all the PlaceHolder script lines of the current Script.

Setting this property to true will leave the pages of the current PlaceHolder script line blank in the output file.

Execute Saras (if any)

The property corresponding to this option should always be set to true (what's the point of setting-up Saras if you do not perform them?), but on occasion, when testing out specific parts of a diary, you may wish to temporarily turn off this option here in the diary generation option.

Test for text overflow

This option alerts you to any possible text overflow in the generated output file.

 

Any text overflow encountered by Q++Studio while generating an output file will be logged. This verification is performed in all the textboxes of the output file, not only those in which tokens were replaced or a SARA acted.

 

Text overflow, denoted by the symbol in QuarkXPress, usually occurs when inserting text of variable length such as holidays or slogans. But it can also occur the first time you generate a diary in a new language, particularly for languages with long weekday names such as German.

 

You should always set this option to true.

Facing Pages

non-facing and facing pages

non-facing and facing pages

When this option is set to true, the pages in the QuarkXPress or InDesign output file are displayed facing one another, like in a normal book.

 

By default this property is set to true since that best represents a physical diary.

 

There are 2 possible reasons to set this property to false:

 

Some dated products, such a wall calendars, or diary models with a horizontal spine, do not lend themselves to a facing pages layout.

The width of QuarkXPress spreads is limited (48 inches, approximately 122 cm, for QuarkXPress 3-10, and 224 inches, almost 6 meters, for QuarkXPress 2015 and above). This means, for facing pages, a maximal page width of 24 inches for QuarkXPress 3-10, and 112 inches for QuarkXPress 2015 and above. Therefore, if you need to generate documents with a page width larger than 24 inches (or 112 inches), the you need to set the Facing Pages option to false.

Whether you choose to use facing pages, or not, for your output file, remember that you should not use facing pages for your GridTemplates.

 

After Generation

 

The After Generation Diary Generation Options below cover the steps to be performed by Q++Studio after a diary has been generated (a link is provided whenever a property can be used to set this option for the current script or as a default).

 

Open DTP output

If this option is on, then the QuarkXPress or InDesign file corresponding to the generated diary will automatically open at the end of diary generation (if there were no major diary generation messages).

Export to PDF

This option means that the generated output file is exported to PDF (if the generated output file contains no major diary generation messages).

 

When the Export to PDF option is checked, then the 2 options below become available.

 

Using Style

This is the QuarkXPress Output Style or InDesign PDF Preset to use to export the current output file to PDF.

Open PDF output

If this option is on, then the QuarkXPress or InDesign file corresponding to the generated diary will automatically open at the end of diary generation (if there were no major diary generation messages).

 

Note that if you are using InDesign, and the InDesign PDF Preset that you are using specifies that the generated PDF should be opened after being generated, then both copies of the generated PDF will be opened, the one in the temporary folder, and the one on the server. This can lead to confusion (changing one PDF which is the temporary, disposable, one, rather than the one in the output folder) as well as the message 181585 if you leave the PDF file of the temporary folder open.

Beep on completion

Use this option to have the internal speaker of your PC emit a short beep to indicate that diary generation is complete.

 

Safeguards

 

The settings below are used to protect against a script going into an infinite loop. The default values rarely need to be changed.

 

Max. Iterations

When Q++Studio evaluates a token, it keeps track of the number of levels of iterations used in converting each individual token. Whenever that number reaches the value of the Maximum Iterations property, the processing of the token is stopped and a run-time error message is generated.

 

Most tokens get converted with an iteration level of 0 (zero). The token comes in and is replaced by text that does not contain tokens. For example, [a1Dddd] may get converted to Monday.

A token such as [a1:dmmmm] may be converted, depending on the language, into [Mmmm] [d][.d] which would cause the token conversion to be called 3 more times to evaluate these 3 tokens, hence a recursion level of 3.

Even recursive macro tokens that generate complete months and format different elements of each day differently, usually reach an iteration level of about 300 only.

 

As can be seen from the above examples, the default value for this property, 1000, should be more than enough in all cases. If necessary, this value can be increased to 10000, but most of the time you will not need to change the value of this property.

Max. Recursion

When Q++Studio evaluates a token it keeps track of the number of levels of recursion used. Whenever that number reaches the value of the Maximum Recursion property, the processing of the token is stopped and a run-time error message is generated.

 

Most tokens get converted with a recursion level of 0 (zero). The token comes in and is replaced by text that does not contain tokens. For example, [a1Dddd] may get converted to Monday.

However, sometimes, a conversion functions must evaluate included tokens immediately because the original token's date cannot be used for these included tokens. This is the case for duration tokens and minicalendar tokens. This is usually a sign that you are replacing a token by the same token, either in the multi-holidays surrounding text or the Moon options. In these cases the recursion level of the conversion function calling itself can increase.

 

The default value for this property, 50, should be more than enough in all cases. If necessary, this value can be increased to 500, but it is not recommended as it can cause a stack overflow, and most of the time you will not need to change the value of this property.

 

If you want any of the above settings values to be standard for all new script created in the future, then you can change the default values of all the diary generation options that correspond to script line property by going to the Execution Preferences.

 

See also: other diary generation options.

 


Topic 177205, last updated on 20-Aug-2021