Where Q++ Tokens get their information from
From the point of view of how Q++ gets the information to process tokens, tokens can be categorized as follows:
|System Tokens||These usually represent numbers and are only based on the current date of the token (as specified by the DayValue). An example is [d] which returns the number of the day (ie '12' for December 12).|
|User-Defined Tokens||These are defined by the user using the Tokens Manager, and usually only depend on the current language (as specified by the LanguageTag). An example is if you wished to create the token [:Christmas] for which you would establish a translation in one or more languages.|
|Mixed-Source Tokens||These tokens require the user to supply a translation, but Q++ still needs to determine how to process them. An example is the token [:season]. The user definitely needs to tell Q++ what the translation for spring, summer, fall, winter is for each language needed. But it is Q++, based on the current date of the token, which will decide whether the token [:season] is replaced by "spring" or by "winter".|
There can be hybrid cases, since tokens can be recursive (ie the translation of a user-defined token involves another token). But, even so, the treatment of each individual sub-token still fits into the above categories.
Important : There are many options within Q++ to disable the treatment of individual tokens. For example you can ask Q++ to ignore tokens whose current date is outside of a given month. If you have a valid token and have supplied a translation for it and still it does not appear in your output file, then make sure that none of the disabling options is interfering. For more information see Disabled Tokens in a Script.