AI assistants such as ChatGPT or Claude can greatly help you navigate the nearly 3000 topics of the Q++Studio documentation and identify the relevant features, topics and terminology.
AI assistants are usually most helpful when used to:
•Translate your request, not necessarily stated in English, into Q++Studio terminology.
•Identify the relevant help topics.
•Explain the relationship between several features.
•Suggest where in the documentation the answer is likely to be found.
AI assistants can often suggest a complete, documented sequence of steps when given enough information. However, they may not be able to inspect the internal structure of native QuarkXPress or InDesign files reliably. For layout-related questions, include screenshots or a PDF preview, and paste all relevant tokens and settings as text.
At the bottom of this topic, you will find a copyable template to use when prompting an AI with a question related to Q++Studio.
General Considerations
You don't have to ask your question in English
You can describe your problem in your own language. Most AI assistants can usually understand your question, identify the corresponding Q++Studio terminology in the English documentation, and explain the solution back to you in your language (while retaining the Q++Studio-specific English terms).
For best results
Include:
•The exact current result and the exact desired result, preferably using a short before-and-after example.
•Anything that must remain unchanged. This helps prevent the assistant from suggesting a broader solution than necessary.
•A screenshot of the desired result, if applicable.
•Your current script, saved as XML (although the XML representation of Q++Studio scripts does not contain the actual contents of referenced InDesign or QuarkXPress templates or the underlying names and contents of referenced database records, the XML format of Q++Studio scripts is fully documented and most AI assistants understand it and are able to offer precise advice based on the XML version of a script).
•The relevant template, macro or output file, if available.
•Any error message, exactly as displayed.
•The version of Q++Studio you are using (XV4, XE3, ...).
•Whether you are using InDesign or QuarkXPress.
Always paste tokens, macro code, error messages and relevant option names as text, even when they are also visible in a screenshot. Characters such as +, -, =, :, |, brackets and capitalization can materially change their meaning.
Unexpected Token Behavior
When a token produces an unexpected result, include:
•The exact token.
•Where it is located: template page, textbox, group or layer.
•The value or result you expected.
•The value or result actually obtained.
•At least one situation where it works and one where it fails.
•Whether the same GridTemplate occurs more than once or is part of an insertion.
Exact comparative results such as “the token returns 1/2 in the first occurrence but 70/71 in the second” are often much more useful than a general description that the token does not work.
Ask in terms of the desired result
Do not try to use Q++Studio technical terms (unless you already are familiar with them), but rather explain your query in natural language (including your own language, if it's not English).
Instead of:
➢How do I use token XYZ?
describe the intended result or problem that you are encountering:
•I want a five-row MiniCalendar where the last week displays dates as 23/30 and 24/31.
•I want weekend dates to appear in a different color.
•My MiniCalendar dates come out staggered, like a staircase.
The AI assistant can then identify the relevant Q++Studio terminology and direct you to the appropriate documentation topics.
Of course, knowledgeable users should include exact Q++Studio terms and tokens that they know (they simply should not guess terminology they are unsure of).
Include screenshots
Screenshots are often more useful than long explanations, especially for:
•MiniCalendars
•date formatting
•colours and typography
•GridTemplate layout
•InDesign or QuarkXPress formatting
Note that uploading images or screenshots may increase AI usage and can result in temporary usage limits.
Specific Text To Include In Your Prompts
Below are some boilerplate texts that should be included in any AI prompt that you make (see the combined prompt template at the bottom of this page).
Ask the AI assistant to use only the Q++Studio documentation
Very important: Make sure to tell the AI assistant to only refer to the Q++Studio documentation and not to try to fill-in any missing information. Its answers should solely be based on the appropriate Q++Studio documentation (XE3 or XV4).
Make sure to include text similar to the following in all your prompts:
➢Using only the current online Q++Studio XE3 documentation, link to the exact topics supporting your answer. Clearly distinguish documented behavior from your own inference. If the documentation does not provide enough information to decide, say so explicitly rather than guessing, and explain what additional test or information would be needed.
The above reduces the risk of unsupported assumptions and makes it easier to identify when the documentation itself does not fully answer the question.
Ask for the most likely solution first
Q++Studio covers hundreds of special cases that sometimes only one client uses in one of their diaries, and the Q++Studio documentation covers all these esoteric cases in detail. The problem is that AI assistants will gladly mention all these cases, unless asked not to.
So, on the first iteration of your asking a question to an AI assistant, make sure to include text similar to the following in your prompt:
➢Start with the most likely/simple Q++Studio solution. Only suggest advanced, specialized or token-modifier solutions if the simpler solution does not apply.
Later, if needed, you can always go back and ask the AI assistant to look at more obscure cases.
Ask for an end-to-end answer and its scope
When asking for a solution, request the complete sequence of steps, including where each option is configured. Also ask what the suggested change affects: individual characters, the entire textbox, a group, a layer, a page, or every occurrence of the GridTemplate.
Explain how to follow up
If the first suggestion does not work, continue in the same conversation and report exactly what you tested and what changed. Avoid simply saying “it did not work” A diagnostic token, representative output values, or a reduced example will usually make the cause much easier to identify.
Below is a single copyable template to use when prompting an AI with a question related to Q++Studio (remember that the specifics that you supply do not need to be in English; use whichever language you are most comfortable with).
Using only the current online Q++Studio XE3 documentation, link to the exact topics supporting your answer. Clearly distinguish documented behavior from your own inference. If the documentation does not provide enough information to decide, say so explicitly rather than guessing, and explain what additional test or information would be needed.
Q++Studio version: insert your specifics here
QuarkXPress or InDesign version: insert your specifics here
Desired result: insert your specifics here
Current result: insert your specifics here
What must remain unchanged: insert your specifics here
Exact tokens or settings involved: insert your specifics here
Where they are located: insert your specifics here
Tests already performed: insert your specifics here
Please provide the complete sequence of steps and explain the scope and any side effects of the proposed solution.
Topic 189120, last updated on 13-Sep-2026
