Please enable JavaScript to view this site.


Navigation: ScriptLine Properties > Generation Options

Generation Options: QuarkXPress Options

Scroll Prev Up Next More

The options in the QuarkXPress Options tab of the generation options ScriptLine property dialog are:


Strip style sheets

When this option is set to true, Q++Studio will remove style sheets from the copy of the GridTemplates used in the current script's generation. This feature may be needed if style sheets are slowing down the copying of pages, on certain GridTemplates, and more importantly, if a conflict in the style sheets used in different GridTemplates of the same script cause QuarkXPress to crash.


Using this option will not change the individual attributes of text that uses style sheets; it will only make those attributes independent of style sheets and remove these style sheets form the output file.

Ignore Invisible Layers

This option, available for Quark versions 8 and above, if checked, tells Q++Studio to ignore all the objects placed on layers that were left as invisible when the GridTemplate was saved.

Use Main Grid as seed for generation

This option, if turned on (the default), ensures that the generated output file of a script uses the Main Grid of that script instead of blank pages as the seed template from which the diary is built. This means that the QuarkXPress preferences of your Main Grid (such as superscript values, em-spaces, ...) are applied automatically to the generated output file.


This option may need to be turned off in some rare cases when the preferences of the Main Grid template conflict with the default preferences of QuarkXPress on your PC, or with the preferences of other GridTemplates used by the same script.

Remove GridTemplate layers

Setting this option to true means that, during diary generation, prior to copying GridTemplates and Plain Quark 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.Note that 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 QuarkXPress documents themselves.


The recommended value for this option is true for Quark 8-10 and false for Quark 2015 and above.

Keep Master Pages' vignette names

This option is useful in scripts that contain many different templates. It ensures that the master pages of the output file maintain any special name that you may have given them in the original GridTemplate.


With the present option set to false, the master pages of the output file simply refer to the number of the template and its page number. But when we set the present option to true, then the master pages of the output file keep these vignette names, making it easier to locate individual pages.

Option FALSE

Option FALSE

Option TRUE

Option TRUE

Note that the use of the option Use Main Grid as seed for generation (see above) will cause the vignette names of at least the Main Grid master pages to be carried over to the output file.


Recommended default: none, as it is a matter of preference.

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.

Arabic Text Processing

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.

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. Note that, for obvious reasons, this option automatically disables the lock all objects option.

Fix Z-order

Quark 2015 and above: Starting with Quark 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.

Quark 8-10: This option, which is set by default to True, tell 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).