Zip CSVs

This option should always be set to true.

Keep CSV files

This option should always be set to true.

Use Native Paragraph Formatting

QuarkXPress

2016-2024

This option determines if the paragraph formatting of the current script, such as used in GenTokens and Minicalendars, uses the legacy xpress tags formatting or native formatting.

➢When using InDesign, this setting is always true.

Note that this setting, when using QuarkXPress 2016-2024, is overridden to true if the force native paragraph formatting preferences setting is set to true.

Remove GridTemplate layers

Setting this option to true means that, during diary generation, prior to copying GridTemplates and Info Page Files, Q++Studio will tell QuarkXPress to move all objects from any non-default layer to the default layer, and will delete all non-default layers

➢The moving of objects to the default layer and the deletion of all other layers is done to copies of your QuarkXPress documents, and not to the original documents themselves.

The recommended value for this option is false when using QuarkXPress 2015-2024.

InDesign

Note that there are no default layers in InDesign and, therefore, this option is always ignored in InDesign scripts (that is to say, it is always assumed to be false).

Break links to Master Pages

When this option is set, at the end of Diary Generation, all objects of the output file are disconnected from their Master Page, and then all objects are deleted from all Master Pages. Note that, for obvious reasons, this option automatically disables the Lock All Objects option.

InDesign

Due to the manner in which master pages are handled in InDesign, this option is always turned on for InDesign, internally, and therefore does not appear in the list of available options.

Remove OPF layers

Setting this option to true means that, after diary generation, Q++Studio will tell QuarkXPress to move all objects from any non-default layer to the default layer, and will delete all non-default layers, in the output file. Note that this property has no use if the value of the Remove GridTemplate layers option is true (which is not recommended when using QuarkXPress 2015-2024).

InDesign

Note that there are no default layers in InDesign and, therefore, this option is always ignored in InDesign scripts (that is to say, it is always assumed to be false).

Verify page objects' sizes

This property is currently (April 2024) not implemented.

Fix Z-order

QuarkXPress 2015-2024

Starting with QuarkXPress 2015, master pages can have layers, and therefore it is recommended that you keep the layers of your templates (ie. set the option Remove GridTemplate layers to false) and set this property also to false (Fix Z-order to false).

QuarkXPress 8-10

QuarkXPress 8-10: This option, which is set by default to True, tells QuarkXPress to verify that the objects, copied to the output file from a template, remain in the right Z-order (ie. an object that was on top of another object in the template remains so in the output file). Usually, this option should remain set to True, unless your template has a lot of objects, in which case the process of checking, and eventually fixing, the z-order of all the objects can take a lot of time (ie. diary generation will remain stuck at 30% for up to 20 minutes for a template with 2000 objects).

InDesign

Does not apply to InDesign.

Color Matching

This property tells QuarkXPress which method to use to identify colors during diary generation. The 3 possible values are: Color Name, RGB, and CMYK.

➢The recommended default value is Color Name.

Does not apply to InDesign, which always uses color name matching.

Arabic Text Processing

(does not apply to InDesign, which handles Arabic internally)

This Generation Option determines how ligatures and contextualization of text is performed in an Arabic text encountered. The options are:

•Font-Dependent Ligatures: The processing of Arabic text in done inside QuarkXPress, where the font used by each string of Arabic text is tested as to which ligatures and context forms it contains, so that more advanced ligatures and context forms are not attempted if the font does not support it.

•Font-Dependent Ligatures Always: Same as above, except that the processing of Arabic text is performed even if there are no token instructions containing Arabic generated from within Q++Studio. In effect this option allows for the processing of hard-coded Arabic text that was already in one of the current script's GridTemplates or in one of the Quark File.

•Minimal Ligatures: This processing of Arabic text is performed within Q++Studio, with no regards as to the font used by any of the Arabic text stemming from the token instructions of the current script. To avoid any problems with fonts which do not support all the ligatures and context forms contained in the Unicode 5.0 standard, only the very essential ligatures (such as LAM-ALEH) and context forms are attempted.

•Full Ligatures: This processing of Arabic text is also performed within Q++Studio, with no regards as to the font used by any of the Arabic text stemming from the token instructions of the current script. However, in this case, all the fonts used to display Arabic are assumed to support all the ligatures and context forms contained in the Unicode 5.0 standard. Use this option only if you are sure that all the fonts used in the current script are fully Unicode compliant.

•No Ligatures: Use this option to totally ignore any Arabic text encountered in any of the token instructions or hard-coded in the current script's GridTemplates or in one of the Quark File files.

The default, and recommended, setting is Font-Dependent Ligatures.