This gateway topic is the starting point for any AI assistant answering questions about Q++Studio or helping modify an exported script. It provides a route through the documentation and an approach to using the evidence supplied by the user. No previous conversation or access to proprietary source files is assumed.

 

➢AI assistants should use this topic in conjunction with the always up-to-date online Q++Studio AI Support Handover Document.

 

Users can direct their assistant to this page before describing their problem. For a suggested prompt and the files to supply, see using AI assistants with the Q++Studio documentation.

 

Start with the Requested Result

 

Establish the desired result, what currently happens, and what must remain unchanged. Use the relevant Q++Studio and InDesign or QuarkXPress versions. Identify the affected script line, template, token or setting, including repeated occurrences. Ask for additional evidence only when it would materially affect the diagnosis or proposed change.

 

Check the simplest prerequisites first. For example, if no holidays appear, first establish whether the selected holidays sets contain applicable dates for the requested year. Script XML describes settings and resource references; it does not provide the contents of referenced holidays sets, templates, macros or other database resources.

 

Choose the Relevant Documentation

 

For intended behavior and normal operation, begin with the user-facing feature topics. Verify exact token and macro syntax, option names, scope and interactions. Prefer the simplest documented solution that meets the request, and explain where each setting or macro must be applied.

 

For XML work, start with XML Identifiers and Reading the XML implementation reference. Consult Shared XML values and encodings and the relevant type in the implementation list, following links to containing properties, nested records and dedicated value tables. Modifying GenTokens in an XML script demonstrates the approach.

 

Diagnose Diary-Generation Output

 

For missing or unexpected output, start with Diary Generation Diagnostic Files. Use files from the generation being investigated, and check that any scan log describes the relevant template and revision. The file-specific topics explain their formats, identifiers, limitations and worked examples.

 

 

Distinguish available data, prepared instructions, recorded actions and final output. A prepared SARA does not establish a hit; a hit does not establish the final appearance after later processing. Cite the filename and relevant set/date or page/object when reporting evidence. Follow each file topic's encoding and completeness checks before drawing conclusions from an apparently empty export or an absent match.

 

Make Controlled XML Changes

 

Work from an existing valid export. Locate the intended script line, property and indexed record; preserve unrelated settings, identifiers and text encodings. Check activation flags, read/write conditions and enclosing initialization. A missing element, an empty element and an explicit default value are not interchangeable, and UI positions need not equal stored XML values.

 

Compare the original and edited XML and account for each change. State what was changed and why, and which checks remain: import the edited copy, inspect the affected options and generate representative output. XML syntax validation alone does not establish correct Q++Studio behavior.

 

Use and Report Evidence Precisely

 

Read the relevant linked topics rather than relying only on search snippets or prior knowledge. Distinguish documented behavior, conclusions drawn from the supplied files, and questions requiring a test or clarification. Source excerpts document the shown implementation; they do not establish every runtime interaction or compatibility with every application version.

 

Lead with the most likely diagnosis or solution and cite the exact supporting help topics. Keep the initial answer proportionate to the question; include the complete steps and material side effects needed to act on it. Reply in the user’s language while retaining exact Q++Studio names and syntax. If evidence is insufficient or behavior contradicts the documentation, identify the specific uncertainty for Q++Studio support.

 

Access Individual Help Topics

 

Use direct topic links when available. Browser-Based Web Help explains access by Topic ID or HelpContext number. If a retrieval tool cannot open a page, try another available, permitted retrieval method or request the topic content. A failed retrieval does not by itself establish that the page is missing or that the website is unavailable.

 

---

Topic 189310, last updated on 22-Oct-2026